Generation_errs

Troubleshooting
1

hello.

generation_errs appears on / partition

[root@s-nas-003 ~]# btrfs device stats /
[/dev/sda3].write_io_errs 0
[/dev/sda3].read_io_errs 0
[/dev/sda3].flush_io_errs 0
[/dev/sda3].corruption_errs 0
[/dev/sda3].generation_errs 5

in /var/log/messages:
Jul 29 22:08:20 s-nas-003 kernel: BTRFS error (device sda3): parent transid verify failed on 714555392 wanted 1796 found 24

after starting scrub new messages in /var/log/messages:

Jul 30 00:39:19 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 1412000: metadata leaf (level 0) in tree 258
Jul 30 00:39:19 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 1412000: metadata leaf (level 0) in tree 258
Jul 30 00:39:19 s-nas-003 kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 0, gen 1
Jul 30 00:39:19 s-nas-003 kernel: BTRFS error (device sda3): unable to fixup (regular) error at logical 714555392 on dev /dev/sda3
Jul 30 00:39:19 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 3509152: metadata leaf (level 0) in tree 258
Jul 30 00:39:19 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 3509152: metadata leaf (level 0) in tree 258
Jul 30 00:39:19 s-nas-003 kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 0, gen 2
Jul 30 00:39:19 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 768704512 on dev /dev/sda3, sector 3614912: metadata leaf (level 0) in tree 2
Jul 30 00:39:19 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 768704512 on dev /dev/sda3, sector 3614912: metadata leaf (level 0) in tree 2
Jul 30 00:39:19 s-nas-003 kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 0, gen 3
Jul 30 00:39:19 s-nas-003 kernel: BTRFS error (device sda3): unable to fixup (regular) error at logical 714555392 on dev /dev/sda3
Jul 30 00:39:19 s-nas-003 kernel: BTRFS error (device sda3): fixed up error at logical 768704512 on dev /dev/sda3
Jul 30 00:40:01 s-nas-003 systemd: Started Session 572 of user root.
Jul 30 00:41:29 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 1412000: metadata leaf (level 0) in tree 258
Jul 30 00:41:29 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 1412000: metadata leaf (level 0) in tree 258
Jul 30 00:41:29 s-nas-003 kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 0, gen 4
Jul 30 00:41:29 s-nas-003 kernel: BTRFS error (device sda3): unable to fixup (regular) error at logical 714555392 on dev /dev/sda3
Jul 30 00:41:29 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 3509152: metadata leaf (level 0) in tree 258
Jul 30 00:41:29 s-nas-003 kernel: BTRFS warning (device sda3): checksum/header error at logical 714555392 on dev /dev/sda3, sector 3509152: metadata leaf (level 0) in tree 258
Jul 30 00:41:29 s-nas-003 kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 0, gen 5
Jul 30 00:41:29 s-nas-003 kernel: BTRFS error (device sda3): unable to fixup (regular) error at logical 714555392 on dev /dev/sda3

2

@Vyacheslav_Finyutin Welcome to the Rockstor community.

I’m no expert but my current understanding is that generation errors are generally not good. So given this is your system drive I’d look to a re-install, and assuming you haven’t used the system pool for any data shares you should be able to mostly pick up from where you left off. And baring no power failure events you could check your system memory: see the Memory Test (memtest86+) doc subsection of our Pre-Install Best Practice (PBP). Best do this anyway to rule out flaky memory being the cause.

Hope that helps, at least a little.

3

@phillxnet thanks for the reply.
There are no problems with memory on the server.
memtest found no errors.