On Wed, Jun 27, 2007 at 01:24:02PM +0200, Andras Simon wrote: > On 6/27/07, Luciano Rocha <strange@xxxxxxxxxxxxx> wrote: > > And it should, when the mount command specified the option loop. From > > the manual: > > > > THE LOOP DEVICE > > The umount command will free the loop device (if any) associated > > with the mount, in case it finds the option 'loop=...' in /etc/mtab, > > or when the -d option was given. Any pending loop devices can be > > freed using 'losetup -d', see losetup(8). > > > > My umount works correctly, with or without offset. > > You're right! I shouldn't have stopped reading man umount at the first > mention of loop. OTOH, it seems like it's a mount and not an umount > bug, because the relevant entry in /etc/mtab > > /dev/loop0 /mnt fuseblk rw,nosuid,nodev,noatime,allow_other,blksize=4096 0 0 > > doesn't have the 'loop=...' option. So umount is in its rights not to > free the loop device. > Er, could you do an ls -ld /etc/mtab? That looks like /proc/mounts, not the userland created /etc/mtab. Or it could be that the fuse wrapper doesn't do the right thing, I haven't tested any fuse filesystem, just standard iso. -- lfr 0/0
Attachment:
pgpx5DXc8HqHk.pgp
Description: PGP signature
