[Bug 769634] New: /proc/mounts shows bind mount as '/boot\040(deleted)'
https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c0 Summary: /proc/mounts shows bind mount as '/boot\040(deleted)' Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: ms@suse.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- inside the initrd when I mount the boot partition to /mnt/boot_bind and after that I bind mount that to /mnt/boot: mount --bind /mnt/boot_bind/boot /mnt/boot it looks ok until you chroot into /mnt chroot /mnt cat /proc/mounts and you can see some strange characters resulting in that the kernel doesn't know about a /boot bind mount including all strange effects afterwards I'm going to workaround this but it's a regression in the kernel imho because you don't see that on 3.2 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c Jeff Mahoney <jeffm@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jeffm@suse.com AssignedTo|kernel-maintainers@forge.pr |mszeredi@novell.com |ovo.novell.com | Severity|Major |Critical -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c1 Miklos Szeredi <mszeredi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO CC| |mszeredi@novell.com InfoProvider| |ms@suse.com --- Comment #1 from Miklos Szeredi <mszeredi@novell.com> 2012-07-11 20:16:47 UTC --- I can't see any changes between 3.2 and 3.4 that could have changed behavior of /proc/mounts. The "(deleted)" suffix means that the file or directory has been unlinked. In the above example it will happen if the "boot" directory is removed. It shouldn't change because of a chroot. Once the directory is removed you should see it in /proc/mounts outside and inside the chroot. Can you please confirm the above? -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c2 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ms@suse.com | --- Comment #2 from Marcus Schaefer <ms@suse.com> 2012-07-12 08:23:43 UTC --- 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 umount /boot mv /boot_bind/boot /boot_bind/tmp mv /boot_bind/tmp/* /boot_bind rmdir /boot_bind/tmp umount /boot_bind rmdir /boot_bind mount $imageBootDevice /boot ---------- when I prevent the 'chroot rootfs' and code the rest with the right paths the problem does not appear. -- 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.
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.
https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c4 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|ms@suse.com | --- Comment #4 from Marcus Schaefer <ms@suse.com> 2012-07-12 09:24:54 UTC --- yes this is what I'd like to express in my initial comment. The umount to /boot said it's already mounted or busy. But without any other action proc/mounts showed this "deleted" flag. It was enough to do: mount -> bind-mount -> chroot -> umount -> [ busy and the deleted flag ] -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c5 Miklos Szeredi <mszeredi@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |ms@suse.com --- Comment #5 from Miklos Szeredi <mszeredi@novell.com> 2012-07-12 09:42:48 UTC --- (In reply to comment #4)
yes this is what I'd like to express in my initial comment. The umount to /boot said it's already mounted or busy. But without any other action proc/mounts showed this "deleted" flag. It was enough to do:
mount -> bind-mount -> chroot -> umount -> [ busy and the deleted flag ]
What type of filesystem is being mounted? Can you please attach the following: /proc/mounts before the umount /proc/mounts after the umount strace of umount -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=769634 https://bugzilla.novell.com/show_bug.cgi?id=769634#c6 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|ms@suse.com | Resolution| |WORKSFORME --- Comment #6 from Marcus Schaefer <ms@suse.com> 2012-07-12 10:55:23 UTC --- *grmbl* what should I say. I rebuild everything to reproduce and to provide you with the requested data and the bug doesn't appear anymore with RC1 3.4.4-1.1 works fine sorry for the noise -- 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.
participants (1)
-
bugzilla_noreply＠novell.com