Hide Forgot
I have a problem with the server running on CentOS. CentOs has been upgraded to version 6.4 and has wsystkie updates. Updates were made according to the official repositories. On the server running the V-Server. #--------------------------------------------FSTAB------------------------------------------# # Device Mountpoint FStype Options Dump Pass /dev/sda1 /boot ext3 rw,noatime 1 2 /dev/vg0/root / ext3 rw,noatime 1 1 /dev/vg0/swap none swap sw 0 0 /dev/vg0/usr /usr ext3 rw,noatime 1 2 /dev/vg0/var /var ext3 rw,noatime 1 2 /dev/vg0/log /var/log ext3 rw,noatime 1 2 /dev/vg0/tmp /tmp ext3 rw,noatime,nosuid,noexec 1 2 /dev/vg0/home /home ext3 rw,noatime 1 2 /dev/vg0/vz /vservers ext3 rw,noatime 1 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 The problem is with / dev / pts / ptmx #host /dev/pts > ls -la total 0 drwxr-xr-x 2 root root 0 Sep 12 12:34 . drwxr-xr-x 18 root root 3860 Sep 12 12:34 .. crw--w---- 1 mmichalski tty 136, 0 Sep 12 12:53 0 c--------- 1 root root 5, 2 Sep 12 12:34 ptmx As you can see it has no rights. The same situation is running virtual. Below is the fstab file virtual none /proc proc defaults 0 0 none /tmp tmpfs size=16m,mode=1777 0 0 none /dev/pts devpts gid=5,mode=620 0 0 What can cause this problem and where to look for solutions?
Hmm - what is the actual problem? How it is related to device mapper? Is lvm2 reading this device ? Or your problem with just access rights ? (Then I'd have guessed it's a bug for udevd and udev rules or eventually systemd)