From: Filipe David Manana <fdmanana@gmail.com>
To: john terragon <jterragon@gmail.com>
Cc: Chris Mason <clm@fb.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>,
stable@vger.kernel.org, Filipe Manana <fdmanana@suse.com>
Subject: Re: [PATCH] Revert "Btrfs: race free update of commit root for ro snapshots"
Date: Thu, 16 Oct 2014 00:05:11 +0100 [thread overview]
Message-ID: <CAL3q7H6bm96eNWtvWdBuc4QnS+6BdkHXZrbEmfm6n5Po1KH3fw@mail.gmail.com> (raw)
In-Reply-To: <CANg_oxx6u3Bk5XHeTYxUHa3t9gnE4J_TWnPyzFCa0aaONxR-6g@mail.gmail.com>
On Wed, Oct 15, 2014 at 11:42 PM, john terragon <jterragon@gmail.com> wrote:
> Hi.
>
> I applied the patch to 3.17.1 but although I haven't seen any
> corrupted ro snapshot yet it's still impossible to do btrfs send. As
> soon as I start btrfs send I still get
>
> ERROR: send ioctl failed with -12: Cannot allocate memory
>
> even if I redirect btrfs send's output to a file (instead of involving
> btrfs receive)
>
> Maybe this time it's actually a btrfs-progs bug?
Not enough information to tell.
Is it a brand new fs? If not, is it a snapshot created after applying
the patch or before? Does a btrfsck reports any issues with the fs?
Is it an incremental (using -p <parent_snapshot>) or a full send? Do
you see any warning (traces, errors) in syslog (dmesg)?
Either an issue in send or, if it's an fs created/used with unpatched
3.17.0/1, it can be a side effect of the corruption.
thanks
>
> Thanks
> John
--
Filipe David Manana,
"Reasonable men adapt themselves to the world.
Unreasonable men adapt the world to themselves.
That's why all progress depends on unreasonable men."
next prev parent reply other threads:[~2014-10-15 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 18:37 [PATCH] Revert "Btrfs: race free update of commit root for ro snapshots" Filipe Manana
2014-10-15 21:11 ` Chris Mason
2014-10-15 22:42 ` john terragon
2014-10-15 23:05 ` Filipe David Manana [this message]
2014-10-15 23:49 ` john terragon
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=CAL3q7H6bm96eNWtvWdBuc4QnS+6BdkHXZrbEmfm6n5Po1KH3fw@mail.gmail.com \
--to=fdmanana@gmail.com \
--cc=clm@fb.com \
--cc=fdmanana@suse.com \
--cc=jterragon@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@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).