HAMMER2 issue ?

Matthew Dillon dillon at backplane.com
Wed Aug 29 08:45:19 PDT 2018


CRC check failure on two inode blocks.   This has happened to me once too,
I've been trying to track it down.  It is possibly related to unclean
shutdowns but it isn't supposed to happen on H2.

In terms of fixing it, it shouldn't hurt per-say (other than not being able
to access whatever files those two inodes are associated with), so you can
probably wait until the next release cycle to get the hammer2 directives
that can destroy the inodes.  Those are in master now (the hammer2
destroy-inum directive).  Any related 'dead' directory entries can also be
located and destroyed via the existing hammer2 destroy directive.

-Matt

On Tue, Aug 28, 2018 at 10:15 AM Laurent Vivier <laurent at lamzi.com> wrote:

> Hello DFlyers !
>
> I got these errors spamming dmesg and my boot TTY although the system
> seems to be running just fine, is this something I should worry about or
> correct ?
>
> I _think_ those are HAMMER2-related but I am unsure
>
> CHILD ERROR DURING FLUSH LOCK 0xfffff801a6e20220->0xfffff801121c1420
> chain 000000015fada40a.01 key=000000000001bbae meth=30 CHECK FAIL
> (flags=0114c002, bref/data da1c77a7b8e6bf1a/28229d6f300a8368)
> CHILD ERROR DURING FLUSH LOCK 0xfffff801a6e3eb20->0xfffff801a7297920
> chain 000000015fada40a.01 key=000000000001bbae meth=30 CHECK FAIL
> (flags=0114c002, bref/data da1c77a7b8e6bf1a/28229d6f300a8368)
> CHILD ERROR DURING FLUSH LOCK 0xfffff801a6e3eb20->0xfffff801a7297920
> chain 000000015fadbc0a.01 key=0000000000000410 meth=30 CHECK FAIL
> (flags=0114c002, bref/data 9f27849872699a0e/44afef9742ea97f7)
>
> My root filesystem is HAMMER2, installed from a DragonFly 5.2.1 system now
> running 5.2.2
>
> Have a great day,
>
> Laurent
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20180829/247224fa/attachment-0003.htm>


More information about the Users mailing list