Hi Is there anything new on this topic? I am using Ubuntu 14.04.1 and experiencing the same problem. - 6 HDDs - LUKS on every HDD - btrfs RAID6 over this 6 crypt-devices No LVM, no nodatacow files. Mount-options: defaults,compress-force=lzo,space_cache With the original 3.13-kernel (3.13.0-32-generic) it is working fine.
Then I tried the following kernels from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/ linux-image-3.14.15-031415-generic_3.14.15-031415.201407311853_amd64.deb - not even booting, kernel panic at boot. linux-image-3.15.6-031506-generic_3.15.6-031506.201407172034_amd64.deb, linux-image-3.15.7-031507-generic_3.15.7-031507.201407281235_amd64.deb, and linux-image-3.16.0-031600-generic_3.16.0-031600.201408031935_amd64.deb causing the hangs like described in this thread. When doing big IO (unpacking a .rar-archive with multiple GB) the filesystem stops working. Load stays very high but nothing actually happens on the drives accoding to dstat. htop shows a D (uninterruptible sleep (usually IO)) at many kworker-threads. Unmounting of the btrfs-filesystem only works with -l (lazy) option. Reboot or shutdown doesn't work because of the blocking threads. So only a power cut works. After the reboot the last written data before the hang is lost. I am now back on 3.13. Regards 2014-07-25 4:27 GMT+02:00 Cody P Schafer <d...@codyps.com>: > > On Tue, Jul 22, 2014 at 9:53 AM, Chris Mason <c...@fb.com> wrote: > > > > > > On 07/19/2014 02:23 PM, Martin Steigerwald wrote: > > > >>> Running 3.15.6 with this patch applied on top: > >>> - still causes a hang with `rsync -hPaHAXx --del /mnt/home/nyx/ > >>> /home/nyx/` > >>> - no extra error messages printed (`dmesg | grep racing`) compared to > >>> without the patch > >> > >> I got same results with 3.16-rc5 + this patch (see thread BTRFS hang with > >> 3.16-rc5). 3.16-rc4 still is fine with me. No hang whatsoever so far. > >> > >>> To recap some details (so I can have it all in one place): > >>> - /home/ is btrfs with compress=lzo > >> > >> BTRFS RAID 1 with lzo. > >> > >>> - I have _not_ created any nodatacow files. > >> > >> Me neither. > >> > >>> - Full stack is: sata <-> dmcrypt <-> lvm <-> btrfs (I noticed others > >>> mentioning the use of dmcrypt) > >> > >> Same, except no dmcrypt. > >> > > > > Thanks for the help in tracking this down everyone. We'll get there! > > Are you all running multi-disk systems (from a btrfs POV, more than one > > device?) I don't care how many physical drives this maps to, just does > > btrfs think there's more than one drive. > > No, both of my btrfs filesystems are single disk. > -- > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
