Hello,
seeing calltraces like this on a Ubuntu 4.13 kernel, not sure what
happens here and what the impact is:
[13729.871604] [ cut here ]
[13729.871647] WARNING: CPU: 1 PID: 3048 at
/build/linux-hwe-rDkE7z/linux-hwe-4.13.0/fs/btrfs/ctree.h:1559
btrfs_update_device+0x1b4
Hello experts,
quick question about btrfs send/receive:
Is btrfs send/receive is prone to cause destination filesystem
corruption/failure, when the source file system is bogus (due to bugs,
or due to other factors like memory bit-flips happening, both *within*
the source file system)?
Or a
Am 07.03.2017 um 15:12 schrieb Hans van Kranenburg:
On 03/05/2017 11:50 PM, Lukas Tribus wrote:
I upgraded btrfs-tools to 4.8.1 as 4.4 didn't have btrfs
inspect-internal dump-tree.
But I cannot find anything about 5242107641856 in the dump-tree output.
What does that mean?
I have no
Hello Hans,
Am 24.02.2017 um 01:26 schrieb Hans van Kranenburg:
Once that is done, I would like to go over the "btrfs recovery" thread
and see if it can
be applied for my case as well. I will certainly need your help when
that time comes...
We can take a stab at it.
I upgraded btrfs-tools
Hey guys,
I believe I have seen a OOM situations reported on the ML and IRC
recently, both of
which are believed to be unrelated to btrfs, which this case is probably
as well; I just
want to provide my dmesg here anyway in case it turns out to be related
to btrfs
nonetheless.
The following i
Hello Hans,
Am 22.02.2017 um 20:40 schrieb Hans van Kranenburg:
Question here is... is it easier for you to nuke the filesystem and
restore the files from somewhere else, or do you want to figure out
manually if it's recoverable, and spend some time with dd, hexedit,
reading struct definitions
I did a "btrfs check" (--readonly):
Summary:
589x filetype 1 errors 4, no inode ref (--> Files)
597x filetype 2 errors 4, no inode ref (--> Directories)
1183x root xxx inode YY errors 2001, no inode item, link count wrong
I looked at a handful of reported files which are verifiable via publi
Upgrading to 4.8, the FS no longer causes a kernel calltrace and does
not go read-only. It only shows the "corrupt leaf, slot offset bad" message.
A scrub completed without errors on 3 devices, while it was aborted on 2
devices. Not sure why it was aborted, since there is no error message in
d
Hi list!
I have btrfs pool consisting of 5x 2,72 TiB LUKS (dm-crypt) partitions
in RAID1, mounted on Linux 4.4 with btrfs-progs 4.4. I never had any
crashes or power loss here, but recently about every 60 - 120 minutes
(while in use) btrfs detects corruptions, aborts the transaction and
drop
