Hi btrfs team, I'm using btrfs on a Ubuntu 14.10 server which I recently upgraded to 15.04: milen@server ~/Desktop> uname -a Linux server 3.19.0-16-generic #16-Ubuntu SMP Thu Apr 30 16:09:58 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux The server has 5 HDDs, 4 of them dedicated to a btrfs filesystem in Raid 1 layout: milen@server ~/Desktop> sudo btrfs fi show Label: none uuid: 684a6bda-4fb5-420d-a2d1-019e38fdc1ee Total devices 4 FS bytes used 3.95TiB devid 1 size 2.73TiB used 2.50TiB path /dev/sdd devid 2 size 2.73TiB used 2.50TiB path /dev/sde devid 3 size 931.51GiB used 699.00GiB path /dev/sdb devid 4 size 2.73TiB used 2.50TiB path /dev/sdc Btrfs v3.17 milen@server ~/Desktop> sudo btrfs fi df /mnt/d Data, RAID1: total=4.08TiB, used=3.95TiB System, RAID1: total=32.00MiB, used=624.00KiB Metadata, RAID1: total=7.00GiB, used=5.30GiB GlobalReserve, single: total=512.00MiB, used=0.00B After the recent OS upgrade I noticed a couple of issues I wanted to ask about: 1. Before the upgrade, the size of the entire array was reported as 9TB (roughly), both on the server (I use conky to monitor server status) and via samba on Windows clients. After the upgrade, the size is reduced to 4.55 TB which seems to better reflect what the actual usable space is, but is unexpected to me (I read some articles on the web about the difficulties in calculating free space on a btrfs filesystem). Is this expected? 2. After the upgrade I see the following entries in the kernel log(attached): [ 78.717743] sdb: unknown partition table [ 78.735588] sdc: unknown partition table [ 78.736279] sdd: unknown partition table [ 78.781962] sde: unknown partition table These correspond to the btrfs drives. How can I check that there is no problem with my filesystem? These messages did not appear on 14.10. When reading data the server still seems to access all drives but I wanted to be sure. I know btrfs is still considered experimental but I did put some important data I don't want to loose on the fs so I just want to make sure everything's OK. Any help is greatly appreciated. Milen
Attachment:
dmesg.log
Description: Binary data
