Skip to main content
Tweeted twitter.com/#!/StackUnix/status/154886474628734976
wrong observation
Source Link

I'm creating a btrfs using

sudo mkfs.btrfs -m raid1 -d raid1 <small-disk> <large-disk> or
sudo mkfs.btrfs -m raid1 -d raid1 <large-disk> <small-disk>

it creates the fs with the size of the larger disk, no matter in which order i supplysum of the disk-arguments.two disks/partitions, but

 btrfs fi df <mountpoint>

gives me RAID1 for data, system and metadata

How can this be correct?

Is there some way like mdadm's

cat /proc/mdstat

to see what btrfs is doing and to assure myself my raid1 is secure? It's not terribly important data, hence it's ok to use btrfs, but i don't want to lose it either.

I'm creating a btrfs using

sudo mkfs.btrfs -m raid1 -d raid1 <small-disk> <large-disk> or
sudo mkfs.btrfs -m raid1 -d raid1 <large-disk> <small-disk>

it creates the fs with the size of the larger disk, no matter in which order i supply the disk-arguments.

How can this be correct?

Is there some way like mdadm's

cat /proc/mdstat

to see what btrfs is doing and to assure myself my raid1 is secure? It's not terribly important data, hence it's ok to use btrfs, but i don't want to lose it either.

I'm creating a btrfs using

sudo mkfs.btrfs -m raid1 -d raid1 <small-disk> <large-disk> or
sudo mkfs.btrfs -m raid1 -d raid1 <large-disk> <small-disk>

it creates the fs with the size of the sum of the two disks/partitions, but

 btrfs fi df <mountpoint>

gives me RAID1 for data, system and metadata

How can this be correct?

Is there some way like mdadm's

cat /proc/mdstat

to see what btrfs is doing and to assure myself my raid1 is secure? It's not terribly important data, hence it's ok to use btrfs, but i don't want to lose it either.

Source Link

Why does btrfs allow to create a raid1 with mismatched drives?

I'm creating a btrfs using

sudo mkfs.btrfs -m raid1 -d raid1 <small-disk> <large-disk> or
sudo mkfs.btrfs -m raid1 -d raid1 <large-disk> <small-disk>

it creates the fs with the size of the larger disk, no matter in which order i supply the disk-arguments.

How can this be correct?

Is there some way like mdadm's

cat /proc/mdstat

to see what btrfs is doing and to assure myself my raid1 is secure? It's not terribly important data, hence it's ok to use btrfs, but i don't want to lose it either.