Ok, so I ended with btrfs restore, seems that all (or most important)
files were restored.
Now looking for another reliable filesystem which will not unrecoverably
die on power outage.
msk
Dňa 22. 1. 2018 o 10:14 Zatkovský Dušan napísal(a):
Hi.
Badblocks finished on both disks with no errors. The only messages
from kernel
during night are 6x perf: interrupt took too long (2511 > 2500),
lowering kernel.perf_event_max_sample_rate to 79500
root@nas:~# smartctl -l scterc /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-4-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke,
www.smartmontools.org
SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)
root@nas:~# smartctl -l scterc /dev/sdb
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.9.0-4-amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke,
www.smartmontools.org
SCT Error Recovery Control:
Read: 70 (7.0 seconds)
Write: 70 (7.0 seconds)
root@nas:~# btrfs-debug-tree -t chunk /dev/sda4 | grep 'METADATA\|SYSTEM'
incorrect offsets 13686 13622
type METADATA|RAID1 num_stripes 2
type METADATA|RAID1 num_stripes 2
type SYSTEM|RAID1 num_stripes 2
type METADATA|RAID1 num_stripes 2
type METADATA|RAID1 num_stripes 2
root@nas:~# btrfs-debug-tree -t chunk /dev/sdb4 | grep 'METADATA\|SYSTEM'
incorrect offsets 13686 13622
type METADATA|RAID1 num_stripes 2
type METADATA|RAID1 num_stripes 2
type SYSTEM|RAID1 num_stripes 2
type METADATA|RAID1 num_stripes 2
type METADATA|RAID1 num_stripes 2
(still used "old" version of btrfs tools, working remotely now, I will
boot something newer when I will get access to that NAS at EOD)
Thank you
msk
Dňa 22. 1. 2018 o 0:24 Chris Murphy napísal(a):
On Sun, Jan 21, 2018 at 4:13 PM, Chris Murphy
<li...@colorremedies.com> wrote:
On Sun, Jan 21, 2018 at 3:31 PM, msk conf <msk.c...@gmail.com> wrote:
Hello,
thank you for the reply.
What do you get for btrfs fi df /array
Can't do that because filesystem is not mountable. I will get stats
for '/'
filesystem instead (because '/array' is an empty directory -
mountpoint on /
Try
$ sudo btrfs-debug-tree -t chunk /dev/mapper/first | grep
'METADATA\|SYSTEM'
You need to adapt that /dev/ node for your case, I just copy pasted
that from my setup. Anyway, that will look at the chunk tree and show
the profile for these chunk types.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
