public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Matthias Koenig <mkoenig@suse.de>
Cc: Dave Kleikamp <shaggy@linux.vnet.ibm.com>,
	ludwig.nussel@suse.de, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] [RFC] New fsck option to ignore device-mapper crypto devices
Date: Wed, 12 Mar 2008 16:14:55 -0400	[thread overview]
Message-ID: <20080312201455.GF15804@mit.edu> (raw)
In-Reply-To: <20080312200236.GE15804@mit.edu>

On Wed, Mar 12, 2008 at 04:02:36PM -0400, Theodore Tso wrote:
> So here's another way you could do things that doesn't require any
> patches to fsck at all.  Just add "comment=crypto" into the option
> field of /etc/fstab, like this.  
> 
> /dev/mapper/crypto-frobnitz /crypto1           ext3    comment=crypto  1 1
> 
> Then you can skip filesystems that have the comment=crypto in the
> options field via:
> 
>      fsck -AR -t opts=!comment=crypto

Oh by the way, in case you haven't tried this, the best way to test
exactly what fsck will do with a set of arguments is by using the -NV
options, i.e.:

      fsck -ARNV -t opts=!comment=crypto

						- Ted

  reply	other threads:[~2008-03-12 20:14 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
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 [this message]
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=20080312201455.GF15804@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