All of lore.kernel.org
 help / color / mirror / Atom feed
From: Craig Andrews <candrews@integralblue.com>
To: fdmanana@gmail.com
Cc: "Stéphane Lesimple" <stephane_btrfs2@lesimple.fr>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Regression in Linux 5.5.0-rc[1-5]: btrfs send/receive out of memory
Date: Tue, 28 Jan 2020 10:05:37 -0500	[thread overview]
Message-ID: <f2ca887d98c1b5aacc4dde88cba74d98@integralblue.com> (raw)
In-Reply-To: <CAL3q7H5FHc9ooNOP3CnXas=_H_BEZN5mzegVMuvtoXgT9nxL6A@mail.gmail.com>

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

On 2020-01-28 10:02, Filipe Manana wrote:
> On Tue, Jan 28, 2020 at 2:46 PM Craig Andrews 
> <candrews@integralblue.com> wrote:
>> 
>> On 2020-01-27 08:44, Filipe Manana wrote:
>> > On Sat, Jan 25, 2020 at 11:18 AM Stéphane Lesimple
>> > <stephane_btrfs2@lesimple.fr> wrote:
>> >>
>> >> > ERROR: failed to clone extents to var/amavis/db/__db.001: Invalid argument
>> >>
>> >> If I may add another data point here, I'm also encountering this issue
>> >> on a 5.5.0-rc6, with the btrfs-rc7 patches applied to it (so as far as
>> >> btrfs is concerned, this is an rc7).
>> >>
>> >> On the first time, it happened after sending ~90 Gb worth of data, and
>> >> aborted (as I didn't specify the -E option to btrfs send). Then, I
>> >> retried with btrfs send -E 0, and it encountered the exact same error
>> >> on the same file.
>> >>
>> >> # btrfs send -v /tank/backups/.snaps/incoming/sendme/ | pv
>> >> 2>/dev/pts/23 | btrfs rec -E 0 /newfs/
>> >> At subvol /tank/backups/.snaps/incoming/sendme/
>> >> At subvol sendme
>> >> ERROR: failed to clone extents to
>> >> retroarch/x86_64/cores/mednafen_saturn_libretro.dll: Invalid argument
>> >> ERROR: failed to clone extents to
>> >> retroarch/x86_64/cores/mednafen_saturn_libretro.dll: Invalid argument
>> >
>> > This is probably the same case for which I sent a fix last week:
>> >
>> > https://patchwork.kernel.org/patch/11350129/
>> >
>> > Thanks.
>> 
>> I applied that patch to 5.5.0-rc7 and that solved the problem. I can 
>> now
>> do backups (which is a send/receive) successfully.
>> 
>> >
>> >>
>> >> The send/receive is still going on for now, currently around the ~200
>> >> Gb mark.
>> >>
>> >> Bees is running on this FS (but I stopped it before doing the
>> >> send/receive).
>> >>
>> >> I can test patches if needed.
>> >>
>> >> --
>> >> Stéphane.
>> 
>> The patch appears to have fixed my problems - thank you!
> 
> Great!
> 
> Can you reply to the patch's thread with a:
> 
> Tested-by: Your Name <email@foo.bar>
> 
> ?
> 
> Or I can reply to it myself with that if you agree.
> 
> Thanks!
> 
>> ~Craig


Can you please send the reply?
Tested-by: Craig Andrews <candrews@integralblue.com>

And again, thank you!
~Craig

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

  reply	other threads:[~2020-01-28 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 12:41 Regression in Linux 5.5.0-rc[1-5]: btrfs send/receive out of memory Craig Andrews
2020-01-13 13:37 ` 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 [this message]
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=f2ca887d98c1b5aacc4dde88cba74d98@integralblue.com \
    --to=candrews@integralblue.com \
    --cc=fdmanana@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=stephane_btrfs2@lesimple.fr \
    /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.