From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: shall distros run btrfsck on boot?
Date: Tue, 24 Nov 2015 06:56:35 +0000 (UTC) [thread overview]
Message-ID: <pan$d4967$d0c5632e$fa0a61b0$e3c076ef@cox.net> (raw)
In-Reply-To: pan$c9010$71046470$f37154a0$cd8b55eb@cox.net
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.)
--
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
next prev parent reply other threads:[~2015-11-24 6:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 4:02 shall distros run btrfsck on boot? Christoph Anton Mitterer
2015-11-24 4:31 ` Wang Shilong
2015-11-24 4:35 ` Duncan
2015-11-24 4:40 ` Eric Sandeen
2015-11-24 4:43 ` Christoph Anton Mitterer
2015-11-24 5:33 ` Qu Wenruo
2015-11-24 6:46 ` Duncan
2015-11-24 6:56 ` Duncan [this message]
2015-11-24 17:14 ` Eric Sandeen
2015-11-24 17:23 ` Christoph Anton Mitterer
2015-11-24 20:38 ` Austin S Hemmelgarn
2015-11-24 22:26 ` Eric Sandeen
2015-11-24 22:33 ` Hugo Mills
2015-11-24 23:01 ` Christoph Anton Mitterer
2015-11-24 23:06 ` Hugo Mills
2015-11-25 1:59 ` shall distros run btrfsck on boot?(Off topic, btrfs per-inode tree idea) Qu Wenruo
2015-11-25 12:32 ` shall distros run btrfsck on boot? Austin S Hemmelgarn
2015-11-25 15:26 ` Martin Steigerwald
2015-11-28 16:52 ` Jeff Mahoney
2015-11-30 1:59 ` Qu Wenruo
2015-11-30 19:27 ` Jeff Mahoney
2015-11-30 15:06 ` Austin S Hemmelgarn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='pan$d4967$d0c5632e$fa0a61b0$e3c076ef@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.