linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Miguel Negrão" <miguel.negrao-lists@friendlyvirus.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: corruption in USB harddrive - backup via send/receive - question
Date: Thu, 16 Apr 2015 20:58:36 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150416T225715-417@post.gmane.org> (raw)
In-Reply-To: 20150416200613.GN5610@merlins.org

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 816 bytes --]

Marc MERLIN <marc <at> merlins.org> writes:

> 
> On Thu, Apr 16, 2015 at 06:48:43PM +0000, Miguel Negrão wrote:
> > Hello,
> > 
> > I'm running a laptop, macbook pro 8,2, with ubuntu, on kernel
> > 3.13.0-49-lowlatency. I have a USB enclosure containing two harddrives
> 
> Btrfs send/receive is not known to work well enough until 3.14.x, and
> several corruption bugs have been fixed between 3.13 and 3.19.
> 
> You should definitely upgrade to a much more recent kernel.
> 
> Marc

Hi Marc,

But in  my case the corruption is happening in the disk from where data is
being sent. Do you mean that btrfs send cand cause corruption on the sending
disk prior to 3.19 ? 

Thank you,
Miguelÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±ý»k~ÏâžØ^n‡r¡ö¦zË\x1aëh™¨è­Ú&£ûàz¿äz¹Þ—ú+€Ê+zf£¢·hšˆ§~†­†Ûiÿÿïêÿ‘êçz_è®\x0fæj:+v‰¨þ)ߣøm

  reply	other threads:[~2015-04-16 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-16 18:48 corruption in USB harddrive - backup via send/receive - question Miguel Negrão
2015-04-16 20:06 ` Marc MERLIN
2015-04-16 20:58   ` Miguel Negrão [this message]
2015-04-17 11:31 ` Austin S Hemmelgarn
2015-04-17 19:45   ` Miguel Negrão
2015-04-20 14:07 ` Sander
2015-04-20 14:29   ` Miguel Negrão

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=loom.20150416T225715-417@post.gmane.org \
    --to=miguel.negrao-lists@friendlyvirus.org \
    --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).