| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: 2.6.24-rc3 oopses while mounting fs |
| From: | KELEMEN Peter <Peter.Kelemen@xxxxxxx> |
| Date: | Tue, 4 Dec 2007 10:42:29 +0100 |
| In-reply-to: | <47549B1A.4070508@sgi.com> |
| Mail-followup-to: | xfs@xxxxxxxxxxx |
| Organization: | CERN European Laboratory for Particle Physics, Switzerland |
| References: | <20071128134523.GF7793@luba> <474E003A.7020000@sgi.com> <20071130223154.GB13589@luba> <47537709.9040406@sgi.com> <20071203220200.GC13667@luba> <47549B1A.4070508@sgi.com> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
* Timothy Shimmin (tes@xxxxxxx) [20071204 11:11]:
Timothy,
Thanks for the recommendations.
> Often it is simplest to save the log using the -C option to a
> file. -C filename [...] The log can then be analysed in various
> ways later.
I did that (I played with it and did the same thing with dd(1),
too).
> If you want to save the filesystem away for possible metadata
> debugging later, then xfs_metadump is your friend.
I'll check this out. I watched Barry implement the thing but we
were stuck in the past for a while with xfsprogs-2.6.x.
Peter
--
.+'''+. .+'''+. .+'''+. .+'''+. .+''
Kelemen PÃter / \ / \ Peter.Kelemen@xxxxxxx
.+' `+...+' `+...+' `+...+' `+...+'
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: 2.6.24-rc3 oopses while mounting fs, KELEMEN Peter |
|---|---|
| Next by Date: | Re: [Patch] xfs_lowbit64 broken on ia32, Lachlan McIlroy |
| Previous by Thread: | Re: 2.6.24-rc3 oopses while mounting fs, Lachlan McIlroy |
| Next by Thread: | TAKE update acl/attr man pages re symlinks, Tim Shimmin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |