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 <li...@colorremedies.com>, 28 Ağu 2018 Sal, 03:39
tarihinde şunu yazdı:
>
> On Mon, Aug 27, 2018 at 6:38 PM, Chris Murphy <li...@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
