From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: v3.10: unmount won't work
Date: Fri, 17 May 2013 20:08:49 +0200 [thread overview]
Message-ID: <51967231.1040509@gmx.de> (raw)
In-Reply-To: <51954640.5050709@redhat.com>
On 05/16/2013 10:49 PM, Eric Sandeen wrote:
> 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. ;)
yes - I'm calling for trouble and I get it - but by this (uncommon) scenario few real NFSv4 and UML bugs were found.
> Can you narrow down which syscalls cause the problem?
Till now not to a single one (would be nice, I know).
Currently I observed that issue not with host kernel 3.9, but with host kernel 3.10-rc1.
Furthermore on the UML guest trinity has to be run long enough (hours) to produce warnings like :
# zgrep "v4 server returned" /var/log/messages* | cut -f3- -d' '
kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 0c6a41f0!
kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 3fe4fa60!
kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 4143f790!
kernel: NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence 48f401f0!
...
> Is this the very first umount call . . . ?
yes, before that probably the NFS service was either restarted or just halted.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
--
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
next prev parent reply other threads:[~2013-05-17 18:08 UTC|newest]
Thread overview: 13+ 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 20:09 ` Toralf Förster
2013-05-14 21:12 ` Eric Sandeen
2013-05-16 20:23 ` Toralf Förster
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
2013-05-17 18:08 ` Toralf Förster [this message]
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=51967231.1040509@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.