| To: | Jan Engelhardt <jengelh@xxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: kernel oops: trying to mount a corrupted xfs partition (2.6.16-rc3) |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Mon, 20 Feb 2006 08:29:46 +1100 |
| Cc: | bjd <bjdouma@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.61.0602171753590.27452@xxxxxxxxxxxxxxx>; from jengelh@xxxxxxxxxxxxxxx on Fri, Feb 17, 2006 at 05:54:49PM +0100 |
| References: | <20060216183629.GA5672@xxxxxxxxxxxxxxxxxxxx> <20060217063157.B9349752@xxxxxxxxxxxxxxxxxxxxxxxx> <Pine.LNX.4.61.0602171753590.27452@xxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5i |
On Fri, Feb 17, 2006 at 05:54:49PM +0100, Jan Engelhardt wrote: > >> XFS mounting filesystem hda3 > >> Starting XFS recovery on filesystem: hda3 (logdev: internal) > >> EIP: 0060:[xlog_recover_do_inode_trans+473/2688] Tainted: P VLI > > > >This indicates you are running recovery - run xfs_repair first > >if you know the filesystem is corrupt. > > > How does one know a filesystem got "corrupt enough" to require xfs_repair > first? Any corruption should be repaired. You'd notice corruption by either running repair (as the bug reporter here had asserted), or via the filesystem shutting down when the ondisk corruption was encountered. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfsdump failure - failed to get bulkstat information for root node, Christoph Hellwig |
|---|---|
| Next by Date: | PARTIAL TAKE 943272 - UUID fix, Nathan Scott |
| Previous by Thread: | Re: kernel oops: trying to mount a corrupted xfs partition (2.6.16-rc3), Jan Engelhardt |
| Next by Thread: | Re: kernel oops: trying to mount a corrupted xfs partition (2.6.16-rc3), Dave Jones |
| Indexes: | [Date] [Thread] [Top] [All Lists] |