From: Nick Bowler <nbowler@draconx.ca>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, jlayton@poochiereds.net
Subject: Re: PROBLEM: nfs I/O errors with sqlite applications
Date: Mon, 12 Oct 2015 23:01:36 -0400 [thread overview]
Message-ID: <20151013030136.GA7081@draconx.ca> (raw)
In-Reply-To: <20151012194647.GJ28755@fieldses.org>
[-- Attachment #1: Type: text/plain, Size: 2187 bytes --]
On 2015-10-12 15:46 -0400, J. Bruce Fields wrote:
> On Mon, Oct 12, 2015 at 03:25:38PM -0400, bfields wrote:
> > On Mon, Oct 12, 2015 at 12:48:56PM -0400, Nick Bowler wrote:
> > > I'm having a problem where, eventually, the nfs-mounted home directory
> > > on one of my machines starts failing in a kind of weird way. The issue
> > > appears to affect only sqlite; I have two applications that I know of
> > > which use it:
> > >
> > > - Firefox, where the symptom is that the browser just hangs randomly,
> > > - gmpc, which crashes immediately on startup with I/O error.
> > >
> > > Once the issue occurs these applications remain permanently broken.
> > > Since the latter is easier to test, I can run it in strace, and the
> > > failing syscall seems to be:
> > >
> > > fcntl(7, F_SETLK, {type=F_RDLCK, whence=SEEK_SET, start=1073741824, len=1}) = -1 EIO (Input/output error)
> > >
> > > When the issue occurs, the client dmesg log is full of messages of the form:
> > >
> > > [3441972.381211] NFS: v4 server returned a bad sequence-id error on an unconfirmed sequence ffff88007612ae20!
> > >
> > > There are no unusual messages on the server.
[...]
> > I wonder if there's some way to make this reproduce more quickly, for
> > example by running something that makes more aggressive use of sqlite,
> > or running multiple copies of such a thing simultaneously. Might be
> > interesting to know what the pattern of file opens and locking looks
> > like (so stracing one of those applications might help).
I could try doing something like using the sqlite3 command-line tool to
do a lot of database operations, and hope I can reproduce. I'd have to
reboot to test though.
I attached a full strace log (gzipped) from a failing process. The
command run is:
sqlite3 newfile.sqlite vacuum
which fails in a similar manner to gmpc.
> Oh, also I forgot to ask what version of the NFS protocol you're using
> (4.0, 4.1, or 4.2).
Looks like 4.0:
athena:/home on /home type nfs4 (rw,relatime,vers=4.0,rsize=524288,wsize=524288,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=krb5,clientaddr=192.168.0.207,local_lock=none,addr=192.168.0.10)
Cheers,
Nick
[-- Attachment #2: sqlite3-vacuum-strace.log.gz --]
[-- Type: application/octet-stream, Size: 2458 bytes --]
next prev parent reply other threads:[~2015-10-13 3:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 16:48 PROBLEM: nfs I/O errors with sqlite applications Nick Bowler
2015-10-12 19:25 ` J. Bruce Fields
2015-10-12 19:46 ` J. Bruce Fields
2015-10-13 3:01 ` Nick Bowler [this message]
2015-10-13 10:52 ` Jeff Layton
2015-10-13 12:54 ` Nick Bowler
2016-07-29 16:43 ` Nick Bowler
2016-07-29 17:52 ` Jeff Layton
2017-06-06 16:46 ` Lutz Vieweg
2017-06-07 3:08 ` NeilBrown
2017-06-08 18:36 ` Lutz Vieweg
2017-06-08 22:07 ` NeilBrown
2017-06-09 11:01 ` Lutz Vieweg
2017-06-09 22:01 ` NeilBrown
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=20151013030136.GA7081@draconx.ca \
--to=nbowler@draconx.ca \
--cc=bfields@fieldses.org \
--cc=jlayton@poochiereds.net \
--cc=linux-nfs@vger.kernel.org \
/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).