Bug Report: btrfs hangs / freezes on 4.3

Hi, just saw this in the logs on a few machines, Kernel 4.3.0, Mount options: /dev/sda /media/storage1 btrfs rw,noatime,compress=lzo,space_cache,subvolid=5,subvol=/ 0 0 [414675.258270] INFO: task java:19267 blocked for more than 120 seconds. [414675.258312] Not tainted 4.3.0-040300-generic

Re: raid5 + HDFS

2015-10-03 0:07 GMT+02:00 Jim Dowling : > Hi Hi, I'm not a btrfs developer but we run HDFS on top of btrfs (mainly due to other use-cases that profit from checksumming data) > I am interested in combining BtrFS RAID-5 with erasure-coded replication for > HDFS. We have an implementation of Reed-So

Re: FYIO: A rant about btrfs

Hi, 2015-09-16 17:20 GMT+02:00 Austin S Hemmelgarn : [...] > 3. He's testing it for a workload is a known and documented problem for > BTRFS, and claiming that that means that it isn't worth considering as a > general usage filesystem. Most people don't run RDBMS servers on their > systems, and a

Re: BTRFS deadlock when OOM killed processes using the file system

2015-08-19 17:39 GMT+02:00 Leo Unbekandt : > Hello everyone, > > I've encountered what looks like a nasty bug which occures when the OOM > kills a process and that this process is working with the file system. > I've been able to reproduce this issue using docker, by limiting the > memory limits of

Re: fs unreadable after powercycle: BTRFS (device sda): parent transid verify failed on 427084513280 wanted 390924 found 390922

2015-08-08 21:05 GMT+02:00 Hugo Mills : >> Maybe someone can give some clues why does this happen in the first >> place? Is it unfortunate timing due to the abrupt power cycle? >> Shouldn't CoW protect against this somewhat? > >Not "somewhat": it should protect it completely. There are two ways

fs unreadable after powercycle: BTRFS (device sda): parent transid verify failed on 427084513280 wanted 390924 found 390922

Hi, after a hard reboot (powercycle) a btrfs volume did not come up again: It's a single 4TB disk - only btrfs with lzo - data=single,metadata=dup [ 121.831814] BTRFS info (device sda): disk space caching is enabled [ 121.857820] BTRFS (device sda): parent transid verify failed on 427084513280

Re: Linux 4.1.0: BTRFS: error (device sdb) in btrfs_run_delayed_refs:2821: errno=-17 Object already exists

Some more data: After unmounting the read-only mounted partition, this notice appears in the kernel log: VFS: Busy inodes after unmount of sdb. Self-destruct in 5 seconds. Have a nice day... Here is a the btrfs check output.. btrfs check --repair seems to fix the issues: # btrfs check /dev/sdb

Linux 4.1.0: BTRFS: error (device sdb) in btrfs_run_delayed_refs:2821: errno=-17 Object already exists

Hi, is this a know issue and is there a already a patch out there for this? This is also happening with Linux 4.0.4. I can reproduce this expect it's happening under load... Mount options: /dev/sdb /media/storage2 btrfs ro,noatime,compress=lzo,space_cache 0 0 # uname -r 4.1.0-040100-generic # bt

Linux 4.1.0: BTRFS: error (device sdb) in btrfs_run_delayed_refs:2821: errno=-17 Object already exists

Hi, is this a know issue and is there a already a patch out there for this? This is also happening with Linux 4.0.4. I can reproduce this expect it's happening under load... Mount options: /dev/sdb /media/storage2 btrfs ro,noatime,compress=lzo,space_cache 0 0 # uname -r 4.1.0-040100-generic # bt