Arch Linux

Try lvm2/device-mapper 2.02.83-1 from testing repo.

Lvm2 update and server rebooted.

Problem persists:
[root@namer ~]# pvdisplay
--- Physical volume ---
PV Name /dev/sda2
VG Name vgdns
PV Size 3.66 GiB / not usable 5.55 MiB
Allocatable yes
PE Size 32.00 MiB
Total PE 117
Free PE 2
Allocated PE 115
PV UUID nGxQ13-XD70-Q0bK-s7g2-fD53-aO3S-deVlOo

--- Physical volume ---
PV Name /dev/sdb1
VG Name vgdns
PV Size 15.03 GiB / not usable 30.36 MiB
Allocatable yes (but full)
PE Size 32.00 MiB
Total PE 480
Free PE 0
Allocated PE 480
PV UUID zawYYb-CrVF-3f7n-lUr3-ylTv-lLTD-zxKd9K

[root@namer ~]# pacman -Qi lvm2
Name : lvm2
Version : 2.02.83-1
URL : http://sourceware.org/lvm2/
Licenses : GPL2 LGPL2.1
Groups : base
Provides : None
Depends On : bash device-mapper>=2.02.83 udev readline
Optional Deps : None
Required By : None
Conflicts With : lvm mkinitcpio<0.5.99
Replaces : None
Installed Size : 2728.00 K
Packager : Eric Belanger <eric@archlinux.org>
Architecture : i686
Build Date : Sun 06 Feb 2011 08:04:23 PM CET
Install Date : Tue 08 Feb 2011 12:35:23 PM CET
Install Reason : Explicitly installed
Install Script : No
Description : Logical Volume Manager 2 utilities

[root@namer ~]# df /
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/dm-1 1644392 313856 1246988 [root@namer ~]# dmesg | egrep "lvr|dm-"
Kernel command line: root=/dev/mapper/vgdns-lvroot ro
device-mapper: ioctl: 4.18.0-ioctl (2010-06-29) initialised: dm-devel@redhat.com
EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (dm-1): re-mounted. Opts: (null)
EXT4-fs (dm-1): re-mounted. Opts: (null)
EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (dm-6): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)

I can also confirm this on my system

--- Physical volume ---
PV Name /dev/sda3
VG Name system
PV Size 84.20 GiB / not usable 4.02 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 21553
Free PE 21553
Allocated PE 0
PV UUID 1Rd2rD-WXPd-4V43-Rn8a-3iq9-Gzr9-KnGBVc

--- Physical volume ---
PV Name /dev/sdb1
VG Name system
PV Size 232.88 GiB / not usable 673.00 KiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 59618
Free PE 0
Allocated PE 59618
PV UUID 1SKHYW-q8GQ-mafu-DhHd-Xprk-wxsr-NzPPQ7

--- Physical volume ---
PV Name /dev/sdc1
VG Name system
PV Size 232.88 GiB / not usable 673.00 KiB
Allocatable yes
PE Size 4.00 MiB
Total PE 59618
Free PE 36248
Allocated PE 23370
PV UUID 5aXwSX-CfqT-dGol-GEyl-2RTJ-WFvP-fycHZX

As well as the root partition being renamed

--- Logical volume ---
LV Name /dev/system/root
VG Name system
LV UUID QKjbN4-3xO3-bAJC-xgzL-5tdz-92lw-i7jp5w
LV Write Access read/write
LV Status available
# open 1
LV Size 320.00 GiB
Current LE 81920
Segments 2
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0

--- Logical volume ---
LV Name /dev/system/swap
VG Name system
LV UUID 5yeEwa-OcX5-tRlJ-6jXQ-ubI5-XMEj-I6Mjul
LV Write Access read/write
LV Status available
# open 1
LV Size 4.00 GiB
Current LE 1024
Segments 1
Allocation contiguous
Read ahead sectors auto
- currently set to 256
Block device 254:1

--- Logical volume ---
LV Name /dev/system/home
VG Name system
LV UUID t41cTt-jMVO-QaHX-keSq-1u96-x1dU-MffUS9
LV Write Access read/write
LV Status available
# open 1
LV Size 176.00 MiB
Current LE 44
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2

(1:334)$ ls -l /dev/system
total 0
lrwxrwxrwx 1 root root 7 Feb 5 08:10 home -> ../dm-2
lrwxrwxrwx 1 root root 7 Feb 5 08:10 root -> ../dm-0
lrwxrwxrwx 1 root root 7 Feb 5 08:10 swap -> ../dm-1

Filesystem Size Used Avail Use% Mounted on
udev 10M 128K 9.9M 2% /dev
/dev/dm-0 320G 1.9G 319G 1% /
shm 1004M 0 1004M 0% /dev/shm
/dev/mapper/system-home
175M 2.9M 172M 2% /home
/dev/sda2 376G 1.5G 355G 1% /backups
/dev/sda1 92M 17M 70M 20% /boot

Discussion of this issue is at
https://bbs.archlinux.org/viewtopic.php?id=113025

Additional info:
lvm2 2.02.82-2

Could you please open two bug reports for two separate and entirely unrelated issues? There is nothing more annoying than having comments regarding two separate issues mixed.

First, the dm-* in df is caused by this: https://projects.archlinux.org/mkinitcpio.git/commit/?id=9ef825cedd8228957f9bdd8df7ae543afd7e0001. No idea if we should revert this, it seems inconsistent with the standard behaviour of the mount command.

Second, I don't understand the other issue at all. What is the expected behaviour here? I don't see anything wrong with this.

There you go, I didn't like this from the start:
https://projects.archlinux.org/mkinitcpio.git/commit/?id=fe843c397a42b3ae73615830392a65908ad7d973

First, I believe it is inconsistent to report a lv as dm-* device when the rest of the volumes are listed with their volume names.

Second, I believe you are right there really is no issue here. It just shows that all PE's on the PV in question have been allocated. I checked on some other non-arch systems and it is of course normal behavior.

Sorry about linking the two unrelated "bugs" and creating unneeded noise - my mistake.

So, the dm-* issue is fixed (new mkinitcpio release will follow soon, you can apply this manually if you are in a hurry), the rest is no bug. Closing.