| To: | Tom Mason <tom_mason@xxxxxx> |
|---|---|
| Subject: | Re: Mount: Structure needs cleaning |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Tue, 14 Oct 2014 10:47:00 +1100 |
| Cc: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx>, Brian Foster <bfoster@xxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <EC9978C1-65B4-48B8-9C3D-980341A752E8@xxxxxx> |
| References: | <4ddef393-ad9e-49a1-80d7-9c29bcd74c8f@xxxxxx> <20141013220940.GE17506@dastard> <EC9978C1-65B4-48B8-9C3D-980341A752E8@xxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
On Mon, Oct 13, 2014 at 11:38:34PM +0100, Tom Mason wrote: > Btw - before I get rid of this old samsung 1tb drive, the folder's > properties in the failed drive actually report a lot higher for > file numbers and sizes than eventually get copied - it reports: > "Error while copying There was an error getting information about > the files in the folder 'xxxxx' no data available" ...is there a > way around this or is this my lost data? You're now into disaster recovery territory. Use ddrescue to image the filesystem, then something like photorec or some other data recovery tool to scrape the image for intact files that otherwise couldn't be pulled from the mounted filesystem. Cheers, Dave. -- Dave Chinner david@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Mount: Structure needs cleaning, Dave Chinner |
|---|---|
| Next by Date: | Re: [PATCH v4] xfs: rework zero range to prevent invalid i_size updates, Dave Chinner |
| Previous by Thread: | Re: Mount: Structure needs cleaning, Tom Mason |
| Next by Thread: | Re: Mount: Structure needs cleaning, Emmanuel Florac |
| Indexes: | [Date] [Thread] [Top] [All Lists] |