From: Nathan Scott <nathans@sgi.com>
To: "Jeffrey E. Hundstad" <jeffrey.hundstad@mnsu.edu>
Cc: Mattias Hedenskog <ml@magog.se>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS breakage in 2.6.18-rc1
Date: Thu, 20 Jul 2006 09:01:09 +1000 [thread overview]
Message-ID: <20060720090109.F1947140@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <44BE48D5.7020107@mnsu.edu>; from jeffrey.hundstad@mnsu.edu on Wed, Jul 19, 2006 at 09:59:33AM -0500
On Wed, Jul 19, 2006 at 09:59:33AM -0500, Jeffrey E. Hundstad wrote:
> I did try the xfs_repair 2.8.4 for a volume running on 2.6.17.4 and it
> annihilated the volume. This volume was not showing signs of crashing.
> So... I guess I would certainly not run xfs_repair unless there is good
> reason.
Erm, wha..? Can you expand on "annihilated" a bit? (please send
me the full xfs_repair output if you still have it).
thanks.
--
Nathan
next parent reply other threads:[~2006-07-19 23:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67dc30140607190717r57ed2fe5w719dcca896110d8@mail.gmail.com>
[not found] ` <44BE48D5.7020107@mnsu.edu>
2006-07-19 23:01 ` Nathan Scott [this message]
2006-07-20 5:51 ` XFS breakage in 2.6.18-rc1 Jeffrey Hundstad
[not found] <20060718222941.GA3801@stargate.galaxy>
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-19 21:14 ` 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-25 20:16 ` Jan Engelhardt
2006-07-25 23:10 ` 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
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=20060720090109.F1947140@wobbly.melbourne.sgi.com \
--to=nathans@sgi.com \
--cc=jeffrey.hundstad@mnsu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=ml@magog.se \
--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