On 5/16/13 3:43 PM, Toralf Förster wrote: > On 05/16/2013 10:36 PM, Eric Sandeen wrote: >> any chance you've got anything crazy going on like mounting the same loop >> file on 2 machines via an nfs export, or anything else out of the ordinary? >> > I mount that directory only from 1 UML guest and only once. > The I run a lot of trinity test in the UML guest suing that share. which apparently manages to break things - as intended. ;) Can you narrow down which syscalls cause the problem? > After that the UML guest was shutdowned. > Finally I stoped teh NFS daemon at the host. > Then I tried to unmount the the drive. > >> If you mount it and do "find -inum 32017 /mount/point" for each of the inode >> numbers below, do the files in question have anything unique going on? > > > n22 ~ # find /mnt/trinity/ -inum 32017 > > > FWIW : > > n22 ~ # umount /mnt/trinity/ > umount: /mnt/trinity: not mounted Is this the very first umount call . . . ? > n22 ~ # grep trinity /etc/mtab /proc/mounts > /etc/mtab:/dev/loop0 /mnt/trinity ext4 rw 0 0 ... because it seems to already be unmounted, if it's not in /proc/mounts (though checking for loop0 in /proc/mounts might be worthwhile too) -Eric > > -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
