Hi all,
we have a build server here that accumulated lots of uncleaned subvolumes.
Snapshots containing build roots are frequently created and destroyed.
There's also a borg backup script which creates and destroys a
snapshot of the root subvolume.
We noticed this only after a reboot for a kernel
Greetings,
I'm getting reproducible Oopses when attempting "btrfs send" on my
root vol, quickly ending in a hard lockup of the machine. Both
incremental send and non-incremental send crash, the former much
earlier. The volume is in a LUKS container.
The initial fault is always during LZO decompre
On Sun, May 3, 2015 at 2:56 AM, Filipe Manana wrote:
> Marc reported a problem where the receiving end of an incremental send
> was performing clone operations that failed with -EINVAL. This happened
> because, unlike for uncompressed extents, we were not checking if the
> source clone offset and
On Mon, Apr 15, 2013 at 3:47 PM, Dan McGrath wrote:
> As per FAQ: It is safe to and recommended to turn fsck.btrfs into a no-op
>
> Signed-off-by: Dan McGrath
> ---
> btrfs.c |2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/btrfs.c b/btrfs.c
> index 691adef..78161a9 100644
> --- a/b
