public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Barry Naujok" <bnaujok@melbourne.sgi.com>
To: 'Jonathan Groll' <lists@groll.co.za>, xfs@oss.sgi.com
Subject: RE: Unexpected inode type 0160000 causes abort of xfs_repair
Date: Fri, 24 Nov 2006 10:58:08 +1100	[thread overview]
Message-ID: <200611232353.KAA09617@larry.melbourne.sgi.com> (raw)
In-Reply-To: <20061123131405.GA27453@groll.co.za>

Yes, this patch will be incorporated in the next xfsprogs update.

And yes, it did blast the inode away, as it wasn't really an inode (or
very very corrupted if it was). 

> -----Original Message-----
> From: Jonathan Groll [mailto:lists@groll.co.za] 
> Sent: Friday, 24 November 2006 12:14 AM
> To: Barry Naujok; xfs@oss.sgi.com
> Subject: Re: Unexpected inode type 0160000 causes abort of xfs_repair
> 
> On Thu, Nov 23, 2006 at 11:51:11AM +1100, Barry Naujok wrote:
> > Can you try the attached patch and see how xfs_repair goes? 
> 
> Many thanks, the patch worked like a charm! Is it going to be
> incorporated into the package in future?
> 
> Luckily I didn't have to blast the inode away, but I suspect that is
> exactly what the effect of the patch was ;-)
> 
> Thanks again,
> Jonathan

  reply	other threads:[~2006-12-20 18:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-22 20:11 Unexpected inode type 0160000 causes abort of xfs_repair Jonathan Groll
2006-11-23  5:39 ` Chris Wedgwood
     [not found] ` <200611230047.LAA09023@larry.melbourne.sgi.com>
2006-11-23 13:14   ` Jonathan Groll
2006-11-23 23:58     ` Barry Naujok [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-23  0:55 Barry Naujok
2006-11-22 20:08 Jonathan Groll

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=200611232353.KAA09617@larry.melbourne.sgi.com \
    --to=bnaujok@melbourne.sgi.com \
    --cc=lists@groll.co.za \
    --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