linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: v3.10: unmount won't work
Date: Thu, 16 May 2013 15:49:04 -0500	[thread overview]
Message-ID: <51954640.5050709@redhat.com> (raw)
In-Reply-To: <519544F5.8010703@gmx.de>

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-05-16 20:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 19:12 v3.10: unmount won't work Toralf Förster
2013-05-14 20:09 ` Toralf Förster
2013-05-14 21:12 ` Eric Sandeen
2013-05-16 20:23   ` Toralf Förster
2013-05-16 20:36     ` Eric Sandeen
2013-05-16 20:43       ` Toralf Förster
2013-05-16 20:49         ` Eric Sandeen [this message]
2013-05-17 18:08           ` Toralf Förster
2013-05-16 20:45       ` Toralf Förster
2013-05-16 20:50         ` Eric Sandeen
2013-05-16 20:50       ` Toralf Förster

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51954640.5050709@redhat.com \
    --to=sandeen@redhat.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=toralf.foerster@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).