On 2/16/16 10:31, Joel Sing wrote:
This is the reason that the volume will not reassemble - two of your chunks
have metadata with version 64, while the rest have version 63. As such, only
chunks 0 and 1 are considered to be online - all others have old metadata and
are marked offline.
This most likely occurred due to the original panic (from another mail in the
same thread):
panic: Non dma-reachable buffer at curaddr 0xffffffff81115888(raw)
Stopped at Debugger+0x9: leave
TID PID UID PRFLAGS PFLAGS CPU COMMAND
*25637 25637 0 0x14000 0x200 1 srdis
Debugger() at Debugger+0x9
panic() at panic+0xfe
_bus_dmamap_load_buffer() at _bus_dmamap_load_buffer+0x1b6
_bus_dmamap_load() at _bus_dmamap_load+0x7f
ahci_load_prdt() at ahci_load_prdt+0x97
ahci_ata_cmd() at ahci_ata_cmd+0x69
atascsi_disk_cmd() at atascsis_disk_cmd+0x1b1
scsi_xs_exec() scsi_xs_exec+0x35
sdstart() at sdstart+0x16f
scsi_iopool_run() at scsi_iopool_run+0x5d
scsi_xsh_runqueue() at scsi_xsh_runqueue+0x13d
scsi_xsh_add() at scsi_xsh_add+0x98
sdstrategy() at sdstrategy+0x10f
spec_strategy() at spec_strategy+0x53
My guess is that it was in the process of writing out new metadata (version
64) when it paniced due to the AHCI driver being passed a non dma-reachable
buffer. This is most likely due to a bug in the softraid code - we're likely
using a malloc'd buffer in a place where we need to use a dma_alloc'd one.
I've been running with krw@'s patch from this related thread[1] and copying
and I've not paniced (yet, still have lots of data to copy back), but I'll
gladly test any patches which come out of this.
thanks,
.jh
[1] http://marc.info/?t=145529342400007&r=1&w=2
