From: Eric Sandeen <sandeen@sandeen.net>
To: "Brian Foster" <bfoster@redhat.com>, "Török Edwin" <edwin@skylable.com>
Cc: Christopher Squires <christopher.squires@hgst.com>,
Karanvir Singh <karanvir.singh@hgst.com>,
Wayne Burri <wayne.burri@hgst.com>,
Luca Gibelli <luca@skylable.com>,
xfs@oss.sgi.com
Subject: Re: PROBLEM: XFS on ARM corruption 'Structure needs cleaning'
Date: Fri, 12 Jun 2015 15:19:41 -0500 [thread overview]
Message-ID: <557B3EDD.3030502@sandeen.net> (raw)
In-Reply-To: <20150612135404.GC60661@bfoster.bfoster>
On 6/12/15 8:54 AM, Brian Foster wrote:
>>> I managed to get an updated kernel on a beaglebone I had sitting around,
>>> but I don't reproduce any errors with the "corrupted" image (I think
>>> we've established that the image is fine on-disk and something is going
>>> awry at runtime):
>>>
>>> root@beaglebone:~# uname -a
>>> Linux beaglebone 3.14.1+ #5 SMP Thu Jun 11 20:58:02 EDT 2015 armv7l GNU/Linux
>>> root@beaglebone:~# mount ./xfs2.test.corrupted /mnt/
>>> root@beaglebone:~# ls -al /mnt/a/
>>> total 12
>>> drwxr-xr-x 3 root root 14 Jun 11 16:11 .
>>> drwxr-xr-x 3 root root 14 Jun 11 16:11 ..
>>> drwxr-x--- 2 root root 8192 Jun 11 16:11 b
>>> root@beaglebone:~# ls -al /mnt/a/b/
>>> total 17996
>>> drwxr-x--- 2 root root 8192 Jun 11 16:11 .
>>> drwxr-xr-x 3 root root 14 Jun 11 16:11 ..
>>> -rw-r--r-- 1 root root 12288 Jun 11 16:11 events.db
>>> -rw-r--r-- 1 root root 15360 Jun 11 16:11 f00000000.db
>>> -rw-r--r-- 1 root root 15360 Jun 11 16:11 f00000001.db
>>> -rw-r--r-- 1 root root 15360 Jun 11 16:11 f00000002.db
>>> -rw-r--r-- 1 root root 15360 Jun 11 16:11 f00000003.db
>>> ...
>>> root@beaglebone:~#
>>>
>>> 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.
>>
>
> Ok. FWIW, I just tried rebuilding with the following 4.6.3 toolchain:
>
> https://www.kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.3/x86_64-gcc-4.6.3-nolibc_arm-unknown-linux-gnueabi.tar.xz
>
> ... and still didn't reproduce any errors. Of course, this probably
> doesn't have whatever patches and whatnot might be included in the
> distro 4.6.3 toolchain. It could be worth a try depending on what
> happens with a newer kernel, though.
FWIW, I tried mounting the corrupted image and running the ls on
Fedora 22, kernel 4.0.4-303.fc22.armv7hl, gcc version 5.1.1, and had no
problems there either.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-12 20:19 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 [this message]
[not found] ` <BLUPR04MB593340A765596780F266454F2BB0@BLUPR04MB593.namprd04.prod.outlook.com>
2015-06-13 13:55 ` Török Edwin
2015-06-12 22:52 ` Dave Chinner
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=557B3EDD.3030502@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bfoster@redhat.com \
--cc=christopher.squires@hgst.com \
--cc=edwin@skylable.com \
--cc=karanvir.singh@hgst.com \
--cc=luca@skylable.com \
--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