On Tue, 2015-11-24 at 11:14 -0600, Eric Sandeen wrote: > In a nutshell, though, I think a filesystem repair should be an > admin-initiated > action, not something that surprises you on a boot, at least for a > journaling > filesystem which is designed to maintain its integrity even in the > face of > a power loss or crash.
Well I wouldn't agree here... I maintain some >2PiB of storage for a LHC Tier-2,... right now everything with ext4. During normal operation we can of course not have any fsck, but every now and then, when we reboot, it happens automatically,... and regularly shows at least some (apparently non-serious) glitches. IMHO, either the kernel driver itself already checks "everything", then we wouldn't need a dedicated check tool. Or it does not, but in that case, there will be people who want to have that in-depth checks run regularly (and even if it's just every half a year). I better wait half an hour at boot, and find such errors, rather than that they silently pile up until I really run into troubles. That being said, of course it should be configurable for the admin... and it is, via fstab. So apart from that, given the expectation that btrfsck should be rock- solid as e.g. e2fsck in some future, I wouldn't see why people shouldn't have the necessary facilities to have it auto-run. Cheers, Chris.
smime.p7s
Description: S/MIME cryptographic signature
