Bug 81781 - page allocation failure: order:4, mode:0x4050
Summary: page allocation failure: order:4, mode:0x4050
Status: NEW
Alias: None
Product: File System
Classification: Unclassified
Component: btrfs (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Josef Bacik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-07 03:27 UTC by Chris Murphy
Modified: 2016-03-20 11:25 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.16.0
Tree: Fedora
Regression: No


Attachments
dmesg 3.16.0-1.fc21.x86_64 (119.47 KB, text/plain)
2014-08-07 03:27 UTC, Chris Murphy
Details
dmesg 3.16.0-1.fc21.x86_64+debug (9.50 KB, text/plain)
2014-08-07 03:59 UTC, Chris Murphy
Details

Description Chris Murphy 2014-08-07 03:27:37 UTC
Created attachment 145321 [details]
dmesg 3.16.0-1.fc21.x86_64

Summary: Midway through btrfs send/receive, the process fails with memory errors.

Command and result:
# btrfs send /mnt/320G/2012april_HDD_fullbackup.ro.0/ | btrfs receive /mnt/500G/
At subvol /mnt/320G/2012april_HDD_fullbackup.ro.0/
At subvol 2012april_HDD_fullbackup.ro.0
ERROR: send ioctl failed with -12: Cannot allocate memory
ERROR: unexpected EOF in stream.


Versions:
kernel-3.16.0-1.fc21.x86_64
btrfs-progs-3.14.2-3.fc21.x86_64

Both the source and destination Btrfs were created in the past 24 hours with the above version kernel and progs.


Reproduce steps:
1. A long time ago in April 2012 a subvolume was made into a btrfs send output file.
2. Today that file was received onto new Btrfs volume "320G" which was successful, no errors.
3. The resulting ro subvolume was send/received to new Btrfs volume "500G"; about 25G into a 115G transfer, the failure occurs.


Reproducible:
Unknown. Trying again right now with Fedora debug kernel (although I don't think it has any Btrfs specific debugging in it, it does have some memory debugging enabled and it could be related to that.)

So far the transfer has gone past the point of the previous failure, attaching a dmesg from the original failure (not a debug kernel).
Comment 1 Chris Murphy 2014-08-07 03:59:34 UTC
Created attachment 145331 [details]
dmesg 3.16.0-1.fc21.x86_64+debug

Just happened with debug kernel, but I'm not seeing new information.
Comment 2 Chris Murphy 2014-08-10 20:41:57 UTC
Is not reproducible with 3.14.15-100.fc19.x86_64.

Note You need to log in before you can comment on or make changes to this bug.