| To: | "Russell G. Howe" <rhowe@xxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair unable to repair a corrupt filesystem |
| From: | Nathan Scott <nathans@xxxxxxx> |
| Date: | Mon, 24 Feb 2003 18:12:37 +1100 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <20030224055532.GA21046@xxxxxxxxxxxxxxxxxxxxx> |
| References: | <20030223081255.GA14077@xxxxxxxxxxxxxxxxxxxxx> <20030223215931.GA798@frodo> <20030224033309.GA20260@xxxxxxxxxxxxxxxxxxxxx> <20030224034815.GC798@frodo> <20030224043829.GA20677@xxxxxxxxxxxxxxxxxxxxx> <20030224052759.GD798@frodo> <20030224055532.GA21046@xxxxxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.3i |
On Mon, Feb 24, 2003 at 05:55:32AM +0000, Russell G. Howe wrote: > On Mon, Feb 24, 2003 at 04:27:59PM +1100, Nathan Scott wrote: > > Can you run the same (first) xfs_db command I sent to print > > out the inode, except change the 2222 to 6296608? I wonder > > if these two inodes are pointing at the same extents... > > Sure thing: > > http://rhowe.sfarc.net/xfs_db_inode_6296608.txt > Taa. Hmmm, they look like distinct files, with completely disjoint extents (which is good). I'll still try to revisit this locally, but if you don't need to keep them, you should be able to blow these files away by writing zeroes into the nextents and size fields (in a similar way to the way you did nblocks overwrite earlier with xfs_db). cheers. -- Nathan |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: upgrade scenario for samba server, Simon Matter |
|---|---|
| Next by Date: | RE: upgrade scenario for samba server, Spyros Ioakim |
| Previous by Thread: | Re: xfs_repair unable to repair a corrupt filesystem, Nathan Scott |
| Next by Thread: | Re: xfs_repair unable to repair a corrupt filesystem, Russell G. Howe |
| Indexes: | [Date] [Thread] [Top] [All Lists] |