geom_journal panic: wrong offset 500107860990 for sectorsize
512 - RESOLVED
anderson at freebsd.org
Tue Apr 3 04:56:33 UTC 2007
On 04/02/07 19:14, Eric Anderson wrote:
> On 04/01/07 13:01, Pawel Jakub Dawidek wrote:
>> On Sun, Apr 01, 2007 at 11:33:54AM -0500, Eric Anderson wrote:
>>> After running:
>>> gjournal load
>>> gjournal label -s 4G /dev/mirror/data
>>> I got this panic, and now every time I load geom_journal.ko, the system panics this same way.
>>> GEOM_JOURNAL: Journal 4239489025: mirror/data contains data.
>>> GEOM_JOURNAL: Journal 4239489025: mirror/data contains journal.
>>> GEOM_JOURNAL: Journal mirror/data clean.
>>> panic: wrong offset 500107860990 for sectorsize 512
>>> I have a crash dump to look at if needed.
>>> Looks something like this:
>>> #8 0xc06e0f13 in kdb_enter (msg=0x12 <Address 0x12 out of bounds>) at cpufunc.h:60
>>> #9 0xc06c2334 in panic (fmt=0xc0943b8b "wrong offset %jd for sectorsize %u") at /usr/src/sys/kern/kern_shutdown.c:547
>>> #10 0xc0685316 in g_io_request (bp=0xc2edaad4, cp=0xc2485140) at /usr/src/sys/geom/geom_io.c:356
>>> #11 0xc0685aae in g_write_data (cp=0xc2485140, offset=Unhandled dwarf expression opcode 0x93) at /usr/src/sys/geom/geom_io.c:643
>>> This is running -CURRENT's latest snapshot (from March).
>> Could you give me full backtrace? I don't see who calls g_write_data()
> This has been resolved. Turns out, that you should not use size
> modifiers like 'G' or 'M' when using the -s option to gjournal. Thanks
> Pawel for the help!!
Here is a patch that adds that functionality. Can be found here:
WARNING: This patch could explode, cause bodily harm, etc. Well, maybe
not.. but you get the point. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 3425 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20070403/41eb99d6/gjournal_size_expression.bin
More information about the freebsd-current