Accident: fscky -y on a compatibility volume

Hello, my name is Leonardo and I have the following problem:

I caused fsck -y to be run on a compatibility volume on the actual
partition (/dev/hda1), and now EVMS can't find the PV that was on that
partition; I assume fsck tried to regenerate what it saw as a damaged
ext2 partition, and in the process, erased the EVMS metadata.
How can I regenerate that metadata?

Thanks for your help.

Here's some more information on what I did, in case the above lacks context:

I have a container with a few EVMS and compatibility volumes. A few of
the compatibility volumes (I hope I'm getting the terminology right)
are ext2 partitions.
Some time ago, I wanted to copy my EVMS partitions to another drive to
try some risky ideas, and I absolutely forgot about /dev/evms versus
/dev/; that is, I forgot I should have tried to copy
/dev/evms/PARTITION instead of /dev/PARTITION.
The problem is I used Gparted for copying, which, without being asked,
does fsck -y on partitions it operates on.
And here's the core of the problem; I think fsck ruined the EVMS
metadata somehow, and now I can't use the PV from EVMS.

Again, any help would be very appreciated.

Leonardo

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Evms-devel mailing list
[email protected]
To subscribe/unsubscribe, please visit:
https://lists.sourceforge.net/lists/listinfo/evms-devel