Johan Gardell [gardin@gmail.com] wrote: > The output from > dmsetup table > gardin-swap_1: > gardin-root: > Dreamhack-dreamhacklv: 0 2636726272 linear 8:34 384 The above output clearly shows that gardin-root and gardin-swap_1 have empty tables. I remember there was a fix that cleaned up empty tables like above but that won't help you. You need to figure out the reason for 'device mapper lookup failure' messages. > >> [22723.980390] device-mapper: table: 254:1: linear: dm-linear: Device > >> lookup failed > >> [22723.980395] device-mapper: ioctl: error adding target to table > >> [22724.001153] device-mapper: table: 254:2: linear: dm-linear: Device > >> lookup failed > >> [22724.001158] device-mapper: ioctl: error adding target to table The above messages are direct reason for not "really" creating gardin-root or gardin-swap_1 logical volumes. If you know the underlying PV's that make up gardin-root LV, try reading from them using 'dd'. If you can read, then the most likely problem is that someone else has opened them. It may be hard to find though. You need to go through usual culprits by running, 'cat /proc/mounts', 'cat /proc/swaps' etc. Is EVMS using them by any chance..., maybe mdraid... > >> mount doesn't give any messages in dmesg > >> > >> lvs shows: > >> ? LV ? ? ? ? ?VG ? ? ? ?Attr ? LSize ? Origin Snap% ?Move Log Copy% ?Convert > >> ? dreamhacklv Dreamhack -wi-ao ? 1,23t > >> ? root ? ? ? ?gardin ? ?-wi-d- 928,00g > >> ? swap_1 ? ? ?gardin ? ?-wi-d- ? 2,59g > >> > >> if i try to mount with: > >> ? mount -t reiserfs /dev/mapper/gardin-root /mnt/tmp > >> > >> i get this in dmesg: > >> ? [23113.711247] REISERFS warning (device dm-1): sh-2006 > >> read_super_block: bread failed (dev dm-1, block 2, size 4096) > >> ? [23113.711257] REISERFS warning (device dm-1): sh-2006 > >> read_super_block: bread failed (dev dm-1, block 16, size 4096) > >> ? [23113.711261] REISERFS warning (device dm-1): sh-2021 > >> reiserfs_fill_super: can not find reiserfs on dm-1 > > > > Looks like you have some kind of LV here. What is the output of the > > following two commands: Your 'dmsetup table' output shows why the mount failed. You have an LV created with no mapping. Thanks, Malahal. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
