On 11/24/15 12:56 AM, Duncan wrote: > Duncan posted on Tue, 24 Nov 2015 06:46:18 +0000 as excerpted: > >> 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. > > Oops! Mis-attribution. Qu not Eric. > > (I had read both replies in my email but only saw Eric's on the list, > which I read in my news client via gmane's list2news service, when I > composed the above. So I presumed the points I remembered being made > were from Eric's post, when it was Qu's.)
Yeah, I don't think that being thorough requires being slow. ;) 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. -Eric -- 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
