devfs
[Top] [All Lists]

Re: devfs superblock error

To: sullivan <sullivan@xxxxxxxxxxxxxx>
Subject: Re: devfs superblock error
From: Richard Gooch <rgooch@xxxxxxxxxxxxxxx>
Date: Thu, 26 Apr 2001 23:06:35 -0600
Cc: devfs@xxxxxxxxxxx
In-reply-to: <20010423234901.E1209@xxxxxxxxxxxxxxxxxxxxx>
References: <OF1AC99DA0.79281072-ON85256A37.0061BF8D@xxxxxxxxxxxxxxx> <20010423234901.E1209@xxxxxxxxxxxxxxxxxxxxx>
Sender: owner-devfs@xxxxxxxxxxx
sullivan@xxxxxxxxxxxxxx writes:
>  On a 2.4.3 kernel I built with devfs configured but not
>  auto mounted at boot time. I intended to manually mount
>  it onto /devfs to play around with it. On reboot I received a
>  message saying that my ext2 superblock was corrupted.
>  
>  After looking closer I noticed that my /etc/fstab was
>  configured with the fs_spec field set to LABEL=/
>  
>  Unfortunately when the fsck utility was run it
>  used the entries provided in /proc/partitions to open
>  and read partition label information to find a match.
>  Since devfs was compiled in, the /proc/partitions entries
>  contain the devfs names (ie. scsi/host0/bus0/target0/lun0/part1).
>  But since devfs wasn't mounted at boot, these entries didn't exist
>  (only the old /dev nodes are present), causing the error to
>  be reported :(
>  
>  In /etc/fstab, replacing LABEL=/ with /dev/sda1 allowed
>  fsck to skip the label matching code and run successfully :)
>  
>  Richard, could you add a note to your doc (maybe by the
>  devfs=nomount details) to warn users to avoid using the
>  LABEL directive in their fstab?

Done.

                                Regards,

                                        Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current:   rgooch@xxxxxxxxxxxxxxx

<Prev in Thread] Current Thread [Next in Thread>