Am 11.04.2010 00:21, schrieb Chris Brannon:
The stat following cryptsetup is different than the stat at the start of process_filesystem. In the first stat, you'll see that /dev/mapper/cryptoroot is a block device. It is at inode 7872. The second stat shows that /dev/mapper/cryptoroot is a symlink, and it is at inode 7949.
/dev/mapper/ devices should NEVER be block devices. They should ONLY be created by udev and should ALWAYS be symbolic links to /dev/dm-* block devices. This is true for all type of device-mapper devices, be it cryptsetup, lvm or dmraid: $ ls -lhF /dev/mapper/ /dev/dm-* brw-rw---- 1 root disk 254, 0 12. Apr 10:40 /dev/dm-0 brw-rw---- 1 root disk 254, 1 12. Apr 10:40 /dev/dm-1 brw-rw---- 1 root disk 254, 2 12. Apr 10:40 /dev/dm-2 brw-rw---- 1 root disk 254, 3 12. Apr 10:40 /dev/dm-3 brw-rw---- 1 root disk 254, 4 12. Apr 10:40 /dev/dm-4 /dev/mapper/: insgesamt 0 crw-rw---- 1 root root 10, 59 12. Apr 10:39 control lrwxrwxrwx 1 root root 7 12. Apr 10:40 evey-chroot32 -> ../dm-4 lrwxrwxrwx 1 root root 7 12. Apr 10:40 evey-home -> ../dm-3 lrwxrwxrwx 1 root root 7 12. Apr 10:40 evey-root -> ../dm-1 lrwxrwxrwx 1 root root 7 12. Apr 10:40 evey-swap -> ../dm-2 lrwxrwxrwx 1 root root 7 12. Apr 10:40 pv -> ../dm-0