| To: | xfs@xxxxxxxxxxx |
|---|---|
| Subject: | Unexpected inode type 0160000 causes abort of xfs_repair |
| From: | Jonathan Groll <lists@xxxxxxxxxxx> |
| Date: | Wed, 22 Nov 2006 22:08:11 +0200 |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.9i (Linux mail 2.4.29-linode39-1um i686) |
I'm unsuccesfully trying to repair an XFS filesystem xfs_repair /dev/md1 and the same with -L both end with bad (negative) size -2150115811482766770 on inode 1539849750 cleared inode 1539849750 bad magic number 0x859b on inode 1539849751, resetting magic number bad version number 0xffffff88 on inode 1539849751, resetting version number Unexpected inode type 0160000 inode 1539849751 Aborted OS: debian sarge (stable) Kernel: 2.6.15.7 xfsprogs 2.8.11-1 Is there anything I can possibly do? Many thanks, Jonathan Groll |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Unexpected inode type 0160000 causes abort of xfs_repair, Jonathan Groll |
|---|---|
| Next by Date: | Re: XFS CORRUPTION 2.6.17.13?, Russell Cattelan |
| Previous by Thread: | Re: Unexpected inode type 0160000 causes abort of xfs_repair, Jonathan Groll |
| Next by Thread: | Review: Reduce in-core superblock lock contention near ENOSPC, David Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |