All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cerem Cem ASLAN <ceremcem@ceremcem.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: DRDY errors are not consistent with scrub results
Date: Tue, 28 Aug 2018 03:49:31 +0300	[thread overview]
Message-ID: <CAN4oSBfAS75x7+D2Ms93NGB5H5MG-AOR5mHg2czGCECg6api3Q@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtSGV1gz66X9BJAJosuhMTvd2=Me-X2tVDwJ0Eg9PA7BPA@mail.gmail.com>

Thanks for your guidance, I'll get the device replaced first thing in
the morning.

Here is balance results which I think resulted not too bad:

sudo btrfs balance start /mnt/peynir/
WARNING:

        Full balance without filters requested. This operation is very
        intense and takes potentially very long. It is recommended to
        use the balance filters to narrow down the balanced data.
        Use 'btrfs balance start --full-balance' option to skip this
        warning. The operation will start in 10 seconds.
        Use Ctrl-C to stop it.
10 9 8 7 6 5 4 3 2 1
Starting balance without any filters.
Done, had to relocate 18 out of 18 chunks

I suppose this means I've not lost any data, but I'm very prone to due
to previous `smartctl ...` results.

Chris Murphy <lists@colorremedies.com>, 28 Ağu 2018 Sal, 03:39
tarihinde şunu yazdı:
>
> On Mon, Aug 27, 2018 at 6:38 PM, Chris Murphy <lists@colorremedies.com> wrote:
>
> >> Metadata,single: Size:8.00MiB, Used:0.00B
> >>    /dev/mapper/master-root         8.00MiB
> >>
> >> Metadata,DUP: Size:2.00GiB, Used:562.08MiB
> >>    /dev/mapper/master-root         4.00GiB
> >>
> >> System,single: Size:4.00MiB, Used:0.00B
> >>    /dev/mapper/master-root         4.00MiB
> >>
> >> System,DUP: Size:32.00MiB, Used:16.00KiB
> >>    /dev/mapper/master-root        64.00MiB
> >>
> >> Unallocated:
> >>    /dev/mapper/master-root       915.24GiB
> >
> >
> > OK this looks like it maybe was created a while ago, it has these
> > empty single chunk items that was common a while back. There is a low
> > risk to clean it up, but I still advise backup first:
> >
> > 'btrfs balance start -mconvert=dup <mountpoint>'
>
> You can skip this advise now, it really doesn't matter. But future
> Btrfs shouldn't have both single and DUP chunks like this one is
> showing, if you're using relatively recent btrfs-progs to create the
> file system.
>
>
> --
> Chris Murphy

  reply	other threads:[~2018-08-28  4:38 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 [this message]
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

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=CAN4oSBfAS75x7+D2Ms93NGB5H5MG-AOR5mHg2czGCECg6api3Q@mail.gmail.com \
    --to=ceremcem@ceremcem.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 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.