[lug] mount: unknown filesystem type 'lvm2pv'

Lee Woodworth blug-mail at duboulder.com
Thu Jun 5 11:22:35 MDT 2008

Sean Reifschneider wrote:
> Bill Thoen wrote:
>> # ls
>> LogVol00  LogVol01
>> # mount /dev/VolGroup01/LogVol01 /mnt/d
>> /dev/mapper/VolGroup01-LogVol01 looks like swapspace - not mounted
> That error message is pretty clear: you're trying to mount a logical volume
> that contains swap.  This is not the droid you are looking for.  Is there
> another LV listed in /dev/VolGroup01 or /dev/mapper, maybe something like
> /dev/VolGroup01/LogVol00?
Use swapon -s to see what swap devices are in use. A Sean said, the errors
you've shown suggest that /dev/VolGroup01/LogVol01 is being used as swap space.

FYI: LVM uses Physical Volumes (PV) as containers for physical blocks, often
a partition but it could be a whole disk. Use the pvs command from the lvm2
package to see what is active.

A Volume Group (VG) is logical container of blocks that can be allocated. A VG
can use multiple PVs. Use the vgs command to see them.

A logical Volume (LV) is logically contiguous set of blocks that functions like
a partition. The blocks for the LV come from a specific VG. Use the lvs command
to see what LVs are active.

To make sure lvm scans and activates everything it finds:
    vgchange -ay

> lvm2pv
> BTW: lvm2pv means the partition you are trying to mount is a LVM Version 2
> Physical Volume -- the partitions that make up a logical volume.
Sean, I'm curious to know what causes the file system type for an LV
to be reported as lvm2pv?

> Sean
Web Page:  http://lug.boulder.co.us
Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
Join us on IRC: lug.boulder.co.us port=6667 channel=#colug

More information about the LUG mailing list