All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig Andrews <candrews@integralblue.com>
To: linux-btrfs@vger.kernel.org
Subject: Regression in Linux 5.5.0-rc[1-5]: btrfs send/receive out of memory
Date: Mon, 13 Jan 2020 07:41:13 -0500	[thread overview]
Message-ID: <5ba0716449eb4f838699fc0b1fb5b024@integralblue.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

If I perform a btrfs send receive like so:

sh -c btrfs send -p /mnt/everything/.snapshots/root.20191230 
/mnt/everything/.snapshots/root.20191231 | btrfs receive 
/mnt/backup/.snapshots/

On Linux 5.4.0, the process completes successfully.

Starting with Linux 5.5.0-rc1 up to the current 5.5 rc, 5.5.0-rc5, the 
result is the OOM killer being invoked which (among other process 
carnage) kills the btrfs processes stopping the backup.

I'm using the same kernel config, same hardware, etc in the two tests. 
The system has 16 GB of RAM, CPU is an i5-6500, arch is amd64.
/mnt/everything is a btrfs fs on luks (/dev/mapper/sda4) on a 1 TB SATA 
SSD (/dev/sda4). /mnt/backup is btfs fs on luks (/dev/mapper/backup) on 
a 2 TB external spinning rust HDD (/dev/sdb).

# df -H /mnt/everything/ /mnt/backup
Filesystem          Size  Used Avail Use% Mounted on
/dev/mapper/sda4    949G  698G  247G  74% /mnt/everything
/dev/mapper/backup  2.1T  1.1T  948G  53% /mnt/backup

I've attached logs and my kernel config to 
https://bugzilla.kernel.org/show_bug.cgi?id=206031

Thank you,
~Craig

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

             reply	other threads:[~2020-01-13 12:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 12:41 Craig Andrews [this message]
2020-01-13 13:37 ` Regression in Linux 5.5.0-rc[1-5]: btrfs send/receive out of memory David Sterba
2020-01-13 14:48   ` Craig Andrews
2020-01-15 18:44     ` Craig Andrews
2020-01-21  2:18   ` Craig Andrews
2020-01-25 11:08   ` Stéphane Lesimple
2020-01-27 13:44     ` Filipe Manana
2020-01-28 14:46       ` Craig Andrews
2020-01-28 15:02         ` Filipe Manana
2020-01-28 15:05           ` Craig Andrews
2020-01-28 15:08             ` Filipe Manana
2020-01-28 17:33               ` Filipe Manana
2020-01-28 17:31             ` David Sterba
2020-01-27 20:08     ` Stéphane Lesimple

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ba0716449eb4f838699fc0b1fb5b024@integralblue.com \
    --to=candrews@integralblue.com \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.