| To: | David Chinner <dgc@xxxxxxx> |
|---|---|
| Subject: | Re: Strange XFS issue on tiny-NAS ARM NFS server |
| From: | "Talpey, Thomas" <Thomas.Talpey@xxxxxxxxxx> |
| Date: | Fri, 16 Mar 2007 07:30:28 -0400 |
| Cc: | "Talpey, Thomas" <Thomas.Talpey@xxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20070315225959.GO6095633@melbourne.sgi.com> |
| References: | <EXNANE01iR9Odutox7n000000c6@exnane01.hq.netapp.com> <45F85BFA.1070505@sandeen.net> <EXNANE01yeKzGZuNY1S000000cb@exnane01.hq.netapp.com> <EXNANE01pH71yEXUIEA000000d3@exnane01.hq.netapp.com> <20070315225959.GO6095633@melbourne.sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
At 06:59 PM 3/15/2007, David Chinner wrote: >On Thu, Mar 15, 2007 at 07:34:37AM -0400, Talpey, Thomas wrote: >> 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... >That's a long way past the end of the partition. > >Tom, did you run xfs_repair on that filesystem after >running with a busted compiler? Who knows how >it broke stuff on disk..... No, this was a freshly rebuilt ~80GB xfs. I was running a test on it over NFS which wrote and read 500MB files repeatedly. And, it ran for quite some time before failing. I haven't had a chance to track it down at all. Tom. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Should xfs_repair take this long?, Thomas Walker |
|---|---|
| Next by Date: | Re: XFS on Redhat4 U4, Geir A. Myrestrand |
| Previous by Thread: | Re: Strange XFS issue on tiny-NAS ARM NFS server, David Chinner |
| Next by Thread: | cache+barriers vs cache+nobarriers vs disabled cache+barriers vs disabled cache+nobarriers, Leon Kolchinsky |
| Indexes: | [Date] [Thread] [Top] [All Lists] |