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
