Hi,
Setting the `compression` property on a subvolume on Linux 4.0-rc2 with
btrfs-progs 3.18.2 causes the error `BTRFS error (device sda5): error
inheriting props for ino [inode] (root 419): -28` to be logged to
`/var/log/syslog` (where `[inode]` is a number). I assume that setting
compression on
Greetings,
I've searched the wiki and the web looking for possible answers to
this question and haven't found information that addresses this use
case specifically. I would greatly appreciate your help or pointing
me in the right direction.
Thanks in advance!
Dave
Use case:
I have a 5TB
For no apparent reason I cannot longer mount my RAID1-pair of
500GB-disks read/write. If I do this, the kernel crashes invariably a
few seconds after the first read attempt. The syslog contains always:
kernel: BTRFS critical (device sdc): unable to update root key 5 132 0
kernel:
Original Message
Subject: Re: btrfs oops while mounting fuzzed btrfs image
From: Eric Sandeen sand...@redhat.com
To: Omar Sandoval osan...@osandov.com, Qu Wenruo
quwen...@cn.fujitsu.com, Chris Mason c...@fb.com, David Sterba
dste...@suse.cz
Date: 2015年03月06日 23:46
On
dave posted on Sun, 08 Mar 2015 11:43:49 -0600 as excerpted:
Greetings,
I've searched the wiki and the web [...]
Thanks for letting us know you already know about the wiki. =:^) Just in
case it's a different wiki... https://btrfs.wiki.kernel.org
Use case:
I have a 5TB single drive
Hi,
The manpage of `btrfs property` would be a good place to explain the
precedence of properties over mount options, e.g. what happens when the
mount option `compress` is set to `zlib` and the property for same
subvolume is set to `` (indicating no compression as you know)? What
happens when
