Bug#352420: lvm2 + udev: some trouble at shutdown ?
Hello Marco,
Sorry for delay but have annoying pb to access my mail ;-(
On Feb 12, Joel Soete [EMAIL PROTECTED] wrote:
I would just like to understand with you why this above steps ('umounting
local fs') did also 'umount /dev', as it seems to be the reason of next
trouble.
The udev package does not do this.
Thinking again about it, this may be caused by a recently-fixed bug in
initscripts. Please check.
Yes fixed by latest distupgrade this Monday morning ;-)
[...]
Will now deactivate swap.
swapoff on /dev.Orig/md/1
swapoff on /dev/md/1
Done deactivating swap.
Will now unmount local filesystems.
/dev/vg00/lv_var umounted
/dev/vg00/lv_src umounted
/dev/vg00/lv_tmp umounted
/dev/vg00/lv_home umounted
Could not find /dev.Orig/.static/dev in mtab
/dev.Orig/.static/dev umounted
/dev.Orig/md/0 umounted
/dev/vg_raid5/lv_sources umounted
/dev/vg_raid5/lv_develop umounted
/dev/vg_raid5/lv_debapt umounted
Done unmounting local filesystems.
Shutting down LVM Volume Groups...
Failed to read VG data from PV (/dev/sdb1)
Failed to read VG data from PV (/dev/sdb1)
Failed to read VG data from PV (/dev/sdb1)
Failed to read VG data from PV (/dev/sdb1)
Unable to find volume group root_vg
0 logical volume(s) in volume group vg_raid5 now active
0 logical volume(s) in volume group vg00 now active
Mounting root filesystem read-only...done.
Will now restart.
md: stopping all md devices.
md: md4 switched to read-only mode.
md: md1 switched to read-only mode.
md: md2 still in use.
md: md3 switched to read-only mode.
md: md0 switched to read-only mode.
Restarting system.
.
Cool ;-)
Tx,
Joel
PS: amoung ...'The following packages will be upgraded:
[...]
112 upgraded, 6 newly installed, 0 to remove and 2 not upgraded.
### Mon Feb 13 08:45:36 2006 ###
Setting up sysvinit (2.86.ds1-12) ...
Setting up base-files (3.1.10) ...
Installing new version of config file /etc/nsswitch.conf ...
Setting up initscripts (2.86.ds1-12) ...
Installing new version of config file /etc/init.d/bootclean ...
Installing new version of config file /etc/init.d/bootlogd ...
Installing new version of config file /etc/init.d/checkroot.sh ...
Installing new version of config file /etc/init.d/halt ...
Installing new version of config file /etc/init.d/mountall.sh ...
Installing new version of config file /etc/init.d/umountfs ...
Setting up sysv-rc (2.86.ds1-12) ...
Setting up module-init-tools (3.2.2-2) ...
Setting up modutils (2.4.27.0-4) ...
Setting up makedev (2.3.1-80) ...
.udevdb presence implies active udev. Aborting MAKEDEV invocation.
.udevdb presence implies active udev. Aborting MAKEDEV invocation.
.udevdb presence implies active udev. Aborting MAKEDEV invocation.
.udevdb presence implies active udev. Aborting MAKEDEV invocation.
Setting up libdevmapper1.02 (1.02.03-1) ...
Loading device-mapper support.
Setting up libdevmapper-dev (1.02.03-1) ...
Setting up dmsetup (1.02.03-1) ...
Setting up udev (0.084-4) ...
Installing new version of config file /etc/udev/devfs.rules ...
Installing new version of config file /etc/udev/udev.rules ...
Installing new version of config file /etc/init.d/udev ...
Setting up devscripts (2.9.13) ...
Setting up intltool (0.34.2-1) ...
[...]
DistUpgrade finished this: Monday 2006-02-13 :-)
So, all related pkg (udev, lvm2+dm, sysvinit, ...) were updated: hard to
figured out the detailed fix ;-(
--
ciao,
Marco
---
NOTE! My email address is changing to ... @scarlet.be
Please make the necessary changes in your address book.
Bug#352420: lvm2 + udev: some trouble at shutdown ?
On Feb 12, Joel Soete [EMAIL PROTECTED] wrote:
I would just like to understand with you why this above steps ('umounting
local fs') did also 'umount /dev', as it seems to be the reason of next
trouble.
The udev package does not do this.
Thinking again about it, this may be caused by a recently-fixed bug in
initscripts. Please check.
--
ciao,
Marco
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#352420: lvm2 + udev: some trouble at shutdown ?
Package: udev Version: 0.084-3 Severity: normal Hi all, Desperating that lvm will ever offer the 'encapsulation' of /boot in lvm like hpux does), i am trying to install a more common lvm+raid1 boot disk with following scheme: boot disk will be build on raid1 + lv, i.e: o the / (aka root), /boot, swap will be purely raid1 (as recommended) o the rest /home, /var, /tmp will be in LVs over raid1 (to get benefit of resizing LVM facilities) ps: raid1 base is still necessary because against announces LVM is not yet able to manage its own raid1 stuff ;-( Additional data (/Develop, /Sources, /DebApt, /MultiCd, ...) will stand on LVs over a software raid5 array of 6*4Gb disk (i.e. 5 + 1 spare) New Boot disk slicing: # cfdisk /dev/sdc cfdisk 2.12p Disk Drive: /dev/sdc Size: 9104953344 bytes, 9104 MB Heads: 64 Sectors per Track: 32 Cylinders: 8683 NameFlags Part Type FS Type [Label]Size (MB) -- sdc1Primary Linux/PA-RISC boot 32.51 sdc2Primary Linux raid autodetect 132.13 sdc3Primary Linux raid autodetect 395.32 sdc5Logical Linux raid autodetect 2097.16 sdc6Logical Linux raid autodetect 6447.70 RAID1 md creation: # mdadm --verbose --create --auto=md /dev/md/boot --level 1 --raid-devices=2 missing /dev/sdc2 # mdadm --verbose --create --auto=md /dev/md/swap --level 1 --raid-devices=2 missing /dev/sdc3 # mdadm --verbose --create --auto=md /dev/md/root --level 1 --raid-devices=2 missing /dev/sdc5 # mdadm --verbose --create --auto=md /dev/md/more_root --level 1 --raid-devices=2 missing /dev/sdc6 # mdadm --detail --scan ARRAY /dev/md3 level=raid1 num-devices=2 UUID=5582e410:c46bda68:e41d50bc:80ce6ffa ARRAY /dev/md2 level=raid1 num-devices=2 UUID=be276566:ca577e05:310f9b03:b6edb13a ARRAY /dev/md1 level=raid1 num-devices=2 UUID=0e8ef8a9:93230c78:30dfa3c5:7033b63d ARRAY /dev/md0 level=raid1 num-devices=2 UUID=28b23a65:5a30a02b:dc1d7564:0f051b08 # ll /dev/md/ total 26 drwxr-xr-x 2 root root 1024 Jan 25 17:55 . drwxr-xr-x 8 root root 24576 Jan 25 17:40 .. brw--- 1 root root 9, 0 Jan 25 16:18 boot brw--- 1 root root 9, 3 Jan 25 17:43 more_root brw--- 1 root root 9, 4 Jan 25 17:55 raid5 brw--- 1 root root 9, 2 Jan 25 16:17 root brw--- 1 root root 9, 1 Jan 25 16:14 swap # ll /dev/md[01234] brw-rw 1 root disk 9, 0 Jan 25 15:23 /dev/md0 == boot brw-rw 1 root disk 9, 1 Jan 25 15:23 /dev/md1 == swap brw-rw 1 root disk 9, 2 Jan 24 18:22 /dev/md2 == root brw-rw 1 root disk 9, 3 Jan 25 15:23 /dev/md3 == more_root brw-rw 1 root disk 9, 4 Jan 24 18:22 /dev/md4 == raid5 LVM2 filter configuration - in /etc/lvm/lvm.conf comment all filter and add a custom one to accept only /dev/md/*: # Custom: only /dev/md/* ;-) filter = [ a|/dev/md/*|, r/.*/ ] # pvcreate /dev/md/more_root Physical volume /dev/md/more_root successfully created # vgcreate vg00 /dev/md/more_root Volume group vg00 successfully created # lvcreate -L 512M -n /dev/vg00/lv_var Logical volume lv_var created # lvcreate -L 128M -n /dev/vg00/lv_tmp Logical volume lv_tmp created # lvcreate -L 128M -n /dev/vg00/lv_home Logical volume lv_home created # for /usr/src # lvcreate -L 2G -n /dev/vg00/lv_src Logical volume lv_src created Creating FS (swap + ext3) = # mkswap /dev/md/swap (why not activate it and check) # swapon /dev/md/swap # swapon -s # mke2fs -j /dev/md/boot # mke2fs -j /dev/md/root # mke2fs -j /dev/vg00/lv_var # mke2fs -j /dev/vg00/lv_tmp # mke2fs -j /dev/vg00/lv_home # mke2fs -j /dev/vg00/lv_src Everything was mounted successfully and a copy of my running system is now finished. No familiar with initramfs, I prefer to try first without this. I temporaly use some work-around to reboot the stuff: adding following line to links.conf: M md0 b 9 0 M md1 b 9 1 M md2 b 9 2 M md3 b 9 3 M md4 b 9 4 D md M md/0 b 9 0 M md/1 b 9 1 M md/2 b 9 2 M md/3 b 9 3 M md/4 b 9 4 M md/boot b 9 0 M md/swap b 9 1 M md/root b 9 2 M md/more_root b 9 3 M md/raid5 b 9 4 :-) All seems ok after that but now encountered some anoying trouble at shutdown: [...] Unmounting local filesystems...umount2: Device or resource busy umount: /dev.Orig busy - remounted read-only done. Shutting down LVM Volume Groups... [...] Unable to unlink device node for 'vg_raid5-lv_develop'
Bug#352420: lvm2 + udev: some trouble at shutdown ?
reassign 352420 lvm2 thanks On Feb 11, Joel Soete [EMAIL PROTECTED] wrote: I do not know what this means, I am not even sure that you are using udev since /dev is supposed to be writeable for the whole shutdown process. But if installing lvm breaks something, then I'd start looking at lvm. Feel free to reassign the bug again if you will be able to show actual issues in the udev package. All seems ok after that but now encountered some anoying trouble at shutdown: [...] Unmounting local filesystems...umount2: Device or resource busy umount: /dev.Orig busy - remounted read-only done. Shutting down LVM Volume Groups... [...] Unable to unlink device node for 'vg_raid5-lv_develop' /dev/vg_raid5/lv_develop: unlink failed: Read-only file system Unable to unlink device node for 'vg_raid5-lv_sources' /dev/vg_raid5/lv_sources: unlink failed: Read-only file system Unable to unlink device node for 'vg_raid5-lv_debapt' /dev/vg_raid5/lv_debapt: unlink failed: Read-only file system 0 logical volume(s) in volume group vg_raid5 now active Unable to unlink device node for 'vg00-lv_var' /dev/vg00/lv_var: unlink failed: Read-only file system Unable to unlink device node for 'vg00-lv_tmp' /dev/vg00/lv_tmp: unlink failed: Read-only file system Unable to unlink device node for 'vg00-lv_home' /dev/vg00/lv_home: unlink failed: Read-only file system Unable to unlink device node for 'vg00-lv_src' /dev/vg00/lv_src: unlink failed: Read-only file system 0 logical volume(s) in volume group vg00 now active -- ciao, Marco signature.asc Description: Digital signature
