umountnfs should umount dependent dirs

Bug #145523 reported by SurJector on 2007-09-27
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
sysvinit (Ubuntu)
Wishlist
Unassigned

Bug Description

Binary package hint: initscripts

When umounting NFS (or networked filesystem) dirs, other "dependent
dirs" have to be unmounted as well. This includes all the dirs below an
NFS dir and all dirs which are loops over files which are mounted below
an NFS dir. The following patch attempts to correct somewhat the
situation. It is not perfect because losetup does not show the complete
filename of a loop device, but the filename that was indicated to the
kernel at loop creation.

SurJector (loic-grenie) wrote :

Here we go with the attachment

description: updated

Thanks for reporting this. I am not sure is this has been implemented yet or not, can you confirm please? Thank you.

Changed in sysvinit (Ubuntu):
importance: Undecided → Wishlist

2009/5/31 Teej <email address hidden>:
> Thanks for reporting this. I am not sure is this has been implemented
> yet or not, can you confirm please? Thank you.

    No, it has not been implemented as of initscripts v2.86.ds1-61ubuntu11
  (up to date jaunty).

      Thanks,

            SurJector

Thanks for updating us, marking Confirmed.

Changed in sysvinit (Ubuntu):
status: New → Confirmed
Toni Spets (hifi) wrote :

The usual situation I have is that I have mounted a network filesystem and over that mounted a CD-ROM image using a loop device. If I forget to unmount the loop device before I shutdown or reboot the system will hang at unmounting for a long time because of the order of unmount (nfs before loop).

To fix this issue directly, all loop devices should be unmounted first.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers