From: Dave Jones <davej@redhat.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: FSX on NFS blew up.
Date: Tue, 3 Oct 2006 20:51:25 -0400 [thread overview]
Message-ID: <20061004005125.GC21677@redhat.com> (raw)
In-Reply-To: <1159922770.9569.26.camel@dyn9047017100.beaverton.ibm.com>
On Tue, Oct 03, 2006 at 05:46:10PM -0700, Badari Pulavarty wrote:
> On Tue, 2006-10-03 at 20:40 -0400, Dave Jones wrote:
> > On Tue, Oct 03, 2006 at 05:34:44PM -0700, Badari Pulavarty wrote:
> > > On Tue, 2006-10-03 at 12:49 -0400, Dave Jones wrote:
> > > > Took ~8hrs to hit this on an NFSv3 mount. (2.6.18+Jan Kara's jbd patch)
> > > >
> > > > http://www.codemonkey.org.uk/junk/fsx-nfs.txt
> > >
> > > I was seeing *similar* problem on NFS mounted filesystem (while running
> > > fsx), but later realized that filesystem is full - when it happend.
> > >
> > > Could be fsx error handling problem ? Can you check yours ?
> >
> > It's running low, but there's no way it ran out. (It's down to about 4GB free).
> >
> > Dave
> >
>
> Okay... Looking at your log
>
> > Size error: expected 0x2b804 stat 0x37000 seek 0x37000
>
> filesize doesn't match. So wondering, if you have a write
> failure or filesystem full case.
The server didn't report anything nasty in its logs, and *touch wood*
hasn't had any hardware problems to date.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-10-04 0:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 16:49 FSX on NFS blew up Dave Jones
2006-10-04 0:34 ` Badari Pulavarty
2006-10-04 0:40 ` Dave Jones
2006-10-04 0:43 ` Dave Jones
2006-10-04 0:46 ` Badari Pulavarty
2006-10-04 0:51 ` Dave Jones [this message]
2006-10-04 23:34 ` Badari Pulavarty
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=20061004005125.GC21677@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@us.ibm.com \
--cc=trond.myklebust@fys.uio.no \
/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