All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Chris Friesen <chris.friesen@genband.com>
Cc: Ben Myers <bpm@sgi.com>, Alex Elder <elder@kernel.org>, xfs@oss.sgi.com
Subject: Re: 2.6.27-based kernel failing xfstests xfs/182
Date: Tue, 14 May 2013 10:45:21 +1000	[thread overview]
Message-ID: <20130514004521.GP32675@dastard> (raw)
In-Reply-To: <519176E7.8070204@genband.com>

On Mon, May 13, 2013 at 05:27:35PM -0600, Chris Friesen wrote:
> 
> Hi,
> 
> I'm working on an embedded system running a 2.6.27-based kernel.
> 
> I'm digging into some intermittent xfs corruption issues.  Yes, I
> realize the right answer is probably to upgrade, but for the usual
> embedded reasons that's tricky.
> 
> I'm seeing test xfs/182 fail with 40 or so files showing messages like:
> 
> file /opt/xfstest2/960 has incorrect size - sync failed
> 
> In our case the xfs filesystems used for testing are on top of lvm,
> which is in turn on top of two SAS drives in RAID1.
> 
> Any suggestions on where I should start looking?  I'm looking at the
> "do_sync() and XFSQA test 182 failures...." thread on the mailing
> list from 2008, can someone point me to the commit that eventually
> resulted from that?

I doubt anyone can pinpoint a fix for you. I'd suggest that you find
the kernel release where the test starts passing, and the work
backwards from there...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-05-14  0:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 23:27 2.6.27-based kernel failing xfstests xfs/182 Chris Friesen
2013-05-14  0:45 ` Dave Chinner [this message]
2013-05-15 21:57 ` 2.6.27-based kernel failing xfstests xfs/182 -- resolved, I think Chris Friesen

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=20130514004521.GP32675@dastard \
    --to=david@fromorbit.com \
    --cc=bpm@sgi.com \
    --cc=chris.friesen@genband.com \
    --cc=elder@kernel.org \
    --cc=xfs@oss.sgi.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.