| To: | Jason Detring <detringj@xxxxxxxxx> |
|---|---|
| Subject: | Re: Read corruption on ARM |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Tue, 26 Feb 2013 16:37:01 -0600 |
| Cc: | xfs@xxxxxxxxxxx |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <CA+AKrqBQ=VG0oVsai+agywDKRgO9cG9AvT6mCTSZxKO3Si5Aiw@xxxxxxxxxxxxxx> |
| References: | <CA+AKrqBQ=VG0oVsai+agywDKRgO9cG9AvT6mCTSZxKO3Si5Aiw@xxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 |
On 2/26/13 3:58 PM, Jason Detring wrote: > Hello list, <snip> > This also seems to impact the Raspberry Pi. Below shows a 256 MB test > case filesystem. > The filesystem was created on an x86-64 box by mkfs.xfs 3.1.8 and > populated by kernel 3.6.9. > This failure report is Linux 3.6.11-g89caf39 built by GCC 4.7.2 from > <https://github.com/raspberrypi/linux/commits/rpi-3.6.y> > The problem appears to be tied to the filesystem, not the media, > since both an external USB reader and a loopback-mounted image on the > unit's main SD media show the same backtrace. The loopback image was > captured on other hardware, then copied onto the RPi via network. Missed this; let me fire up my pi and see if I can replicate it. -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Read corruption on ARM, Eric Sandeen |
|---|---|
| Next by Date: | Re: Read corruption on ARM, Eric Sandeen |
| Previous by Thread: | Re: Read corruption on ARM, Dave Chinner |
| Next by Thread: | Re: Read corruption on ARM, Eric Sandeen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |