From: Theodore Tso <tytso@MIT.EDU>
To: Mike Frysinger <vapier@gentoo.org>
Cc: util-linux@vger.kernel.org
Subject: Re: `fsck -A` and fs-specific options
Date: Wed, 13 Jul 2011 07:17:27 -0400 [thread overview]
Message-ID: <EFBAB464-FF32-46CB-8BB9-A94CE880F730@mit.edu> (raw)
In-Reply-To: <CAJaTeTpBxcZ8ofxSHd7B1aRbU3wtSH=ED6ZYKEPPs4q3fgc2nA@mail.gmail.com>
On Jul 12, 2011, at 3:18 PM, Mike Frysinger wrote:
> when i read the kernel source, that seemed to be the case. but i dont
> think it's the case for reiserfs, and i think there's a very tiny edge
> case with ext[34] related to moving the journal, but probably so small
> we can ignore it :p.
What do you think the edge case is? Yes, the external journal's
dev_t is cached, but that is only used by the kernel since it
was simpler than having callouts to a userspace daemon.
E2fsck will use blkid to locate the external journal, and when it
finds it, it will update the cached dev_t if it is out of date, so that
at mount time the kernel will be able to find the external journal.
This way even if the external journal is on a device with an
unstable dev_t (e.g., a USB device), the right thing should
happen...
-- Ted
next prev parent reply other threads:[~2011-07-13 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 2:59 `fsck -A` and fs-specific options Mike Frysinger
2011-07-12 11:02 ` Theodore Tso
2011-07-12 19:18 ` Mike Frysinger
2011-07-13 11:17 ` Theodore Tso [this message]
2011-07-13 18:31 ` Mike Frysinger
2011-07-13 8:32 ` Karel Zak
2011-07-13 11:13 ` Theodore Tso
2011-07-13 15:03 ` Fake block devices (Was Re: `fsck -A` and fs-specific options) David Zeuthen
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=EFBAB464-FF32-46CB-8BB9-A94CE880F730@mit.edu \
--to=tytso@mit.edu \
--cc=util-linux@vger.kernel.org \
--cc=vapier@gentoo.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.