| To: | Patrick Shirkey <pshirkey@xxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: file corruption issue |
| From: | Ben Myers <bpm@xxxxxxx> |
| Date: | Tue, 15 May 2012 10:13:31 -0500 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <64776.110.174.53.110.1337043522.squirrel@xxxxxxxxxxxxxxxxx> |
| References: | <51509.110.174.53.110.1336699622.squirrel@xxxxxxxxxxxxxxxxx> <20120511165012.GC16099@xxxxxxx> <59946.110.174.53.110.1336959906.squirrel@xxxxxxxxxxxxxxxxx> <20120514142948.GS3963@xxxxxxx> <64776.110.174.53.110.1337043522.squirrel@xxxxxxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.20 (2009-06-14) |
On Tue, May 15, 2012 at 02:58:42AM +0200, Patrick Shirkey wrote: > Unfortunately I cannot unmount the partition/s to run xfs_metadump because > they are in use. > > I have found some files that were truncated on a recent crash. Is there > any tool I can run on those files to get info that might be useful? Hrm.. xfs_bmap output could be helpful so we can see the block map. Do you know how big they are supposed to be? How much was truncated? Unfortunately since you don't know which database will have the corruption... you'll need to get xfs_bmap output for all of them, and then after a crash get the 'after'. Is that a possibility? -Ben |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re-Validierung Ihre E-Mail-Konto, E-MAIL |
|---|---|
| Next by Date: | Re: [PATCH 2/2 V2] xfstests 273: fix of reading scratch size and removing lost+found, Eric Sandeen |
| Previous by Thread: | Re: file corruption issue, Patrick Shirkey |
| Next by Thread: | Re: file corruption issue, Patrick Shirkey |
| Indexes: | [Date] [Thread] [Top] [All Lists] |