| To: | Frank Hellmann <frank@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair Err 990 |
| From: | Eric Sandeen <sandeen@xxxxxxx> |
| Date: | Fri, 03 Jun 2005 11:57:11 -0500 |
| Cc: | XFS List <linux-xfs@xxxxxxxxxxx> |
| In-reply-to: | <42A05FD8.8070809@opticalart.de> |
| References: | <42A05FD8.8070809@opticalart.de> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 1.0 (X11/20041206) |
Frank Hellmann wrote:
corrupt dinode 2537480171, extent total = 1, nblocks = 0. Unmount and run xfs_repair. Anything I can do to fix this via xfs_db? Like hiding that part from the users until I have a chance to do the xfs_dump+mkfs.xfs+xfs_restore routine? I've fixed this sort of thing before by using db to set both extents and nblocks to 0 for that inode, and re-running repair. I think. :) -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: TAKE 937235 - mkfs vs MD0/1, Martin K. Petersen |
|---|---|
| Next by Date: | right su and sw values for raid 10, Ed |
| Previous by Thread: | xfs_repair Err 990, Frank Hellmann |
| Next by Thread: | right su and sw values for raid 10, Ed |
| Indexes: | [Date] [Thread] [Top] [All Lists] |