Looking into triggering the error again and dmesg and sysrq, but here
are the other two:
# btrfs fi show
Label: none uuid: 9302fc8f-15c6-46e9-9217-951d7423927c
Total devices 8 FS bytes used 13.00TB
devid 4 size 3.64TB used 3.48TB path /dev/sdt
devid 3 size 3.64TB used 3.48TB path /dev/sds
devid 8 size 3.64TB used 3.48TB path /dev/sdr
devid 6 size 3.64TB used 3.48TB path /dev/sdp
devid 7 size 3.64TB used 3.48TB path /dev/sdq
devid 5 size 3.64TB used 3.48TB path /dev/sdo
devid 1 size 3.64TB used 3.48TB path /dev/sdl
devid 2 size 3.64TB used 3.48TB path /dev/sdm
Btrfs v0.20-rc1
# btrfs fi df /storage/storage-vol0/
Data, RAID10: total=13.89TB, used=12.99TB
System, RAID10: total=64.00MB, used=1.19MB
System: total=4.00MB, used=0.00
Metadata, RAID10: total=21.00GB, used=17.59GB
Regards,
Hans-Kristian Bakke
On 14 December 2013 22:35, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:
>
> On Dec 14, 2013, at 1:30 PM, Hans-Kristian Bakke <hkbakke@xxxxxxxxx> wrote:
>>
>> During high disk loads, like backups combinded with lot of writers,
>> rsync at high speed locally or btrfs defrag I always get these
>> messages, and everything grinds to a halt on the btrfs filesystem:
>>
>> [ 3123.062229] INFO: task rtorrent:8431 blocked for more than 120 seconds
>> [ 3123.062251] Not tainted 3.12.4 #1
>
> On blocks, if this is an unknown problem, often devs will want to see dmesg after you've issued dmesg -n7 and sysrq+w. More on sysrq triggering is here:
> https://www.kernel.org/doc/Documentation/sysrq.txt
>
>> The filesystem have used about 26TB of the available 29TB (real
>> available data), and some of the files on it are heavily fragmented
>> (around 100 000 extents at about 25GB)
>
> Please include results from btrfs fi show, and btrfs fi df <mp>.
>
>
> Chris Murphy
--
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
