Date: Thu, 15 Mar 2007 07:34:37 -0400
To: xfs@oss.sgi.com
From: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Subject: Re: Strange XFS issue on tiny-NAS ARM NFS server
Cc: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
In-Reply-To: <EXNANE01yeKzGZuNY1S000000cb@exnane01.hq.netapp.com>
References: <EXNANE01iR9Odutox7n000000c6@exnane01.hq.netapp.com>
 <45F85BFA.1070505@sandeen.net>
 <EXNANE01yeKzGZuNY1S000000cb@exnane01.hq.netapp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-ID: <EXNANE01pH71yEXUIEA000000d3@exnane01.hq.netapp.com>
Sender: xfs-bounce@oss.sgi.com
Errors-to: xfs-bounce@oss.sgi.com
Precedence: bulk
Content-Length: 1855
Lines: 52

Evidently that was not the only compiling issue (surprise):

><6>attempt to access beyond end of device
><6>sda3: rw=2, want=2574098408, limit=154272195
><6>attempt to access beyond end of device
><6>sda3: rw=2, want=2574098408, limit=154272195
><6>attempt to access beyond end of device
><6>sda3: rw=2, want=2574098408, limit=154272195
><6>attempt to access beyond end of device
><6>sda3: rw=0, want=2574098408, limit=154272195
><1>I/O error in filesystem ("sda3") meta-data dev sda3 block 0x996d9fe0       ("xfs_trans_read_buf") error 5 buf count 4096

Oh, well.

Tom.


At 05:19 PM 3/14/2007, Talpey, Thomas wrote:
>Wow good memory, 3 years ago:
><http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2004-March/0>20287.html>
>
>I'm compiling with gcc4.1.1 for arm5t big endian, patched for multiple
>arm ports (OpenEmbedded) and it still botches that code today.
>Works fine with the arithmetic decomposition in the message.
>And I never blame the compiler! ;-)
>
>Thanks!
>
>BTW, XFS gives this little machine a nice bump in NFS write
>bandwidth. Goes from ~6MB/sec to ~7MB/s. CPU limited, mainly.
>
>Tom.
>
>At 04:32 PM 3/14/2007, Eric Sandeen wrote:
>>Talpey, Thomas wrote:
>>> This might be pilot error, but a *very* strange thing happens with
>>> an XFS filesystem on an NFS server I'm experimenting with. This is
>>> an NSLU2 ARM-based machine, running 2.6.20.1 and an XFS filesystem
>>> freshly built on a usb-attached 2.5" drive.
>>> 
>>> Running Connectathon 04 basic tests against the server, things are
>>> fine with an EXT-formatted filesystem. However, reformatting the
>>> export as a default XFS filesystem (mkfs.xfs -f /dev/sda3), the
>>> following occurs:
>>
>>arm compiler has bugs that miscompile xfs... I think if you google arm + 
>>xfs and maybe search the list archives, you'll find a possible workaround.
>>
>>-Eric
>>
>>