From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS kernel errors in 3.15.5
Date: Sat, 19 Jul 2014 10:18:24 +0000 (UTC) [thread overview]
Message-ID: <pan$f1686$a044955$9456213d$15d333ff@cox.net> (raw)
In-Reply-To: 1874170.zy97UOFIcr@zafu
Swâmi Petaramesh posted on Sat, 19 Jul 2014 09:19:13 +0200 as excerpted:
> This happens systematically these days, while trying to backup using
> rsync two of my laptops on an external HD - BTRFS formatted.
While I've not seen it, based on reports here on the list, there's
apparently a known issue with rsync on btrfs for 3.15 so far. It seems
to trigger most often on btrfs' with compression enabled, tho I'm not
sure if compression is required to trigger it or if it simply happens
more often with it.
I'm not sure of the status, but Chris Mason mentioned that he was
investigating and trying to reproduce, so they're definitely actively
working on it.
People seem to have better luck either reverting to the latest 3.14
series kernel for the moment, or updating to the latest 3.16-rc or live-
git build, with 3.16 of course getting close to release now. I'd move
forward as I know they're always fixing stuff and I routinely test kernel
rcs anyway, but Marc Merlin (one of the people reporting this bug), at
least, has moved back to 3.14 instead, as he says that works well for him.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-07-19 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-19 7:19 BTRFS kernel errors in 3.15.5 Swâmi Petaramesh
2014-07-19 10:18 ` Duncan [this message]
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='pan$f1686$a044955$9456213d$15d333ff@cox.net' \
--to=1i5t5.duncan@cox.net \
--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).