Arch Linux

WildEagle

Member

Registered: 2008-02-05

Posts: 8

[SOLVED] Problems umounting a loop file at shutdown

Hi all,
I have run out of space on /. As a temporary solution I create a 3 Gb file on a ntfs partition, formatted it as ext3 and mounted it, via loop device, as /var/tmp that is where I need additional space. All works correctly but when I shutdown the system I see an error on the ntfs partition:

umount: /mnt/ACER: device is busy.
        (In some cases useful info about processes that use
         the device is found by lsof(8) or fuser(1))

I know that the system umount partitions as they appear in /etc/fstab. Of course there is first the ntfs partition (in /mnt/ACER) and after the /mnt/ACER/vartmp.dir mounted in /var/tmp.
How can I tell to system to umount first /mnt/ACER/vartmp.dir and after the /mnt/ACER?
Thanks for your help!

Last edited by WildEagle (2008-10-21 22:04:50)

WildEagle

Member

Registered: 2008-02-05

Posts: 8

Re: [SOLVED] Problems umounting a loop file at shutdown

I searched into the /etc/rc.d dir. I found /etc/rc.d/netfs startup file who mount and umount network filesystems with these two lines:

/bin/mount -a -t nfs,nfs4,smbfs,codafs,ncpfs,cifs,shfs,fuse,fuseblk
...
umount -a -t nfs,nfs4,smbfs,codafs,ncpfs,cifs,shfs,fuse,fuseblk

I commented out the fuse,fuseblk filesystems as I mount ntfs partition with ntfs-3g which uses fuseblk.

/bin/mount -a -t nfs,nfs4,smbfs,codafs,ncpfs,cifs,shfs #,fuse,fuseblk
...
umount -a -t nfs,nfs4,smbfs,codafs,ncpfs,cifs,shfs #,fuse,fuseblk

Now it works well.