Re: Linux 4.14 breaks btrfs filesystems (3 times already)

2017-12-24 Thread Alec Blayne
On 24-12-2017 09:37, Nazar Mokrynskyi wrote: > Hi folks, > > I know this is a bold statement, but this is also exactly what I'm > experiencing. > > 2 filesystems that worked perfectly since July 2015 and one freshly created > crashed during last 5 weeks since Ubuntu 18.04 switched from 4.13 t

PaX: size overflow detected

2016-03-29 Thread Alec Blayne
Hi, I got this warning on dmesg: PAX: size overflow detected in function btrfs_get_extent fs/btrfs/inode.c:6690 cicus.1228_386 min, count: 104, decl: len; num: 0; context: extent_map; Which was followed by this Call Trace: [ 354.375166] Call Trace: [ 354.375173] [] ? dump_stack+0x47/0x72 [

Btrfs raid1 array has issues with rtorrent usage pattern.

2014-10-28 Thread Alec Blayne
Hi, it seems that when using rtorrent to download into a btrfs system, it leads to the creation of files that fail to read properly. For instance, I get rtorrent to crash, but if I try to rsync the file he was writting into someplace else, rsync also fails with the message "can't map file "$file":