public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: David Chinner <dgc@sgi.com>,
	Russell Cattelan <cattelan@thebarn.com>,
	xfs@oss.sgi.com
Subject: Re: XFS CORRUPTION 2.6.17.13?
Date: Fri, 24 Nov 2006 10:55:25 +1100	[thread overview]
Message-ID: <20061123235525.GD11034@melbourne.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611231816340.18083@p34.internal.lan>

On Thu, Nov 23, 2006 at 06:18:00PM -0500, Justin Piszcz wrote:
> Ah,
> 
> I did not make a copy unfortunatley.

It was too much to hope for :/

> I used the default mkfs.xfs settings from Knoppix 4.0.2 I believe, 
> whatever version of xfsprogs it has for a 400GB drive.

Ok, so 256 byte inodes then. A single bad buffer write is possible
then.

> Any idea how it could have been 'trashed' in one way?  It appeared to 
> occur shortly after boot-up, which then a backup occurs (heavy I/O) to a 
> remote box via NFS.

No idea - I was hoping to get a clue by looking at the raw corrupted
data if you still had it around.....

Cheers,

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

      reply	other threads:[~2006-11-23 23:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-20 20:00 XFS CORRUPTION 2.6.17.13? Justin Piszcz
2006-11-20 20:50 ` Justin Piszcz
2006-11-22 21:41 ` Russell Cattelan
2006-11-23 16:40   ` Justin Piszcz
2006-11-23 23:07     ` David Chinner
2006-11-23 23:18       ` Justin Piszcz
2006-11-23 23:55         ` David Chinner [this message]

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=20061123235525.GD11034@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=cattelan@thebarn.com \
    --cc=jpiszcz@lucidpixels.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