panic in geom (spindown + eil + journal)

Bjoern A. Zeeb bzeeb-lists at lists.zabbadoz.net
Wed Jun 25 17:30:07 UTC 2008


Hi,

ad0 and ad8 had been spun down.

I did a geli attach on ad8 and upon the following gjournal load
it went *boom*:

[replay]
GEOM_ELI:     Crypto: software
GEOM_JOURNAL: Journal 1861009973: ad8.eli contains data.
GEOM_JOURNAL: Journal 1861009973: ad8.eli contains journal.
GEOM_JOURNAL: Journal ad8.eli clean.
ad0: request while spun down, starting.
panic: wrong offset 671299584 for sectorsize 2352
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
kdb_backtrace() at kdb_backtrace+0x32
panic() at panic+0x1ab
g_io_request() at g_io_request+0xdb
g_slice_start() at g_slice_start+0x204
g_io_schedule_down() at g_io_schedule_down+0x229
g_down_procbody() at g_down_procbody+0x78
fork_exit() at fork_exit+0x14a
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffffff80c65d30, rbp = 0 ---
Uptime: 1d18h0m21s
Physical memory: 2036 MB
Dumping 330 MB:ad8: Idle, spin down
ad8: drive spun down.
ad0: Idle, spin down
ad0: drive spun down.

It's been hanging there. I had to break into the debugger and forced
another doadump which I'll hopefully find once I reboot.

db> call doadump
Physical memory: 2036 MB
Dumping 330 MB: 315 299 283 267 251 235 219 203 187 171 155 139 123 107 91 75 59 43 27 11
Dump complete
= 0xf

HEAD from within the last week, amd64.

-- 
Bjoern A. Zeeb              Stop bit received. Insert coin for new game.


More information about the freebsd-current mailing list