From: Eric Sandeen <sandeen@redhat.com>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>,
Christoph Anton Mitterer <calestyo@scientia.net>,
Duncan <1i5t5.duncan@cox.net>,
linux-btrfs@vger.kernel.org
Subject: Re: shall distros run btrfsck on boot?
Date: Tue, 24 Nov 2015 16:26:47 -0600 [thread overview]
Message-ID: <5654E427.6060708@redhat.com> (raw)
In-Reply-To: <5654CAE0.5040907@gmail.com>
On 11/24/15 2:38 PM, Austin S Hemmelgarn wrote:
> if the system was
> shut down cleanly, you're fine barring software bugs, but if it
> crashed, you should be running a check on the FS.
Um, no...
The *entire point* of having a journaling filesystem is that after a
crash or power loss, a journal replay on next mount will bring the
metadata into a consistent state.
-Eric
next prev parent reply other threads:[~2015-11-24 22:26 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
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 [this message]
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=5654E427.6060708@redhat.com \
--to=sandeen@redhat.com \
--cc=1i5t5.duncan@cox.net \
--cc=ahferroin7@gmail.com \
--cc=calestyo@scientia.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.