[DragonFlyBSD - Bug #742] (In Progress) umount problems with multiple mounts

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #742 has been updated by tuxillo.

Status changed from Feedback to In Progress
Assignee set to tuxillo

Hi,

corecode pointed out I was missing an additional mount_null / /mnt in my test. After doing that I can reproduce the issue:

# df -h
Filesystem     Size   Used  Avail Capacity  Mounted on
/dev/vkd0s1a   2.0G   1.3G   558M    70%    /
devfs          1.0K   1.0K     0B   100%    /dev
procfs         4.0K   4.0K     0B   100%    /proc
/              2.0G   1.3G   558M    70%    /mnt
/var           2.0G   1.3G   558M    70%    /mnt/var
/usr           2.0G   1.3G   558M    70%    /mnt/usr
/              2.0G   1.3G   558M    70%    /mnt
# umount /mnt
unmount(0x8033214280): Cannot unmount: 2 mount refs still present
umount: unmount of /mnt failed: Device busy
# umount /mnt/var/
umount: unmount of /mnt/var failed: Invalid argument

Assigining this to myself.

Cheers,
Antonio Huete


----------------------------------------
Bug #742: umount problems with multiple mounts
http://bugs.dragonflybsd.org/issues/742#change-11781

* Author: corecode
* Status: In Progress
* Priority: Normal
* Assignee: tuxillo
* Category: Userland
* Target version: 3.8.0
----------------------------------------
hey,

yes, my fault, but:

%mount 
/dev/ad6s1a on / (ufs, local, soft-updates)
/dev/ad6s1b on /pbulk (ufs, local, soft-updates)
/ on /pbulk/clients/labospc67_1/root (null, local, read-only)
/pbulk/clients/labospc67_1/var on /pbulk/clients/labospc67_1/root/var (null, local)
/pbulk/clients/labospc67_1/tmp on /pbulk/clients/labospc67_1/root/tmp (null, local)
/pbulk/clients/labospc67_1/dev on /pbulk/clients/labospc67_1/root/dev (null, local)
/ on /pbulk/clients/labospc67_1/root (null, local, read-only)

%umount labospc67_1/root
umount: unmount of /pbulk/clients/labospc67_1/root failed: Device busy

%umount /pbulk/clients/labospc67_1/root/var
umount: unmount of /pbulk/clients/labospc67_1/root/var failed: Invalid argument

something is wrong here.  i guess I can't umount the "upper" root mount, because it takes the "lower" root mount first.  dito for the subdirs.

cheers
  simon



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account