![]() You'll have to take each case as it comes. There are other methods that block devices can be nested (fuse, loopback filesystems) that will have their own methods for determining the underlying block device, and you can even nest multiple layers so you have to work your way down. You can see that /dev/md2 is on the /dev/sda3 and /dev/sdb3 devices. To look at the components of a md device, you can use mdadm -detail or look in /proc/mdstat # df /srv Since a volume group can span multiple physical volumes, you may find that you have multiple devices listed.Īnother type of logical block device is a md (Multiple Devices, and used to be called meta-disk I think) device, such as /dev/md2. The last column tells you that the logical volume usr in the volume group orthanc ( /dev/mapper/orthanc-usr) is on the device /dev/sda3. LV VG Attr LSize Origin Snap% Move Log Copy% Convert Devices # lvs -o +devices /dev/mapper/orthanc-usr For this, you can use the lvs(8) command: # df /usr Run these commands to collect disk and LUN information from ESXi: Run the esxcli storage core path list or esxcfg-scsidevs -l command to generate a list of all LUN paths currently connected to the ESXi host. If the device is a logical volume, you will need to determine which block device(s) the logical volume is on. The first field has the device that the file or directory is on.įilesystem 1K-blocks Used Available Use% Mounted on The df(1) command will tell you the device that a file or directory is on: df /work
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |