linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Smith <lenovomi@gmail.com>
To: Patrik Lundquist <patrik.lundquist@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: uknown issues - different sha256 hash - files corruption
Date: Tue, 26 Jan 2016 13:27:08 +0100	[thread overview]
Message-ID: <CAAcrkYJciZXnH7PXF3Nc58AibXPHZkxaZHgEVpc445TcYx_QQg@mail.gmail.com> (raw)
In-Reply-To: <CAA7pwKM+OZoF7v3Xq=J=KSpidsGsY4hi6TxxkSAKZAJRODCDSg@mail.gmail.com>

but i heard that was serious issue with LVM/MD + ext4 in 3-4x kernels?

On Tue, Jan 26, 2016 at 1:23 PM, Patrik Lundquist
<patrik.lundquist@gmail.com> wrote:
> On 26 January 2016 at 12:54, John Smith <lenovomi@gmail.com> wrote:
>>
>> is it possible there is connection with
>> https://bugzilla.kernel.org/show_bug.cgi?id=93581, i have 2x 3tb wd
>> red drives, kernel 4.4.
>
> No, WD Red aren't Shingled Magnetic Recording (SMR) drives.

  reply	other threads:[~2016-01-26 12:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 22:00 uknown issues - different sha256 hash - files corruption John Smith
2016-01-25  0:06 ` Patrik Lundquist
     [not found]   ` <CAAcrkY+3w--OGYWwben+KYohdqwBBryDn8REJ6tiBk4jM3Tp9w@mail.gmail.com>
2016-01-25  9:03     ` Patrik Lundquist
2016-01-25 16:53       ` John Smith
2016-01-25 22:02         ` Henk Slager
2016-01-26  0:15           ` John Smith
     [not found]             ` <CAAcrkYK7p1kFNS_p7s12Qv3Hafemq89hgocfa+DoX6Y15bXeBA@mail.gmail.com>
2016-01-26 11:58               ` John Smith
2016-01-26 11:59                 ` John Smith
2016-01-26 11:54           ` John Smith
2016-01-26 12:23             ` Patrik Lundquist
2016-01-26 12:27               ` John Smith [this message]
2016-01-26 14:32               ` John Smith
2016-01-26 16:51                 ` Duncan
2016-01-26 17:41                   ` John Smith
2016-01-27  8:00                     ` Duncan
2016-01-25  0:28 ` Duncan
2016-01-25  0:48   ` Chris Murphy

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=CAAcrkYJciZXnH7PXF3Nc58AibXPHZkxaZHgEVpc445TcYx_QQg@mail.gmail.com \
    --to=lenovomi@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=patrik.lundquist@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).