| To: | Anastas Giokov <antzi@xxxxxxxxxx> |
|---|---|
| Subject: | Re: Problem repairing XFS |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Fri, 10 Sep 2004 11:26:40 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20040909090323.DE1791BCFC@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| References: | <20040909090323.DE1791BCFC@xxxxxxxxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
On Thu, Sep 09, 2004 at 05:03:23AM -0400, Anastas Giokov wrote: > > Hi! > > After a disk problem (bad sectors) I have the following problem: > > Using xfs_repair on the device I receive the following message: > > corrupt inode XXXXX (btree). Unmount and run xfs_repair. > fatal error -- 990 - couldn't iget disconnected inode > > The device is unmounted at this point and re-running xfs_repair dives the > same output. The resulting fs is mountable, but part of it is not recovered. > > Is there a way to "skip" the corrupt inode, so the repair can finish, even > losing some data? You can use xfs_db to zero inodes/directories by hand... or fix the repair bug, but thats a more difficult undertaking. cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Courier-imap] Courier Imap 3.0.7 rpmbuild fails with xfs->lvm2->md1, Nathan Scott |
|---|---|
| Next by Date: | TAKE 907752 - acl update, Nathan Scott |
| Previous by Thread: | Re: Problem repairing XFS, Net Llama! |
| Next by Thread: | TAKE 921118 - growfs on realtime, Nathan Scott |
| Indexes: | [Date] [Thread] [Top] [All Lists] |