public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chatterton <chatz@melbourne.sgi.com>
To: Nathan Scott <nathans@sgi.com>, Christian Kujau <evil@g-house.de>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS breakage in 2.6.18-rc1
Date: Sun, 30 Jul 2006 08:28:05 +1000	[thread overview]
Message-ID: <44CBE0F5.3050201@melbourne.sgi.com> (raw)
In-Reply-To: <20060729202223.GD20039@charite.de>



Ralf Hildebrandt wrote:
> * Nathan Scott <nathans@sgi.com>:
> 
>> Barry sent an xfs_repair patch to resolve this issue to the xfs@oss.sgi.com
>> list yesterday; please give that a go and let us know how it fares.
> 
> Just to let you know, I did a cvs checkout of xfs-cmds
> as described on http://oss.sgi.com/projects/xfs/source.html
> 
> Then I saved the patch from
> http://oss.sgi.com/archives/xfs/2006-07/msg00374.html using the
> "Original" link on hat page.
> 
> I build a xfs_Repair binary using that, transferred it onto an old
> KLAX boot cd I had and repaired the XFS root on my laptop.
> 
> I got 5000 files in lost and found, mostly the whole manpages from my
> system. Had to reinstall a few packages to restore lost binaries, but
> that's all.
> 
> When will that horrible bug be fixed in 2.6.x? 
> 

The bug is fixed in 2.6.17.7.

David

  reply	other threads:[~2006-07-29 22:28 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 22:29 XFS breakage in 2.6.18-rc1 Torsten Landschoff
2006-07-18 22:57 ` Nathan Scott
2006-07-19  8:08   ` Alistair John Strachan
2006-07-19 22:56     ` Nathan Scott
2006-07-20 10:29       ` Kasper Sandberg
2006-07-19 10:21   ` Kasper Sandberg
2006-07-19 12:43     ` Alistair John Strachan
2006-07-19 15:25       ` Kasper Sandberg
2006-07-19 22:59     ` Nathan Scott
2006-07-20  7:13     ` FAQ updated (was Re: XFS breakage...) Nathan Scott
2006-07-20 12:42       ` Hans-Peter Jansen
2006-07-20 13:28       ` David Greaves
2006-07-20 16:11         ` Chris Wedgwood
2006-07-20 22:14           ` Nathan Scott
2006-07-20 22:18             ` Justin Piszcz
2006-07-20 22:24               ` Nathan Scott
2006-07-20 22:43                 ` Justin Piszcz
2006-07-20 22:52                   ` Nathan Scott
2006-07-20 22:55                     ` Justin Piszcz
2006-07-20 22:57                       ` Justin Piszcz
2006-07-20 23:00                       ` Nathan Scott
2006-07-20 23:10                         ` Justin Piszcz
2006-07-20 23:12                           ` Chris Wedgwood
2006-07-20 23:15                             ` Justin Piszcz
2006-07-20 23:19                             ` Nathan Scott
2006-07-20 15:13       ` Kevin Radloff
2006-07-20 16:51         ` Alistair John Strachan
2006-07-31 16:25       ` Jan Kasprzak
2006-07-31 16:38         ` Justin Piszcz
2006-08-02  4:32         ` Nathan Scott
2006-07-19 21:14   ` XFS breakage in 2.6.18-rc1 Torsten Landschoff
2006-07-19 23:09     ` Nathan Scott
2006-07-22 16:27   ` Christian Kujau
2006-07-23 23:01     ` Nathan Scott
2006-07-28 17:01       ` Christian Kujau
2006-07-28 21:48         ` Nathan Scott
2006-07-29 20:22           ` Ralf Hildebrandt
2006-07-29 22:28             ` David Chatterton [this message]
2006-07-18 23:06 ` Kevin Radloff
  -- strict thread matches above, loose matches on Subject: below --
2006-07-19 14:17 Mattias Hedenskog
2006-07-19 14:59 ` Jeffrey E. Hundstad
2006-07-19 23:01   ` Nathan Scott
2006-07-20  5:51     ` Jeffrey Hundstad
2006-07-19 21:09 ` Torsten Landschoff
2006-07-20 10:46   ` Jan Engelhardt

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=44CBE0F5.3050201@melbourne.sgi.com \
    --to=chatz@melbourne.sgi.com \
    --cc=evil@g-house.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nathans@sgi.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