public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: "Talpey, Thomas" <Thomas.Talpey@netapp.com>
Cc: xfs@oss.sgi.com
Subject: Re: Strange XFS issue on tiny-NAS ARM NFS server
Date: Fri, 16 Mar 2007 09:59:59 +1100	[thread overview]
Message-ID: <20070315225959.GO6095633@melbourne.sgi.com> (raw)
In-Reply-To: <EXNANE01pH71yEXUIEA000000d3@exnane01.hq.netapp.com>

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
> ><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

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.....

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-03-15 23:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 16:11 Strange XFS issue on tiny-NAS ARM NFS server Talpey, Thomas
2007-03-14 20:32 ` Eric Sandeen
2007-03-14 21:19   ` Talpey, Thomas
2007-03-14 21:21     ` Eric Sandeen
2007-03-14 21:31       ` Talpey, Thomas
2007-03-15 11:34     ` Talpey, Thomas
2007-03-15 22:59       ` David Chinner [this message]
2007-03-16 11:30         ` Talpey, Thomas

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=20070315225959.GO6095633@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=Thomas.Talpey@netapp.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