From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Matthias Koenig <mkoenig@suse.de>
Cc: "Theodore Ts'o" <tytso@mit.edu>,
ludwig.nussel@suse.de, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] [RFC] New fsck option to ignore device-mapper crypto devices
Date: Thu, 06 Mar 2008 11:23:47 -0600 [thread overview]
Message-ID: <1204824227.7964.4.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <n7xzltbwzq3.fsf@sor.suse.de>
On Thu, 2008-03-06 at 18:04 +0100, Matthias Koenig wrote:
> Dave Kleikamp <shaggy@linux.vnet.ibm.com> writes:
> > Should field 8 of /etc/fstab (fs_passno) be zero for these mount points?
> > Is there any reason for it to be anything different?
>
> Why? zero would mean that they should never get checked.
> I think it is reasonable to have the choice to get your crypto
> filesystems checked. Current practise for SuSE has been to allow
> only 0, but checked this filesystem anyway, which has lead to complaints.
> So we want to do this more consistent.
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.
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2008-03-06 17:23 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 [this message]
2008-03-06 17:42 ` Theodore Tso
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=1204824227.7964.4.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=ludwig.nussel@suse.de \
--cc=mkoenig@suse.de \
--cc=tytso@mit.edu \
/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