| To: | Jonathan Groll <lists@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: Unexpected inode type 0160000 causes abort of xfs_repair |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Wed, 22 Nov 2006 21:39:14 -0800 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20061122201131.GD2493@xxxxxxxxxxx> |
| References: | <20061122201131.GD2493@xxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
On Wed, Nov 22, 2006 at 10:11:31PM +0200, Jonathan Groll wrote: > Is there anything I can possibly do? smash the inode using xfs_db (set mode to 0 should work) and run repair, it will prune it away for you |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Review: Reduce in-core superblock lock contention near ENOSPC, David Chinner |
|---|---|
| Next by Date: | Re: [PATCH] (and bad attr2 bug) - pack xfs_sb_t for 64-bit arches, Timothy Shimmin |
| Previous by Thread: | Unexpected inode type 0160000 causes abort of xfs_repair, Jonathan Groll |
| Next by Thread: | Re: Unexpected inode type 0160000 causes abort of xfs_repair, Jonathan Groll |
| Indexes: | [Date] [Thread] [Top] [All Lists] |