btrfs device delete missing always crushes and stop system.
It log console only not STDOUT/STDERR or core file.
This is copy from leaved message on console's last screen.
=
oops_end+0x9c/0cd0
die+0x4b/0x70
do_trap+0xb2/0x140
do_error_trap+0x89/0x110
? update_inline_extent_backref+0x2ab/0x2b0
Hey.
I've often wondered:
When I do a send/receive, does the receiving side use the checksums
from the sending side (either by directly storing them or by comparing
them with calculated checksums and failing if they don't match after
the transfer)?
Cause that would effectively secure any transpor
Dear btrfs experts,
I hope this is the correct place to ask, the wiki and manpages did not help me
on these questions.
BTRFS has gained extended inode refs, skinny metadata and no-holes quite a
while ago and these are now the defaults for new mkfs.btrfs. btrfstune can
activate those features
Dear btrfs experts,
I just tried to make use of btrfs send / receive for incremental backups (using
btrbk to simplify the process).
It seems that on my two machines, btrfs send gets stuck after transferring some
GiB - it's not fully halted, but instead of making full use of the available
I/O,
OOM killer still killed rsync with swappiness 0, so rebuilt and
rebooted with the patch and restarted the rsync. Seems to be running
fine atm. Cached mem shoots right up to almost all of RAM and stays
there per usual. We'll see how it goes.
On Fri, Aug 26, 2016 at 3:02 PM, Tomasz Torcz wrote:
> O
On Sat, Aug 27, 2016 at 3:56 AM, Omar Sandoval wrote:
> On Fri, Aug 26, 2016 at 02:06:29PM +0300, Anatoly Pugachev wrote:
>>
>> I can't load btrfs module with this patch applied to 4.8.0-rc3+ (git
>> v4.8-rc3-39-g61c0457)
>> on "modprobe btrfs" i'm getting the following in the logs and module
>> d
