You shouldn't name your lvs like pathnames as you did. It is just going to confuse you down the road. A common naming is lv_<something>. Ie lv_root. So to address the lv from lvdisplay you do vg-name/lv-name. It is not a path to a file system location. Lvdisplay only worls from that naming convention. Patrick Dupre <pd520@xxxxxxxxxx> wrote: >Thank. > >Can you do something with this: > > > > >lvdisplay /dev/VolGrpSys0/ > /dev/VolGrpSys0/root_usr: read failed after 0 of 4096 at 11534270464: >Input/output error > /dev/VolGrpSys0/root_usr: read failed after 0 of 4096 at 11534327808: >Input/output error > /dev/VolGrpSys0/root_usr: read failed after 0 of 4096 at 0: Input/output >error > /dev/VolGrpSys0/root_usr: read failed after 0 of 4096 at 4096: >Input/output error > /dev/VolGrpSys0/root_usr_lib: read failed after 0 of 4096 at 3145662464: >Input/output error > /dev/VolGrpSys0/root_usr_lib: read failed after 0 of 4096 at 3145719808: >Input/output error > /dev/VolGrpSys0/root_usr_lib: read failed after 0 of 4096 at 0: >Input/output error > /dev/VolGrpSys0/root_usr_lib: read failed after 0 of 4096 at 4096: >Input/output error > /dev/VolGrpSys0/root_usr_local: read failed after 0 of 4096 at >13627228160: Input/output error > /dev/VolGrpSys0/root_usr_local: read failed after 0 of 4096 at >13627285504: Input/output error > /dev/VolGrpSys0/root_usr_local: read failed after 0 of 4096 at 0: >Input/output error > /dev/VolGrpSys0/root_usr_local: read failed after 0 of 4096 at 4096: >Input/output error > /dev/VolGrpSys0/root_usr_src: read failed after 0 of 4096 at 6291390464: >Input/output error > /dev/VolGrpSys0/root_usr_src: read failed after 0 of 4096 at 6291447808: >Input/output error > /dev/VolGrpSys0/root_usr_src: read failed after 0 of 4096 at 0: >Input/output error > /dev/VolGrpSys0/root_usr_src: read failed after 0 of 4096 at 4096: >Input/output error > One or more specified logical volume(s) not found. > >and this ! > > > --- Logical volume --- > LV Name /dev/VolGrpSys0/root_usr > VG Name VolGrpSys0 > LV UUID AdPmoo-VyKK-3wk9-yn3u-6fTV-qdFq-2nXpel > LV Write Access read/write > LV Status available > # open 2 > LV Size 10.74 GiB > Current LE 2750 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 253:16 > > --- Logical volume --- > LV Name /dev/VolGrpSys0/root_usr_lib > VG Name VolGrpSys0 > LV UUID VcPp7o-UrE4-7Ubb-CaYd-ZIbJ-VcbI-sv362Z > LV Write Access read/write > LV Status available > # open 2 > LV Size 2.93 GiB > Current LE 750 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 253:17 > > --- Logical volume --- > LV Name /dev/VolGrpSys0/root_usr_local > VG Name VolGrpSys0 > LV UUID kXzQq6-Ikzk-xn0O-LLQu-fS0g-6Cmn-O6u0nJ > LV Write Access read/write > LV Status available > # open 2 > LV Size 12.69 GiB > Current LE 3249 > Segments 3 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 253:18 > > --- Logical volume --- > LV Name /dev/VolGrpSys0/root_usr_src > VG Name VolGrpSys0 > LV UUID ZcDrCr-MHlb-JN1b-12B1-FTu3-qzri-Z6dqd0 > LV Write Access read/write > LV Status available > # open 2 > LV Size 5.86 GiB > Current LE 1500 > Segments 1 > Allocation inherit > Read ahead sectors auto > - currently set to 256 > Block device 253:19 > > > > >> No such thing as lvm partition unless you're talking the pv. Fdisk shows your where it is, and pvdisplay gives you the details of the pv. Similar vgdisplay and lvdisplay gives you details of the logical volumes. > >Patrick Dupre <pd520@xxxxxxxxxx> wrote: > >>Hello, >> >>How can I display the partition table with lvm partitions. >>fdisk only give the lvm partition, not the details. >> >>Thank. >> >>-- >>--- >>========================================================================== >> Patrick DUPRÃ | | >> Department of Chemistry | | Phone: (44)-(0)-1904-434384 >> The University of York | | Fax: (44)-(0)-1904-432516 >> Heslington | | >> York YO10 5DD United Kingdom | | email: patrick.dupre@xxxxxxxxxx >>========================================================================== >>-- >>users mailing list >>users@xxxxxxxxxxxxxxxxxxxxxxx >>To unsubscribe or change subscription options: >>https://admin.fedoraproject.org/mailman/listinfo/users >>Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines >-- >users mailing list >users@xxxxxxxxxxxxxxxxxxxxxxx >To unsubscribe or change subscription options: >https://admin.fedoraproject.org/mailman/listinfo/users >Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines > >-- >--- >========================================================================== > Patrick DUPRÃ | | > Department of Chemistry | | Phone: (44)-(0)-1904-434384 > The University of York | | Fax: (44)-(0)-1904-432516 > Heslington | | > York YO10 5DD United Kingdom | | email: patrick.dupre@xxxxxxxxxx >========================================================================== >-- >users mailing list >users@xxxxxxxxxxxxxxxxxxxxxxx >To unsubscribe or change subscription options: >https://admin.fedoraproject.org/mailman/listinfo/users >Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
