Disk dying or different problem?

[Jan Lentfer <Jan.Lentfer@xxxxxx>]

During nightly hammer clean the system disk was set to read-only:

Dec 24 03:01:51 epia kernel: hammer: debug: changed on reblocker uncache
Dec 24 03:06:09 epia kernel: HAMMER(ROOT): Critical error 
inode=4357331932 error=5 while syncing inode
Dec 24 03:06:09 epia kernel: HAMMER(ROOT): Forcing read-only mode

In the morning I tried to mount the disk rw again which resulted in a panic:

Dec 24 09:01:31 epia kernel: HAMMER read-only -> read-write
Dec 24 09:01:31 epia kernel: panic: assertion: 
hammer_oneref(&buffer->io.lock) in hammer_recover_flush_buffer_callback
Dec 24 09:01:31 epia kernel: Trace beginning at frame 0xd139296c
Dec 24 09:01:31 epia kernel: panic(ffffffff) at panic+0xe8
Dec 24 09:01:31 epia kernel: panic(c059d5bb,c060ec28,c0588140,0,0) at 
panic+0xe8
Dec 24 09:01:31 epia kernel: 
hammer_recover_flush_buffer_callback(d1310498,d1392a08,0,0,dc5b2bf8) at 
hammer_recover_flush_buffer_callback+0xb2
Dec 24 09:01:31 epia kernel: 
hammer_buf_rb_tree_RB_SCAN(cf1c7034,0,c04b09d5,d1392a08,cf1c7000) at 
hammer_buf_rb_tree_RB_SCAN+0xad
Dec 24 09:01:31 epia kernel: 
hammer_recover_flush_buffers(cf1c7000,c2aabb90,1,c0669580,0) at 
hammer_recover_flush_buffers+0x20
Dec 24 09:01:31 epia kernel: 
hammer_vfs_mount(c2c934a8,bfbffab7,bfbff810,cc452e58,5001) at 
hammer_vfs_mount+0x407
Dec 24 09:01:31 epia kernel: 
vfs_mount(c2c934a8,bfbffab7,bfbff810,cc452e58,c2bb6af8) at vfs_mount+0x45
Dec 24 09:01:31 epia kernel: sys_mount(d1392cf0,1e8d,0,dbc0dee0,246) at 
sys_mount+0x647
Dec 24 09:01:31 epia kernel: syscall2(d1392d40) at syscall2+0x20e
Dec 24 09:01:31 epia kernel: Xint0x80_syscall() at Xint0x80_syscall+0x36
Dec 24 09:01:31 epia kernel: Uptime: 4d10h1m32s
Dec 24 09:01:31 epia kernel: Physical memory: 999 MB
Dec 24 09:01:31 epia kernel: Dumping 341 MB: 326 310 294 278 262 246 230 
214 198 182 166 150 134 118 102 86 70 54 38 22 6Copyright (c) 2003-2010 
The DragonFly Project.

Unfortunatley savecore doesn't find anything, so I don't have a dump :(


After reboot disk was recovered and mounted no problem:

Dec 24 09:01:31 epia kernel: HAMMER(ROOT) recovery check seqno=05d10b56
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) recovery range 
30000000013cd3c0-30000000034476a8
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) recovery nexto 
30000000013cd3c0 endseqno=05d42195
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) recovery undo 
30000000013cd3c0-30000000034476a8 (34054888 bytes)(RW)
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) Found REDO_SYNC 30000000013ce170
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) recovery complete
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) recovery redo 
30000000013cd3c0-30000000034476a8 (34054888 bytes)(RW)
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) Embedded extended redo 
30000000013ce170, -3504 extbytes
Dec 24 09:01:31 epia kernel: HAMMER(ROOT) End redo recovery



Is this disk near end of life or is something else going own?

The FS is rather fresh, I reinstalled this box a few weeks ago. It's 
2.8.2/i386.



Jan