That's a quirk of LVM2, which is implemented using the device mapper instead of traditional files under /dev. If you do a long listing of /dev/VolGroup00 you'll see that where you used to see device files named, for example, lvol1, lvol2, lvol3, etc, you instead now see these same names used as symbolic links pointing to the device mapper versions. > -----Original Message----- > From: redhat-list-bounces@xxxxxxxxxx > [mailto:redhat-list-bounces@xxxxxxxxxx] On Behalf Of Johan Booysen > Sent: Thursday, August 30, 2007 10:39 AM > To: General Red Hat Linux discussion list > Subject: lvm logical volume paths > > hi all, > > my apologies if this is a stupid question. this relates to a > Red Hat Enterprise Linux Server 2.6.18-8.el5xen installation > (i know bits and pieces about linux, but have much to still learn). > > why, when i cat fstab, do i get this: > > # cat /etc/fstab > ... > ... > /dev/VolGroup00/data1 /data1 ext3 defaults > 1 2 > /dev/VolGroup00/data2 /data2 ext2 defaults > 1 2 > ... > ... > > but when doing df i get "mapper" included in the output. > > # df -h > Filesystem Size Used Avail Use% Mounted on > /dev/mapper/VolGroup00-data1 > 473G 198M 449G 1% /data1 > /dev/mapper/VolGroup00-data2 > 473G 70M 449G 1% /data2 > ... > > i'd appreciate your insights. > -- > redhat-list mailing list > unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=subscribe > https://www.redhat.com/mailman/listinfo/redhat-list > -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list
