re: strange panic: freebsd 6.3: ffs_alloccg: map corrupted [SOLVED]
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 different geli sector sizes but 4K at most :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re: strange panic: freebsd 6.3: ffs_alloccg: map corrupted [SOLVED]
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 those, who are interested in: this issue was not related to UFS but to GELI. 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 cheers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange panic: freebsd 6.3: ffs_alloccg: map corrupted
On Fri, February 1, 2008 16:30, [EMAIL PROTECTED]@mgEDV.net wrote: hi folks, 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 the destination filesystem i created from scratch today, and the other which is read from is fsck'd. because of privacy/security considerations, i cannot really post the whole configuration of the machine (like fs-layout, other details, dmesg will be ok if needed). the backtrace can be viewed on this image: http://www.mgedv.at/panic_ffs_alloccg.png update: the filesystem is created using the following newfs-cmd: newfs -L newdata -O 2 -U -b 65536 -f 8192 -c 262144 -i 524288 -m 0 -o space /dev/amrd2 btw, i forgot to mention, that the panic is raised at different amounts of data being copied. so this does not seem like a hardware defect for me... anyone out there who has an idea? cheers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
strange panic: freebsd 6.3: ffs_alloccg: map corrupted
hi folks, 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 the destination filesystem i created from scratch today, and the other which is read from is fsck'd. because of privacy/security considerations, i cannot really post the whole configuration of the machine (like fs-layout, other details, dmesg will be ok if needed). the backtrace can be viewed on this image: http://www.mgedv.at/panic_ffs_alloccg.png any ideas how to react on this? cheers... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
