| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Re: 2.6.24-rc3 oopses while mounting fs |
| From: | KELEMEN Peter <Peter.Kelemen@xxxxxxx> |
| Date: | Mon, 3 Dec 2007 23:02:00 +0100 |
| In-reply-to: | <47537709.9040406@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> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
* Lachlan Mcilroy (lachlan@xxxxxxx) [20071203 14:24]: Lachlan, > Okay, sounds like it might be a corrupt log. Yep. > Can you run xfs_logprint on the device or saved log? Sure. http://cern.ch/fuji/lxfsre1103/xfs_logprint1.txt.bz2 It aborted though, with the following message: xfs_logprint: unknown log operation type (343b) Bad data in log > Also give xfs_logprint -t -i a go. http://cern.ch/fuji/lxfsre1103/xfs_logprint2.txt.bz2 > You've saved the log into a file? You can get the filesystem > mounted again by deleting the log with xfs_repair -L <dev>. > You'll probably need to run xfs_repair over the filesystem to be > safe. I conserved this filesystem away for further analysis, I'm not sure how helpful it can be. Thanks, Peter -- .+'''+. .+'''+. .+'''+. .+'''+. .+'' Kelemen PÃter / \ / \ Peter.Kelemen@xxxxxxx .+' `+...+' `+...+' `+...+' `+...+' |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Patch] xfs_lowbit64 broken on ia32, David Chinner |
|---|---|
| Next by Date: | Re: 2.6.24-rc3 oopses while mounting fs, Timothy Shimmin |
| Previous by Thread: | Re: 2.6.24-rc3 oopses while mounting fs, Lachlan McIlroy |
| Next by Thread: | Re: 2.6.24-rc3 oopses while mounting fs, Timothy Shimmin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |