Re: mount doesn't mount on boot-up [OT]

[David G. Miller (aka DaveAtFraud)]

Tim <ignored_mailbox(a)yahoo.com.au&gt; wrote:

>  On Tue, 2006-10-31 at 20:46 -0700, David G. Miller wrote:
>    
> > > I'm guessing there is a user program such as diskdruid to change the 
> > > partition label.  Unfortunately, I don't know what it is. 
> >     
>
>  apropos label
>
>  e2label              (8)  - Change the label on an ext2/ext3 filesystem
>  findfs               (8)  - Find a filesystem by label or UUID
>  mlabel               (1)  - make an MSDOS volume label
>  ppmlabel             (1)  - add text to a PPM image
>  vol_id               (8)  - probe filesystem type and read label and uuid
>
>  man e2label 
A more correct explanation as to why I didn't know the command is I

usually don't bother with partition labels.  If I add a drive to a 
system, I've usually found it easier to just change fstab to use the 
actual device for any affected partitions.  There's probably a good 
reason to use labels instead of devices but I'm not aware of what that 
reason is.  Not sure why the OP is having problems and using the device 
in fstab doesn't seem to be working for him.  It works from the command 
line which makes no sense.

My first exposure to man pages was on HP-UX (late 1980s) so I prefer 
"man -k" to apropos.  Besides, fewer letters to type. :D

Cheers,
Dave

-- 
Politics, n. Strife of interests masquerading as a contest of principles.
-- Ambrose Bierce

mount doesn't mount on boot-up [OT]

[Tim]

On Wed, 2006-11-01 at 08:27 -0700, David G. Miller wrote:
>  I usually don't bother with partition labels.  If I add a drive
> to a 
>  system, I've usually found it easier to just change fstab to use the 
>  actual device for any affected partitions. 
/me too, twice over...

>  There's probably a good reason to use labels instead of devices
> but
>  I'm not aware of what that reason is. 
Here's one example:  If one were to be dealing with several swappable
drives (e.g. drives in those removable caddies), there's a certain
amount of ease that mounting via a volume name can be done without
having to figure out which particular /dev/hd parameter to use.  Even
more so, if you're using those drives across several computers (that's a
lot of /dev/hd variations to keep in your head).

And then there's managing a drive when the system's had a bit of a
stuff-up.  You have to peruse around to work out which partition is
which, but you can very simply use a label to mount /home, for instance,
without having to care which partition it was on.

-- 
(Currently testing FC5, but still running FC4, if that's important.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.

mount doesn't mount on boot-up [OT]

[Rick Stevens]

On Thu, 2006-11-02 at 08:46 +1030, Tim wrote:
>  On Wed, 2006-11-01 at 08:27 -0700, David G. Miller wrote:
>  > I usually don't bother with partition labels.  If I add a drive to a 
>  > system, I've usually found it easier to just change fstab to use the 
>  > actual device for any affected partitions.
>  
>  /me too, twice over...
>  
>  > There's probably a good reason to use labels instead of devices but
>  > I'm not aware of what that reason is.
>  
>  Here's one example:  If one were to be dealing with several swappable
>  drives (e.g. drives in those removable caddies), there's a certain
>  amount of ease that mounting via a volume name can be done without
>  having to figure out which particular /dev/hd parameter to use.  Even
>  more so, if you're using those drives across several computers (that's a
>  lot of /dev/hd variations to keep in your head).
>  
>  And then there's managing a drive when the system's had a bit of a
>  stuff-up.  You have to peruse around to work out which partition is
>  which, but you can very simply use a label to mount /home, for instance,
>  without having to care which partition it was on. 
If you want a stuff-up, try booting a system with two drives that have
a /usr partition label.  Your guess as to which /usr gets mounted.  It's
caused lots of grief at this end.  I know what's happening and how to
fix it, I'm just getting tired of doing it all the time.

----------------------------------------------------------------------
- Rick Stevens, Senior Systems Engineer     rstevens(a)vitalstream.com -
- VitalStream, Inc.                       http://www.vitalstream.com -
-                                                                    -
-           Vegetarian:  Old Indian word for "lousy hunter"          -
----------------------------------------------------------------------

mount doesn't mount on boot-up [OT]

[Claude Jones]

On Wed November 1 2006 8:39 pm, Rick Stevens wrote:
>  On Thu, 2006-11-02 at 08:46 +1030, Tim wrote:
>  > And then there's managing a drive when the system's had a bit of a
>  > stuff-up.  You have to peruse around to work out which partition is
>  > which, but you can very simply use a label to mount /home, for instance,
>  > without having to care which partition it was on.
>
>  If you want a stuff-up, try booting a system with two drives that have
>  a /usr partition label.  Your guess as to which /usr gets mounted.  It's
>  caused lots of grief at this end.  I know what's happening and how to
>  fix it, I'm just getting tired of doing it all the time. 
Well, I've got a stuff-up - but where's the stomach?

my fstab:

LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot1            /boot                   ext2    defaults        1 2
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
LABEL=/home             /home                   ext3    defaults        1 2
proc                    /proc                   proc    defaults        0 0
sysfs                   /sys                    sysfs   defaults        0 0
LABEL=SWAP-sda2         swap                    swap    defaults        0 0
/dev/sdc1		/home/cj/archive	ext3	defaults	1 2


message I got when booting up just now:

Nov  1 20:25:48 localhost kernel: audit(1162430744.537:6): avc:  denied  { mounton } for 
pid=2341 comm="mount" name="archive" dev=sdb1 ino=65175554
scontext=system_u:system_r:mount_t:s0 tcontext=user_u:object_r:user_home_t:s0 tclass=dir
Nov  1 20:25:48 localhost kernel: audit(1162430744.537:7): avc:  denied  { mounton } for 
pid=2341 comm="mount" name="archive" dev=sdb1 ino=65175554
scontext=system_u:system_r:mount_t:s0 tcontext=user_u:object_r:user_home_t:s0 tclass=dir

That last entry is my latest try for this drive in fstab - it's clear. The label for
that drive had been /home/cj/archive - I changed it to "bigstore"  - 
I tried using the LABEL=/bigstore method, as well. The problem is that on boot-up, my
system is trying to mount sdb1 instead of sdc1 - sdb1
has already been mounted in a previous step as /: any other ideas, anyone? 
-- 
Claude Jones
Brunswick, MD, USA

mount doesn't mount on boot-up [OT]

[Tim]

On Wed, 2006-11-01 at 17:39 -0800, Rick Stevens wrote:
>  If you want a stuff-up, try booting a system with two drives that
> have
>  a /usr partition label.  Your guess as to which /usr gets mounted.
>  It's caused lots of grief at this end.  I know what's happening and
>  how to fix it, I'm just getting tired of doing it all the time. 
Yes, it appears not a lot of thought went into handling that.  I can
see, at least, two ways it could have been done:

Ask the user:  While booting, a warning that two like-named partitions
exist, and what to do about it.  Mount one as /usr and the other as
something else.  Or just mount one of them, picking which one.

Automatically mount the first one (the one with the lowest device
number) presuming that it'll be the boot device, and that any other
drives that have been plugged in won't be.  Which leaves you with the
other drive unmounted, or having it automounted with a slightly
different name.

-- 
(Currently testing FC5, but still running FC4, if that's important.)

Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.

mount doesn't mount on boot-up [OT]

[James Wilkinson]

David G. Miller wrote:
>  There's probably a good reason to use labels instead of devices 
>  but I'm not aware of what that reason is. 
Please note that /dev/hdx device names are going away in the future --
even parallel ATA disks (IDE) will be called /dev/sdx. When this
happens, references to /dev/hdx in grub config files or /etc/fstab will
break.

The new drivers have already been merged into the Linux kernel tree, and
may be turned on for Fedora Core 7.

See http://lwn.net/Articles/198344/ for more details.

-- 
E-mail:     james@ | That brought a lump to the eye and a tear to the throat.
aprilcottage.co.uk |     -- "I'm Sorry, I Haven't A Clue", BBC Radio 4