https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c3 Miklos Szeredi <mszeredi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ms@suse.com --- Comment #3 from Miklos Szeredi <mszeredi@novell.com> 2012-07-12 09:09:26 UTC --- (In reply to comment #2)
Hmm, no as far as I can see boot is not removed. What happens more detailed is this:
---------------
==> mount boot device to boot_bind in new rootfs
mount $imageBootDevice /rootfs/boot_bind
... maybe access data from origin boot location ... all done temporarly bind mount boot_bind to boot to not confuse other tools e.g mkinitrd
mount --bind /rootfs/boot_bind/boot /rootfs/boot
==> chroot to new rootfs and cleanup
chroot rootfs
Here
umount /boot
/rootfs/boot is umounted. Why is it still in /proc/mounts? Likely because the umount failed with EBUSY. Can you please confirm? If I'm right, then we need to find out why it is busy. It could be a kernel or a userspace issue.
mv /boot_bind/boot /boot_bind/tmp mv /boot_bind/tmp/* /boot_bind
This
rmdir /boot_bind/tmp
is where /rootfs/boot is removed (even though it's been renamed). The kernel is being perfectly correct when it's showing it with the "(deleted)" suffix. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.