| To: | Lukas Hejtmanek <xhejtman@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs_repair |
| From: | Frank Hellmann <frank@xxxxxxxxxxxxx> |
| Date: | Sat, 08 Jan 2005 15:46:51 +0100 |
| Cc: | linux-xfs@xxxxxxxxxxx, frank@xxxxxx |
| In-reply-to: | <20050106230232.GE2313@mail.muni.cz> |
| Organization: | Optical Art Film- und Special-Effects GmbH |
| References: | <20050106224742.GB2313@mail.muni.cz> <26743c105010614583c2d5499@mail.gmail.com> <20050106230232.GE2313@mail.muni.cz> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla Thunderbird 0.8 (X11/20040926) |
Hi Lukas! If you have a chance, do a copy (via dd) to an empty disk before trying to recover anything and use that copied disk for playing around. Rebuilds tend to start at the beginning of the disks and go sequentially further on. So my first guess is that the partition table is corrupt and will give xfs_repair strange partition layouts back. If you have any idea how it was laid out, I would suggest to restore it to the original layout, via fdisk or the like. After that try an xfs_repair and now it should be able to find a suitable superblock. For the data I would fear that there will be a _lot_ of corrupted/missing files now. As they say: RAID is _not_ a backup... Anyway, good luck for the recovery. Cheers,
Frank...Lukas Hejtmanek wrote: On Thu, Jan 06, 2005 at 11:58:16PM +0100, Mathieu Betrancourt wrote:
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: TAKE 904196 - Merge up to 2.6.10., Jason White |
|---|---|
| Next by Date: | TAKE 923968 - Move support code for NFS exporting to a conditionally built file, Christoph Hellwig |
| Previous by Thread: | Re: xfs_repair, Lukas Hejtmanek |
| Next by Thread: | oops with software raid, lvm, xfs, nfs and smp, Phil Dier |
| Indexes: | [Date] [Thread] [Top] [All Lists] |