/proc/dasd/devices
-Original Message-
From: Phil Tully [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 05, 2003 9:20 AM
To: [EMAIL PROTECTED]
Subject: Re: [LINUX-390] VG to Mdisk mapping ?
Neale
Thanks, PVSCAN provides the first bit of info.
Would pvscan help? It would tell you
Neale
Thanks, PVSCAN provides the first bit of info.
Would pvscan help? It would tell you the device path name and the volume
group to which it belongs.
linxken:~ # df -h
FilesystemSize Used Avail Use% Mounted on
/dev/dasda1 200M 87M 113M 44% /
/dev/vg3/tmp
cat /proc/dasd/devices | grep dasdb1
Mark Post
-Original Message-
From: Phil Tully [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 05, 2003 9:20 AM
To: [EMAIL PROTECTED]
Subject: Re: VG to Mdisk mapping ?
-snip-
How do map /dev/dasdb1 to mdisk 101?
Phil
Would pvscan help? It would tell you the device path name and the volume
group to which it belongs.
-Original Message-
Hello all,
We are trying to develop procedure for other support organizations to
monitor our Linux/Z environments. One of the problems that has popped
up was how to
Phil,
Try a 'cat /proc/dasd/devices' to see the device_name to mdisk_address
mapping.
For further mapping info of how are those logical volumes mapped onto your
physical volumes, try 'pvdata -av /dev/dasdb1'.
Ronald van der Laan
Hello all,
We are trying to develop procedure for other support organizations to
monitor our Linux/Z environments. One of the problems that has popped
up was how to drill down from a know mount point to a mdisk address.
The mapping is muddied by our use of LVM.
Any help with this would be
