Re: Unable to mount loopback devices in RAID mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi!

> So I do not understand why it does not work correctly for
> him to mount either device.  Maybe this problem is not
> what I see in my testing (using 32) with disk partitions
> instead of loop.
> 
> With partitions, I only see the mount problem on raid0,
> not on raid1.
Without having looked at the code:
It seems as if this is a problem in mkfs. The first time, I mount the fresh image I have to search the correct device. After having mounted it at least once, I can use both devices interchangeably:

$ dd if=/dev/zero of=raid1_0.img bs=1M count=500
$ dd if=/dev/zero of=raid1_1.img bs=1M count=500
$ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img
$ losetup /dev/loop0 raid1_0.img
$ losetup /dev/loop1 raid1_1.img
$ mount -t btrfs /dev/loop0 /mnt/btrfs
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
       missing codepage or helper program, or other error
       In some cases useful info is found in syslog - try
       dmesg | tail  or so
$ mount -t btrfs /dev/loop1 /mnt/btrfs
#OK
$ umount /mnt/btrfs
$ mount -t btrfs -o ro /dev/loop0 /mnt/btrfs
#OK
$ umount /mnt/btrfs
$ mount -t btrfs -o ro /dev/loop1 /mnt/btrfs
#OK

So my guess is, that there's something wrong with mkfs.

	Cheers,
		Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux