All of lore.kernel.org
 help / color / mirror / Atom feed
From: ein <ein.net@gmail.com>
To: Cerem Cem ASLAN <ceremcem@ceremcem.net>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: DRDY errors are not consistent with scrub results
Date: Wed, 29 Aug 2018 11:56:44 +0200	[thread overview]
Message-ID: <ef6a2ce8-43d8-59cd-194b-566da77ba8dd@gmail.com> (raw)
In-Reply-To: <CAN4oSBdfDVGmG8L2vS9h9McEs5aSuP5RfTGREB2ZhGwmAg4JhA@mail.gmail.com>

On 08/28/2018 12:51 AM, Cerem Cem ASLAN wrote:
> Hi,
>

Good morning.

>
> I'm not sure how to proceed at the moment. Taking succesfull backups
> made me think that everything might be okay but I'm not sure if I
> should continue trusting the drive or not. What additional checks
> should I perform?
> 

Can you please show also:

btrfs dev stats /path/to/the/mount/point


-- 
PGP Public Key (RSA/4096b):
ID: 0xF2C6EA10
SHA-1: 51DA 40EE 832A 0572 5AD8 B3C0 7AFF 69E1 F2C6 EA10

      parent reply	other threads:[~2018-08-29 13:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-27 22:51 DRDY errors are not consistent with scrub results Cerem Cem ASLAN
     [not found] ` <CAJCQCtSq5K90gpfGQN8JhqQddBg62m8EG_bFuWN5XyzdNStDfw@mail.gmail.com>
     [not found]   ` <CAN4oSBeHwnsm5Ecz1hAQLk6s6utHfn5XeR8xMhnZpmT-sb-_iw@mail.gmail.com>
2018-08-28  0:38     ` Chris Murphy
2018-08-28  0:39       ` Chris Murphy
2018-08-28  0:49         ` Cerem Cem ASLAN
2018-08-28  1:08           ` Chris Murphy
2018-08-28 18:50             ` Cerem Cem ASLAN
2018-08-28 21:07               ` Chris Murphy
2018-08-28 23:04                 ` Cerem Cem ASLAN
2018-08-28 23:58                   ` Chris Murphy
2018-08-29  6:58                     ` Cerem Cem ASLAN
2018-08-29  9:58                       ` Duncan
2018-08-29 10:04                         ` Hugo Mills
2018-08-29  9:56 ` ein [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=ef6a2ce8-43d8-59cd-194b-566da77ba8dd@gmail.com \
    --to=ein.net@gmail.com \
    --cc=ceremcem@ceremcem.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.