we were trying to use a 8KB sector size on the geli
provider, which caused the panic.
using 4KB as sector size works.
the command before:
geli init -bP -e 3DES -K /my/test.key -s 8192 /dev/da0
and after:
geli init -bP -e 3DES -K /my/test.key -s 4096 /dev/da0
thank you for info. i use
during copying ~350GB from one volume to another on
the local machine (separate disks, separate fs's) i
get the following panic:
start = 0, len = 23691, fs = /newdata
panic: ffs_alloccg: map corrupted
KDB: enter: panic
[ thread pid 835 tid 10070 ]
stopped at kdb_enter +0x2c: leave
for
