From: Theodore Tso <tytso@MIT.EDU>
To: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
Cc: Matthias Koenig <mkoenig@suse.de>,
ludwig.nussel@suse.de, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] [RFC] New fsck option to ignore device-mapper crypto devices
Date: Thu, 6 Mar 2008 12:42:20 -0500 [thread overview]
Message-ID: <20080306174220.GH18188@mit.edu> (raw)
In-Reply-To: <1204824227.7964.4.camel@norville.austin.ibm.com>
On Thu, Mar 06, 2008 at 11:23:47AM -0600, Dave Kleikamp wrote:
> Zero tells fsck not to check the filesystem during reboot. It's what
> tells fsck -A which filesystems to check. If we don't expect the
> filesystem to be check-able during that phase, a non-zero value won't
> have any real meaning.
I'm now beginning to understand why SuSE wanted fsck -M/-m (ignore
mounted filesystems). Looks like SuSE has a very strange and
non-standard usage scenario with fsck -A which is *not* just at
boot-time.
So before we try to figure out whether Yet Another FSCK option makes
sense, maybe it would be good to get an explanation exactly *how* SuSE
is using fsck -A, besides just at boot-time?
- Ted
next prev parent reply other threads:[~2008-03-06 17:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 13:41 [PATCH] [RFC] New fsck option to ignore device-mapper crypto devices Matthias Koenig
2008-03-06 14:32 ` Dave Kleikamp
2008-03-06 17:04 ` Matthias Koenig
2008-03-06 17:23 ` Dave Kleikamp
2008-03-06 17:42 ` Theodore Tso [this message]
2008-03-07 14:20 ` Matthias Koenig
2008-03-07 15:19 ` Dave Kleikamp
2008-03-12 15:59 ` Matthias Koenig
2008-03-12 20:02 ` Theodore Tso
2008-03-12 20:14 ` Theodore Tso
2008-03-13 5:37 ` Dave Kleikamp
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=20080306174220.GH18188@mit.edu \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=ludwig.nussel@suse.de \
--cc=mkoenig@suse.de \
--cc=shaggy@linux.vnet.ibm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox