Re: [PATCH] [RFC] New fsck option to ignore device-mapper crypto devices

[Dave Kleikamp <shaggy@linux.vnet.ibm.com>]

This is just a nitpick that doesn't change your argument at all.

On Wed, 2008-03-12 at 16:02 -0400, Theodore Tso wrote:
> On Wed, Mar 12, 2008 at 04:59:03PM +0100, Matthias Koenig wrote:
> > 1. Do we agree that fstab fs_passno could be used besides fsck -A by a 
> >    separate script to decide if a filesystem (that could not be checked 
> >    in the fsck -A phase) should be checked?
> 
> Well, historically there have been /etc/fstab entries which look like
> this:
> 
> /dev/zipdrive       /media/zipdisk   ext3 default,noauto 0 0
> 
> This is because there might not be a zip disk in the drive at the time
> of the boot.  However, a root user could insert a zip disk, and then
> run the command "fsck /dev/zipdrive" and expect it to work, and the
> follow that up with "mount /dev/zipdrive".
> 
> So passno == 0 can't mean "don't mount the filesystem, ever".  All it
> means is "don't mount it at boot".  So I don't think trying to kludge
> new fields into fs_passno is the way to go.

s/mount/check/ in the above paragraph.  passno only tells fsck what to
do.  "noauto" tells mount what to mount at boot time.

-- 
David Kleikamp
IBM Linux Technology Center