Gerry, for the benefit of the rest of us who are depending on snapshot -
Was there much writing and/or reading going on between the time your backup was made, and the time of the hang?
I know that snapshot works by putting an extra load on every write to the origin volume. Is there any reason, known to knowledgeable LVM designers on this list, why this should lead to "hundreds of errors" when a system hang takes place? I assume stuff got caught in a half-committed state, but _hundreds_... ???
Thanks,
Larry
On 4/30/08, Gerry Reno <greno@verizon.net> wrote:
I ran e2fsck against the new logvol and it found the filesystem and the journal but
the filesystem was corrupted with hundreds of errors. At this point I just reformatted
the device and now I'm loading the backup onto it.
How do I handle the LVM metadata? The restored metadata will not be correct. Or does
LVM have a way to figure this out?
Gerry
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
_______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
