Bugzilla – Bug 135876
LVM mounting at boot not correct (missing mounts)
Last modified: 2005-11-29 23:25:01 UTC
I have Adaptec SCSI RAID mirror (hardware) configuration with 2 hdds. The logical device is seen by SuSE as sda. I have created the following partitions: sda1 - /boot - ext2 - 100MB sda2 - swap - 2GB sda3 - LVM - it contains these volumes and their mounting points: /dev/system/home │ 2.0 GB│ │/home│ /dev/system/mysql│ 40.0 GB│ │/var/lib/mysql│ /dev/system/root │ 1.0 GB│ │/ │ /dev/system/srv │ 2.0 GB│ │/srv │ /dev/system/suse │ 9.0 GB│ │/suse│ /dev/system/tmp │ 500.0 MB│ │/tmp │ /dev/system/usr │ 2.0 GB│ │/usr │ /dev/system/var │ 2.0 GB│ │/var Now, the problem is, that after reboot /dev/system/mysql is not mounted. It has it's entry in fstab, there is no difference between this one volume and anyone else. mount and df does not show it after reboot. If I start yast, then go to LVM, and edit this volume to remove it's mount point, save the changes, and than edit it again to assign a mount point - the volume is mounted OK. Until the next reboot. I guess it is because it's mount point is actually 3rd level and it tries to mount it before / or /var are mounted. I did not find any docs about possible limitations, so I guess what I do is right, and there is a bug in the way LVMs are mounted on boot. Or ... if there is a way to explicitly set the order of mounting? Please, let me know if you need more info for the system. Btw, I see this behavior on another similar system (Again hardware RAID mirror, SuSE 10.0 x86-64, LVM). Cheers Sunny
The mount order is defined by /etc/fstab. If /var/lib/mysql is listen before /var move it after /var. Does this fix the issue? If yes, did you manually edit /etc/fstab before? If no, please provide complete /etc/fstab.
Created attachment 59011 [details] the fstab of the affected machine The fstab order looks OK. Never edited by hand. Cheers Sunny
Some addition: as you see in fstab, I need this particular volume to be mounted as owned by mysql:mysql. If I remove these options (uid, gid), upon restart the volume is mounted. So looks like the bug is there. Cheers Sunny
Sorry guys, overlooked here. The fs is ext3, and uid and gid options are not supported. This fails the mount. Cheers, and thanks for the rapid engagement with the report.