linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rich Freeman <r-btrfs@thefreemanclan.net>
To: David Arendt <admin@prnet.org>
Cc: Chris Mason <clm@fb.com>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs send and kernel 3.17
Date: Mon, 13 Oct 2014 13:22:43 -0400	[thread overview]
Message-ID: <CAGfcS_k7Y2-j3moyFw3j0gzb6Xuj-AutfjvZzEnpMem-z0KPRA@mail.gmail.com> (raw)
In-Reply-To: <543A61EE.7070200@prnet.org>

On Sun, Oct 12, 2014 at 7:11 AM, David Arendt <admin@prnet.org> wrote:
> This weekend I finally had time to try btrfs send again on the newly
> created fs. Now I am running into another problem:
>
> btrfs send returns: ERROR: send ioctl failed with -12: Cannot allocate
> memory
>
> In dmesg I see only the following output:
>
> parent transid verify failed on 21325004800 wanted 2620 found 8325
>

I'm not using send at all, but I've been running into parent transid
verify failed messages where the wanted is way smaller than the found
when trying to balance a raid1 after adding a new drive.  Originally I
had gotten a BUG, and after reboot the drive finished balancing
(interestingly enough without moving any chunks to the new drive -
just consolidating everything on the old drives), and then when I try
to do another balance I get:
[ 4426.987177] BTRFS info (device sdc2): relocating block group
10367073779712 flags 17
[ 4446.287998] BTRFS info (device sdc2): found 13 extents
[ 4451.330887] parent transid verify failed on 10063286579200 wanted
987432 found 993678
[ 4451.350663] parent transid verify failed on 10063286579200 wanted
987432 found 993678

The btrfs program itself outputs:
btrfs balance start -v /data
Dumping filters: flags 0x7, state 0x0, force is off
  DATA (flags 0x0): balancing
  METADATA (flags 0x0): balancing
  SYSTEM (flags 0x0): balancing
ERROR: error during balancing '/data' - Cannot allocate memory
There may be more info in syslog - try dmesg | tail

This is also on 3.17.  This may be completely unrelated, but it seemed
similar enough to be worth mentioning.

The filesystem otherwise seems to work fine, other than the new drive
not having any data on it:
Label: 'datafs'  uuid: cd074207-9bc3-402d-bee8-6a8c77d56959
        Total devices 6 FS bytes used 2.16TiB
        devid    1 size 2.73TiB used 2.40TiB path /dev/sdc2
        devid    2 size 931.32GiB used 695.03GiB path /dev/sda2
        devid    3 size 931.32GiB used 700.00GiB path /dev/sdb2
        devid    4 size 931.32GiB used 700.00GiB path /dev/sdd2
        devid    5 size 931.32GiB used 699.00GiB path /dev/sde2
        devid    6 size 2.73TiB used 0.00 path /dev/sdf2

This is btrfs-progs-3.16.2.

--
Rich

  parent reply	other threads:[~2014-10-13 17:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DC336054-F307-4A86-AD6D-204E700DE9AA@prnet.org>
2014-10-07 13:19 ` btrfs send and kernel 3.17 Chris Mason
2014-10-07 20:45   ` David Arendt
2014-10-07 20:46     ` Chris Mason
2014-10-12 11:11       ` David Arendt
2014-10-12 15:24         ` john terragon
2014-10-12 21:35           ` David Arendt
2014-10-13  4:11             ` David Arendt
2014-10-13 12:40               ` john terragon
2014-10-13 15:40                 ` David Arendt
2014-10-13 17:22         ` Rich Freeman [this message]
2014-10-13 20:27           ` btrfs random filesystem corruption in " David Arendt
2014-10-13 20:42             ` Rich Freeman
2014-10-13 22:36               ` Duncan
2014-10-14 11:17                 ` admin
2014-10-14 21:35                   ` Duncan
2014-10-14 22:03                     ` Robert White
2014-10-14 22:55                       ` Duncan
2014-10-14 17:00                 ` David Arendt
2014-10-13 20:48             ` john terragon
2014-10-13 20:55               ` Rich Freeman
2014-10-13 20:57                 ` Rich Freeman
2014-10-13 21:22                 ` john terragon
2014-10-13 21:25                   ` David Arendt
2014-10-13 21:49                     ` Duncan
2014-10-13 23:18                   ` Rich Freeman
2014-10-14  1:30                     ` john terragon
2014-10-13 21:22               ` David Arendt
2014-10-06 18:50 btrfs send and " David Arendt
2014-10-06 19:06 ` Chris Mason
2014-10-06 19:48   ` David Arendt
2014-10-06 20:51   ` David Arendt
2014-10-06 22:22     ` Chris Mason

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=CAGfcS_k7Y2-j3moyFw3j0gzb6Xuj-AutfjvZzEnpMem-z0KPRA@mail.gmail.com \
    --to=r-btrfs@thefreemanclan.net \
    --cc=admin@prnet.org \
    --cc=clm@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).