No problem. You have to wait a bit though, as the volume is currently going through a reduction in the number of drives from 8 to 7 and I do not feel comfortable stalling the volume while that is happening. I will report back with the logs later on. Mvh Hans-Kristian Bakke On 16 December 2013 19:33, Chris Mason <clm@xxxxxx> wrote: > On Mon, 2013-12-16 at 19:22 +0100, Hans-Kristian Bakke wrote: >> I have explicitly set compression=lzo, and later noatime just to test >> now, else it's just default 3.12.4 options (or 3.13-rc2 when I tested >> that). >> >> To make sure, here is my btrfs mounts from /proc/mounts: >> /dev/sdl /btrfs btrfs rw,noatime,compress=lzo,space_cache 0 0 >> /dev/sdl /storage/storage-vol0 btrfs rw,noatime,compress=lzo,space_cache 0 0 >> >> /etc/fstab: >> UUID=9302fc8f-15c6-46e9-9217-951d7423927c /btrfs btrfs >> defaults,compress=lzo,noatime 0 2 >> UUID=9302fc8f-15c6-46e9-9217-951d7423927c /storage/storage-vol0 >> btrfs defaults,subvol=storage-vol0,noatime 0 2 >> >> Hardware: >> CPU: Intel Xeon X3430 (Quad Core) >> MB: Supermicro X8SI6-F >> RAM: 16GB (4x4GB) Samsung ECC/Unbuffered DDR3 1333mhz CL9 (MEM-DR340L-SL01-EU13) >> HDDs in btrfs RAID10: 8 x Western Digital Se 4TB 64MB 7200RPM SATA >> 6Gb/s (WD4000F9YZ) >> HBAs: LSI SAS 9211-8i, LSI SAS 9201-16i >> > > Ok, could you please capture the dmesg output after a sysrq-w during one > of the stalls during rsync writing? We want to see all the stack traces > of all the waiting procs. > > Defrag is a slightly different use case, so I want to address that > separately. > > -chris > -- 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
