On Nov 14, 2008, at 10:02 AM, Chris Edwards wrote:
installed the xfs module with yum and then deleted all the loopback
devices with losetup -d and started over again...
[root@wdcxen1 ~]# losetup -a
[root@wdcxen1 ~]# losetup /dev/loop0 /root/wdcdns1.img
[root@wdcxen1 ~]# losetup -a
/dev/loop0: [0807]:14876937 (/root/wdcdns1.img)
[root@wdcxen1 ~]# mount -t xfs -o loop,ro,noatime,nodev,nofsck ~/
wdcdns1.img /mnt/tmp/
Stop doing that! :) When you run 'mount' with '-o loop' it sets up
the loop device for you. There is no reason to create the loop device
ahead of time.
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Did you try checking syslog?
Also, if you are trying to mount the original device and the loop back
device at the same time, xfs will complain about conflicting UUIDs.
If that's what syslog says is going on, and you really want to mount
the same file system (one from the original device and one from the
loopback), then you will need to use the mount option 'nouuid'.
brassow
_______________________________________________
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/
