I noticed a couple of days ago that my logs were full of the following
parent transid verify failed error:
BTRFS error (device sdb): parent transid verify failed on 2763865407488 wanted 2560346 found 2586243
Notably, I have not observed anything not functioning or broken on my system: my NFS export seems to work (I haven’t verified my SMB ones, though), all my Rock-ons work normally. Furthermore, no errors were found in my most recent pool scrub (as per webUI’s report).
I of course would like to:
- Make sure this does not reflect another substantial problem that might be lurking somewhere.
- Get rid of this “error message spam” in my logs.
After some Googling, it appears that one may not worry about this error when the disk is in advance when compared to the journal like in my case (2,586,243 vs 2,560,346), and that it may be safe to clear the journal logs with
btrfs-zero-log /dev/sdb (as read here on SO, for instance). However, I noticed that the btrfs-zero-log manpage says one does not need to use btrfs-zero-log if the filesystem can be mounted.
Now, what would be the best way to verify everything is fine (or not) with my system? Would a
btrfs fi show or
btrfs check /dev/sdb help and be recommended?
If everything is confirmed as well with regards to this error, would
btrfs-zero-log be ok to use? I do remember having some other “errors” in the journal related to qgroup rescan failing, for instance, but that may be material for another topic here.
PS: my config is simple and as follows:
- latest rockstor release (-32 or -33 if I remember correctly)
- 1 OS SDD
- 2 x HDD in RAID1 in a single pool (sdb is part of this).