Re: Corrupted FS after recovery. Coincidence?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Jamie Thompson <jamierocks@xxxxxxxxx> wrote:

>Here's the strange thing, it recovered very quickly, which I thought
>was 
>nice, but I wonder if it created a problem, as about an hour later I 
>started getting errors in my logs:

I'm not an expert in these things, but I would guess the following:
You re-added the partition instead of the drive, the MD metadata was at the end of the drive (same position regardless of whether it was a partition or a whole drive), and so MD just did a resync. However, the first section of the drive, or the offset of all data (from the beginning of the drive) was now wrong. You probably needed to clear the metadata on the drive before adding the partition to the array.

Someone else might confirm the above, but my suspicion is based on the fact that the resync was so quick (used the bitmap from the whole drive instead of making a new one for the partition).

PS, I'm glad you were able to get all your data back, though you should probably verify that nothing was corrupted in the process, perhaps from a backup restore and file comparison....

Regards,
Adam

Regards,
Adam

-- 
Adam Goryachev
Website Managers
Phone: 02 8304 0000
www.websitemanagers.com.au
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux