linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Filipe David Manana <fdmanana@gmail.com>
To: Duncan <1i5t5.duncan@cox.net>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>,
	Chris Mason <clm@fb.com>, Marc MERLIN <marc@merlins.org>,
	samjnaa@gmail.com
Subject: Re: Significance of high number of mails on this list?
Date: Fri, 22 Aug 2014 10:58:33 +0100	[thread overview]
Message-ID: <CAL3q7H6PrjdSA-qjEsiX6vEMQbeYukn2R4vh=f4mteQNv0Y_qg@mail.gmail.com> (raw)
In-Reply-To: <pan$258d1$c3749601$d83e6a85$e56acf7f@cox.net>

On Fri, Aug 22, 2014 at 8:35 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> Konstantinos Skarlatos posted on Fri, 22 Aug 2014 09:56:55 +0300 as
> excerpted:
>
>> I would stay with rsync for a while, because there is always the
>> possibility of a bug that corrupts both your primary filesystem and your
>> backup one, or send propagating corruption from one filesystem to
>> another (Or maybe I am too paranoid, it would be good if we could have
>> the opinion of a btrfs developer on this)
>
> No claim to be a dev, btrfs or otherwise, here, but I believe in this
> case you /are/ "being too paranoid."
>
> Both btrfs send and receive only deal with data/metadata they know how to
> deal with.  If it's corrupt in some way or if they don't understand it,
> they don't send/write it, they fail.

Most of the time yes, however we have at least 1 know bug that affects
3.14.x only where send silently corrupts file data (replaces valid
data with zeroes) at the destination:

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=766b5e5ae78dd04a93a275690a49e23d7dcb1f39

The fix landed in 3.15, but wasn't backported to 3.14.x yet (adding
Chris to cc).

>
> IOW, if it works without error it's as guaranteed to be golden as these
> things get.  The problem is that it doesn't always work without error in
> the first place, sometimes it /does/ fail.  In that instance you can
> always try again as the existing data/metadata shouldn't be damaged, but
> if it keeps failing you may have to try something else, rsync, etc.
>
> --
> 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
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
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."

  reply	other threads:[~2014-08-22  9:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-21  3:22 Significance of high number of mails on this list? Shriramana Sharma
2014-08-21  9:14 ` Duncan
2014-08-21 11:11 ` Martin Steigerwald
2014-08-22  3:40   ` Shriramana Sharma
2014-08-22  4:19     ` Marc MERLIN
2014-08-22  6:56     ` Konstantinos Skarlatos
2014-08-22  7:35       ` Duncan
2014-08-22  9:58         ` Filipe David Manana [this message]
2014-08-22 13:13           ` Konstantinos Skarlatos
2014-08-22 17:35           ` Duncan
2014-08-22 18:34         ` Rich Freeman
2014-08-22 13:15       ` Marc MERLIN
2014-08-22 11:43 ` Austin S Hemmelgarn

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='CAL3q7H6PrjdSA-qjEsiX6vEMQbeYukn2R4vh=f4mteQNv0Y_qg@mail.gmail.com' \
    --to=fdmanana@gmail.com \
    --cc=1i5t5.duncan@cox.net \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.org \
    --cc=samjnaa@gmail.com \
    /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).