From: Dave Chinner <david@fromorbit.com>
To: "Török Edwin" <edwin@skylable.com>
Cc: Karanvir Singh <karanvir.singh@hgst.com>,
Brian Foster <bfoster@redhat.com>,
Eric Sandeen <sandeen@sandeen.net>,
Luca Gibelli <luca@skylable.com>,
xfs@oss.sgi.com,
Christopher Squires <christopher.squires@hgst.com>,
Wayne Burri <wayne.burri@hgst.com>
Subject: Re: PROBLEM: XFS on ARM corruption 'Structure needs cleaning'
Date: Sat, 13 Jun 2015 08:52:09 +1000 [thread overview]
Message-ID: <20150612225209.GA20262@dastard> (raw)
In-Reply-To: <557AD4D4.3010901@skylable.com>
On Fri, Jun 12, 2015 at 03:47:16PM +0300, Török Edwin wrote:
> On 06/12/2015 03:21 PM, Brian Foster wrote:
> > I echo Dave's suggestion down thread with regard to toolchain. This
> > kernel was compiled with the following cross-gcc (installed via Fedora
> > package):
> >
> > gcc version 4.9.2 20150212 (Red Hat Cross 4.9.2-5) (GCC)
> >
> > Are you using something different?
>
> /proc/version says:
>
> Linux version 3.14.3-00088-g7651c68 (jenkins@boulder-jenkins) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #24 Thu Apr 9 16:13:46 MDT 2015
>
> I'll get back to you when I have a new kernel running.
Yup, that's looking like a toolchain bug. Thread about arm directory
read corruption:
http://oss.sgi.com/archives/xfs/2013-02/msg00505.html
cross-gcc version results:
http://oss.sgi.com/archives/xfs/2013-02/msg00563.html
"A quick rundown:
-cross-gcc4.4: OK
-cross-gcc4.5: OK
-cross-gcc4.6: BAD
-cross-gcc4.7: BAD
-cross-gcc4.8: OK"
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-12 22:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 6:23 PROBLEM: XFS on ARM corruption 'Structure needs cleaning' Török Edwin
2015-06-11 15:16 ` Brian Foster
2015-06-11 15:28 ` Török Edwin
2015-06-11 15:51 ` Eric Sandeen
2015-06-11 15:58 ` Eric Sandeen
2015-06-11 16:32 ` Török Edwin
2015-06-11 17:10 ` Eric Sandeen
2015-06-11 17:13 ` Török Edwin
2015-06-11 17:16 ` Eric Sandeen
2015-06-11 20:07 ` Eric Sandeen
2015-06-11 20:29 ` Eric Sandeen
2015-06-11 22:53 ` Dave Chinner
2015-06-12 12:21 ` Brian Foster
2015-06-12 12:47 ` Török Edwin
2015-06-12 13:54 ` Brian Foster
2015-06-12 20:19 ` Eric Sandeen
[not found] ` <BLUPR04MB593340A765596780F266454F2BB0@BLUPR04MB593.namprd04.prod.outlook.com>
2015-06-13 13:55 ` Török Edwin
2015-06-12 22:52 ` Dave Chinner [this message]
2015-08-12 0:56 ` katsuki.uwatoko
2015-08-12 3:14 ` Dave Chinner
2015-08-12 6:19 ` katsuki.uwatoko
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=20150612225209.GA20262@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.com \
--cc=christopher.squires@hgst.com \
--cc=edwin@skylable.com \
--cc=karanvir.singh@hgst.com \
--cc=luca@skylable.com \
--cc=sandeen@sandeen.net \
--cc=wayne.burri@hgst.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox