Re: geom_journal panic: wrong offset 500107860990 for sectorsize 512 - RESOLVED

From: Eric Anderson <anderson_at_centtech.com>
Date: Mon, 02 Apr 2007 19:14:03 -0500
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()
> exactly.
> 


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!!

Eric


-- 
------------------------------------------------------------------------
Eric Anderson        Sr. Systems Administrator        Centaur Technology
An undefined problem has an infinite number of solutions.
------------------------------------------------------------------------
Received on Mon Apr 02 2007 - 22:14:05 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:07 UTC