Christoph Anton Mitterer posted on Tue, 24 Nov 2015 05:43:31 +0100 as excerpted:
[Duncan wrote...] >> The btrfs kernel code itself detects and often >> corrects many problems, and btrfs check is simply not recommended for >> automatic at-boot scheduling -- if the kernel code can't fix it without >> intervention, then the problem is too serious to be fixed without >> intervention by some scheduled btrfs check run, as well. > I once had an issue with a btrfs, where the kernel didn't show anything > but btrfsck did...(not the one Qu's currently looking into). That wouldn't be entirely uncommon, because as Eric mentions, btrfs check is intended to be thorough, where the kernel mount-time check is intended to be fast. But of course, as Eric also mentions, that's yet another reason you don't want btrfs check running at boot... it's *SSLLLOOWWWWW*, because it's being thorough. There are times you'd want to run btrfs check, the reason it's even there as a subcommand, but that would be when the filesystem either fails to mount, or when it exhibits other serious symptoms of problems... send and balance fails, remount-readonlys, nasty messages in the kernel log, etc. Careful admins may want to run btrfs check periodically in any case, but because it /is/ slow, and because it /isn't/ supposed to be needed for routine issues, they probably don't want to be doing it at boot when everything else is waiting on it. Because you don't want your boot taking hours... And in many cases, if a check /is/ going to take hours and even then not guarantee that the filesystem is workable, admins may want to simply blow away the filesystem, recreate it, and copy everything back to it from backups, rather than spending that much time on something that still has a good chance of being broken afterward. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
