Hi developers, I have been playing with btrfs on our test server. I have streessed it much ... and I can say ... it's troughput and features are very nice and usable, but I experienced one problem during testing, btrfs triggered lockup of 3 of 8 CPU cores of testing server. What I was doing ? Simultaneously: - copying 130GB file on one subvolume to another file and measuring speed by pv - removing one device (/dev/md3) from btrfs - running btrfs defrag on whole fs (via xargs) - rsyncing files from another server to subvolume - untaring the first 130GB tar to one subdirectory Our server is HP-DL380, 12*146GB SAS HDD, 72GB RAM, Intel Xeon 5620 Running uptodate debian wheezy with kernel and btrfs-tools from testing 3.9-1-amd64 #1 SMP Debian 3.9.6-1 x86_64 GNU/Linux # btrfs version Btrfs Btrfs v0.19 btrfs was created on top on 3 software RAID6 devices, every one built from 4 SAS drive About one hour after this(see dmesg) server became inaccessible, so I had to restart it by power cycle. After reboot there was problem with free space cache, but it was fixed automatically. I have one suspection, I have tried next this: btrfs balance start /btrfs and then btrfs resize 4:max /btrfs (device was previosly smaller) it failed with dmesg output: btrfs: dev add/delete/balance/replace/resize operation in progress. So it is possible, that it is mutualy exclusive and should not be permitted in the other way, to start balance or defrag when device is being removed, is this true ? Thank you all for your good work! Ondrej Kunc dmesg output: http://pastebin.com/Ndxypkxa P.S. in case of duplicate message I'm sorry, but I was not able to post from our company email. -- Ondřej Kunc -- 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
