btrfs fi df doesn't show raid type after balance
Did something break.. ? we are not reporting raid type after balance.
-----------
# btrfs fi df /btrfs Data, RAID0: total=2.00GB, used=2.03MB Data: total=8.00MB, used=0.00 System, RAID0: total=16.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, RAID0: total=2.00GB, used=216.00KB Metadata: total=8.00MB, used=4.00KB
# btrfs bal /btrfs Done, had to relocate 5 out of 5 chunks
# btrfs fi df /btrfs Data: total=1.00GB, used=2.78MB System: total=4.00MB, used=4.00KB Metadata: total=1.00GB, used=276.00KB # -----------
btrfs-progs is at integration-20130321 and 3.8.0+
Thakns
Anand
Quoted 16 lines · Anand Jain
Did something break.. ? we are not reporting raid type after balance.
-----------
# btrfs fi df /btrfs Data, RAID0: total=2.00GB, used=2.03MB Data: total=8.00MB, used=0.00 System, RAID0: total=16.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, RAID0: total=2.00GB, used=216.00KB Metadata: total=8.00MB, used=4.00KB# btrfs bal /btrfs Done, had to relocate 5 out of 5 chunks
Quoted 8 lines
# btrfs fi df /btrfs Data: total=1.00GB, used=2.78MB System: total=4.00MB, used=4.00KB Metadata: total=1.00GB, used=276.00KB # -----------btrfs-progs is at integration-20130321 and 3.8.0+
I already saw this. When the filesystem is empty a balance revert the RAID mode to the single one. If the filesystem is not empty I was not able to reproduce this.
Quoted 8 lines
Thakns
AnandSignature · 3 lines
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Signature · 2 lines
gpg @keyserver.linux.it: Goffredo Baroncelli (kreijackATinwind.it> Key fingerprint BBF5 1610 0B64 DAC6 5F7D 17B2 0EDA 9B37 8B82 E0B5
Quoted 2 lines · Goffredo Baroncelli
Quoted 1 line · Anand Jain
Did something break.. ? we are not reporting raid type after balance.
fi df reports exactly what is on the filesystem.
Quoted 19 lines
Quoted 19 lines
-----------
# btrfs fi df /btrfs Data, RAID0: total=2.00GB, used=2.03MB Data: total=8.00MB, used=0.00 System, RAID0: total=16.00MB, used=4.00KB System: total=4.00MB, used=0.00 Metadata, RAID0: total=2.00GB, used=216.00KB Metadata: total=8.00MB, used=4.00KB# btrfs bal /btrfs Done, had to relocate 5 out of 5 chunks# btrfs fi df /btrfs Data: total=1.00GB, used=2.78MB System: total=4.00MB, used=4.00KB Metadata: total=1.00GB, used=276.00KB # -----------
Quoted 5 lines
Quoted 1 line
btrfs-progs is at integration-20130321 and 3.8.0+
I already saw this. When the filesystem is empty a balance revert the RAID mode to the single one. If the filesystem is not empty I was not able to reproduce this.
Any unused raid profile is thrown away after full balance (except system/single if it is there), because balance is currently implemented that way. It does not check if there is a preferred allocation profile to keep even if it is empty. The single profile is default and is automatically picked after new data are being written.
I've seen this after creating a multi-device fs with raid0/1/10 profiles, filled with data, removed everyting, ran balance to unallocate the blockgroups and found data group missing. I don't have an explanation why the raid0 profiles got merged into the single profiles in Anand's example.
david