Dude, > Precis: if the file system is very busy (being hammered) *and* it's > over 85% full, the block allocator can get stuck trying to work out > the *very best* allocation rather than one that'll do and let it get > on with other work. To the point where you see CPU go through the > roof, with 80% system CPU and a very unresponsive system. You can't > stop this without rebooting the box.
This is exactly what we're seeing, except that we could get out of it by dropping older snapshots. > Sun acknowledged it as a bug and it'll be fixed in a future release; > they gave us a hotpatch. The workaround? Keep the ZFS filesystem in > question under 70% full ... :-) > This is an obscure bug and isn't reason to avoid ZFS in general - the > bug only gets tickled in particular circumstances, when ZFS is having > the heck beaten out of it. I'd still happily recommend ZFS for almost > anything, because it really is *that cool*. hehehehehe, 'the heck beaten out of it' sounds like what we tend to do to our systems at wikimedia ;-) by the way, if you know such details, what are you doing in editing community. get over to the dark side ;-)) Domas _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
