Mailinglist Archive: opensuse (4570 mails)

< Previous Next >
LVM mounting order - complete disaster
  • From: Sunny <sloncho@xxxxxxxxx>
  • Date: Tue, 29 Nov 2005 01:24:41 +0000 (UTC)
  • Message-id: <e7eeb230511281724o7aea21aeibfd31777118fd7ec@xxxxxxxxxxxxxx>
Hi,
I have created the following setup:

sda:
sda1: /boot
sda2: /swap
sda3: LVM

i.e. all of the rest space is put in one volume group.

Now, I created volumes inside, for all my needs (i.e. /tmp, /var,
/usr, etc...). and left some free space for latter assignment.

After the system was installed and up and running, I decided to assign
the rest free space to be used by mysql.

So, I created (using yast/lvm) a new volume from the free space, set
mount point to /var/lib/mysql, set the filesystem options, everything.
Nothing special, looks exactly like all other volumes.

Yast created everything, added an entry in fstab and mounted the
volume. Perfect.

...Until reboot. This volume is not mounted on reboot. If after the
system is started I go to yast/lvm - it shows it as mounted, but it is
not. It is not displayed neither by mount, nor by df.

So, using yast/lvm, I unmount the volume, save the changes, mount it
again on the same place, save changes - and the volume is there,
mounted, with all the files.

I can reproduce this behaviour on 2 SuSE 10.0 machines.

Looks like the problem may be in that this volume is mounted at a
third level, and maybe it tries to mount it before the parent volume
is mounted at all. I have this:

vol1 -> /
vol2 -> /var
volx -> /var/lib/mysql


In fstab these mounts are listed in the right order. So I'm wondering
if there is some different mechanism for ordering which volume is
activated after which?

Thanks
--
--
Svetoslav Milenov (Sunny)

< Previous Next >
This Thread