Upgrading to 4.8, the FS no longer causes a kernel calltrace and does
not go read-only. It only shows the "corrupt leaf, slot offset bad" message.
A scrub completed without errors on 3 devices, while it was aborted on 2
devices. Not sure why it was aborted, since there is no error message in
dmesg?
Any suggestions why the scrub was aborted?
# uname -a
Linux srv1-dom0 4.8.0-36-generic #36~16.04.1-Ubuntu SMP Sun Feb 5
09:39:57 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
# btrfs scrub status /storage/users/
scrub status for f50f980e-7640-49c7-bf8d-20d55cfe6005
scrub started at Wed Feb 22 00:07:33 2017 and was aborted after
06:35:42
total bytes scrubbed: 10.60TiB with 0 errors
/# btrfs scrub status /storage/users/ -d
scrub status for f50f980e-7640-49c7-bf8d-20d55cfe6005
scrub device /dev/dm-5 (id 1) history
scrub started at Wed Feb 22 00:07:33 2017 and finished after
06:35:36
total bytes scrubbed: 2.30TiB with 0 errors
scrub device /dev/dm-6 (id 2) history
scrub started at Wed Feb 22 00:07:33 2017 and finished after
06:35:30
total bytes scrubbed: 2.30TiB with 0 errors
scrub device /dev/dm-7 (id 3) history
scrub started at Wed Feb 22 00:07:33 2017 and finished after
06:35:42
total bytes scrubbed: 2.30TiB with 0 errors
scrub device /dev/dm-8 (id 4) history
scrub started at Wed Feb 22 00:07:33 2017 and was aborted after
05:01:37
total bytes scrubbed: 1.85TiB with 0 errors
scrub device /dev/mapper/sde3_crypt (id 5) history
scrub started at Wed Feb 22 00:07:33 2017 and was aborted after
05:01:37
total bytes scrubbed: 1.85TiB with 0 errors
#dmesg | grep BTRFS
[ 929.737119] BTRFS critical (device dm-9): corrupt leaf, slot offset
bad: block=5242107641856,root=1, slot=39
[19772.594129] BTRFS critical (device dm-9): corrupt leaf, slot offset
bad: block=5242107641856,root=1, slot=39
[19777.127704] BTRFS critical (device dm-9): corrupt leaf, slot offset
bad: block=5242107641856,root=1, slot=39
[19777.552191] BTRFS critical (device dm-9): corrupt leaf, slot offset
bad: block=5242107641856,root=1, slot=39
#
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
