Lars Ellenberg wrote:
You are right, datavg seems OK from the device-mapper point of view.
But at filesystem level, the filesystem on datavg-snk2lv seems to be
4.0 GB but in fact it is 80 GB. My opinion is at a point in past,
device-mapper again scramled the major and minor numbers and
systemvg-usrlv overwrited datavg-snk2lv.
unlikely. it would not have changed the file system layout.
more likely, the mapping is wrong.
what do you find in /etc/lvm/backup and /etc/lvm/archive ?
those are plain text files, which store the mapping at that point in
time. compare it with the current mapping.
maybe there is something obvious in the difference...
btw, what did you find on the 253,5
which was missing from your previous device node list?
From dmsetup table output, datavg-snk2lv seems OK. How can I recover
the filesystem on it ? Or more basic question, is it possible to
recover ???
well, everything is possible :->
its more a question of time and effort...
After issuing the commands you recommended, 253,5 appeared and the
systemvg is now OK. Thanks..
Now the problem appeared to be a JFS problem. For datavg, mapping seems
to be correct, LV information and the info from dmsetup seems to be equal.
If anybody in this list have experience and can lead me
- to view the contents of the raw device (/dev/datavg/snk2lv) with
jfs-utils
- to get the filenames on the device (again with jfs-utils)
I will really appreciate..
Thank you for all your help....
*
* Suleyman Nazif Kutlu (a.k.a SNK)
* mailto: suleyman.kutlu@gmail.com
*
_______________________________________________
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/
