Bug #1033

HAMMER: fatal trap 12 when mount_hammer

Added by tuxillo over 6 years ago. Updated over 6 years ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

As a lot of times before, I've loaded my vinum configuration and tried to mount
my hammer volume (/dev/vinum/datapool) with a surprise.

mount_hammer drops the kernel to a fatal trap 12. For details take a look to
images on leaf. This is reproduced everytime I try to mount that HAMMER volume.

I don't really know if there's something corrupt in my HAMMER volume.

Looking to that p output we see that:
master# addr2line -e /kernel c046de8c
/usr/src/sys/libkern/crc32.c:116

And that line corresponds to:
while (size--)
crc = crc32_tab[(crc ^ *p++) & 0xFF] ^ (crc >> 8);

I'm afraid I can't specify exactly the HAMMER version that this kernel is using,
but it must be that "HAMMER 54/Many: Performance tuning" or so.

If you need further information, let me know and I'll try to provide it.

History

#2 Updated by tuxillo over 6 years ago

I've just compiled the latest code and now when trying to mount the HAMMER
volume I get this:

Debugger("CRC FAILED: B-TREE NODE")
Stopped at Debugger+0x34: movb $0,in_DEbugger.3919
db>

#3 Updated by mneumann over 6 years ago

Make sure that you do a fresh newfs_hammer. And don't forget to compile
the latest newfs_hammer as well!

Regards,

Michael

#4 Updated by tuxillo over 6 years ago

I can't lose my information, so no newfs_hammer here :)

Cheers,
Antonio Huete

#5 Updated by mneumann over 6 years ago

Then it will probably not work! It's better not to use hammer for
important data yet!!! Better make a backup of your data and wait for the
2.0 release.

Regards,

Michael

#6 Updated by dillon over 6 years ago

:
:> Make sure that you do a fresh newfs_hammer. And don't forget to compile
:> the latest newfs_hammer as well!
:>
:> Regards,
:>
:> Michael
:
:I can't lose my information, so no newfs_hammer here :)
:
:Cheers,
:Antonio Huete

Please do not put any data on a HAMMER filesystem that you can't afford
to lose, not yet.

The on-media format is not going to be set in stone until maybe two
weeks before the 2.0 release. The release will be mid-july so the
on-media format is going to keep changing for the rest of this month.

I have three major media changes in the works at the moment.

-Matt
Matthew Dillon
<>

#7 Updated by tuxillo over 6 years ago

After following Sascha and Michael advices, I realized that there was a problem
with my HAMMER version. All changes in code required to do a newfs_hammer all
old HAMMER volumes.

Reading mail below made my doubts dissapear.
http://leaf.dragonflybsd.org/mailarchive/kernel/2008-06/msg00122.html

This can be closed.

Also available in: Atom PDF