FreeBSD 6.1 kernel panic
I have the following setup: 3ware 9550SX-4LP raid card 4x 500GB SATA HD's in Raid 10. It's running on: FreeBSD store01 6.1-RELEASE-p12 FreeBSD 6.1-RELEASE-p12 #0: Mon Jan 22 11:20:03 UTC 2007 I use this machine mainly for backups and NFS mount points. The problem is that when I perform backups at night, within 1 hour or so the machine reboots because of kernel panic. The exact error message is: Mar 31 00:29:05 store01 syslogd: kernel boot file is /boot/kernel/kernel Mar 31 00:29:05 store01 kernel: start = 0, len = 11431, fs = /usr Mar 31 00:29:05 store01 kernel: panic: ffs_alloccg: map corrupted Mar 31 00:29:05 store01 kernel: Uptime: 2d22h57m30s Mar 31 00:29:05 store01 kernel: Cannot dump. No dump device defined. Mar 31 00:29:05 store01 kernel: Automatic reboot in 15 seconds - press a key on the console to abort This has been happening only since I started doing massive backups on this box ( lots of directories/files ). After reboot, if I run a fsck -y on the partitions everything turns out fine but with fixed errors like: Mar 28 03:53:13 store01 fsck: /dev/da0s1f: INCORRECT BLOCK COUNT I=28342913 (40 should be 0) (CORRECTED) The only other place where I've found a problem very similar to mine is: http://www.nabble.com/kern-35580:-creating-directories-on-large-UFS2--%3E-boom-t3203420.html but that is on NetBSD. Does anyone know if what I'm describing is a current bug in FreeBSD 6.1 or a problem with the 3ware card or something else. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD 6.1 kernel panic
I have the following setup: 3ware 9550SX-4LP raid card 4x 500GB SATA HD's in Raid 10. It's running on: FreeBSD store01 6.1-RELEASE-p12 FreeBSD 6.1-RELEASE-p12= #0: Mon Jan 22 11:20:03 UTC 2007 I use this machine mainly for backups and NFS mount points. The problem = is that when I perform backups at night, within 1 hour or so the machine re= boots because of kernel panic. The exact error message is: Mar 31 00:29:05 store01 syslogd: kernel boot file is /boot/kernel/kernel Mar 31 00:29:05 store01 kernel: start = 0, len = 11431, fs = /usr Mar 31 00:29:05 store01 kernel: panic: ffs_alloccg: map corrupted Mar 31 00:29:05 store01 kernel: Uptime: 2d22h57m30s Mar 31 00:29:05 store01 kernel: Cannot dump. No dump device defined. Mar 31 00:29:05 store01 kernel: Automatic reboot in 15 seconds - press a ke= y on the console to abort This has been happening only since I started doing massive backups on th= is box ( lots of directories/files ). After reboot, if I run a fsck -y on t= he partitions everything turns out fine but with fixed errors like: Mar 2= 8 03:53:13 store01 fsck: /dev/da0s1f: INCORRECT BLOCK COUNT I=28342913 (4= 0 should be 0) (CORRECTED) The only other place where I've found a problem very similar to mine is:= [1]http://www.nabble.com/kern-35580:-creating-d irectories-on-large-UFS2--%3E-boom-t3203420.html but that is on N etBSD. Does anyone know if what I'm describing is a current bug in FreeBSD 6.1 = or a problem with the 3ware card or something else. Thanks! References 1. 3Dhttp://www.nabble.com/kern-35580:-creating-directories-on-large___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 kernel panic
From a troubleshooting standpoint, I would check the following: 1) A Quick Memtest86 2) The management interface to the RAID (functional CLI in FBSD? otherwise BIOS menu); sector scan on logical volume. 3) Backup and newfs the file system UFS2 (it's just backups?) 4) The changelog for the driver on the releng-6 branch; any serious pullups into 6-stable/6.2-P* ~BAS On Sat, 2007-03-31 at 14:43 -0400, [EMAIL PROTECTED] wrote: I have the following setup: 3ware 9550SX-4LP raid card 4x 500GB SATA HD's in Raid 10. It's running on: FreeBSD store01 6.1-RELEASE-p12 FreeBSD 6.1-RELEASE-p12 #0: Mon Jan 22 11:20:03 UTC 2007 I use this machine mainly for backups and NFS mount points. The problem is that when I perform backups at night, within 1 hour or so the machine reboots because of kernel panic. The exact error message is: Mar 31 00:29:05 store01 syslogd: kernel boot file is /boot/kernel/kernel Mar 31 00:29:05 store01 kernel: start = 0, len = 11431, fs = /usr Mar 31 00:29:05 store01 kernel: panic: ffs_alloccg: map corrupted Mar 31 00:29:05 store01 kernel: Uptime: 2d22h57m30s Mar 31 00:29:05 store01 kernel: Cannot dump. No dump device defined. Mar 31 00:29:05 store01 kernel: Automatic reboot in 15 seconds - press a key on the console to abort This has been happening only since I started doing massive backups on this box ( lots of directories/files ). After reboot, if I run a fsck -y on the partitions everything turns out fine but with fixed errors like: Mar 28 03:53:13 store01 fsck: /dev/da0s1f: INCORRECT BLOCK COUNT I=28342913 (40 should be 0) (CORRECTED) The only other place where I've found a problem very similar to mine is: http://www.nabble.com/kern-35580:-creating-directories-on-large-UFS2--%3E-boom-t3203420.html but that is on NetBSD. Does anyone know if what I'm describing is a current bug in FreeBSD 6.1 or a problem with the 3ware card or something else. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.1 kernel panic
Gotcha, I will try these options but just to recap: How likely is it that the bug reported in that NetBSD page also occurs on FreeBSD ? The system works fine otherwise, if I don't do any heavy copying. I had it up for 30 days without any incident whatsoever. The moment I start doing a large copy, after a while, the kernel panic occurs. Quoting Brian A. Seklecki [EMAIL PROTECTED]: From a troubleshooting standpoint, I would check the following: 1) A Quick Memtest86 2) The management interface to the RAID (functional CLI in FBSD? otherwise BIOS menu); sector scan on logical volume. 3) Backup and newfs the file system UFS2 (it's just backups?) 4) The changelog for the driver on the releng-6 branch; any serious pullups into 6-stable/6.2-P* ~BAS On Sat, 2007-03-31 at 14:43 -0400, [EMAIL PROTECTED] wrote: I have the following setup: 3ware 9550SX-4LP raid card 4x 500GB SATA HD's in Raid 10. It's running on: FreeBSD store01 6.1-RELEASE-p12 FreeBSD 6.1-RELEASE-p12 #0: Mon Jan 22 11:20:03 UTC 2007 I use this machine mainly for backups and NFS mount points. The problem is that when I perform backups at night, within 1 hour or so the machine reboots because of kernel panic. The exact error message is: Mar 31 00:29:05 store01 syslogd: kernel boot file is /boot/kernel/kernel Mar 31 00:29:05 store01 kernel: start = 0, len = 11431, fs = /usr Mar 31 00:29:05 store01 kernel: panic: ffs_alloccg: map corrupted Mar 31 00:29:05 store01 kernel: Uptime: 2d22h57m30s Mar 31 00:29:05 store01 kernel: Cannot dump. No dump device defined. Mar 31 00:29:05 store01 kernel: Automatic reboot in 15 seconds - press a key on the console to abort This has been happening only since I started doing massive backups on this box ( lots of directories/files ). After reboot, if I run a fsck -y on the partitions everything turns out fine but with fixed errors like: Mar 28 03:53:13 store01 fsck: /dev/da0s1f: INCORRECT BLOCK COUNT I=28342913 (40 should be 0) (CORRECTED) The only other place where I've found a problem very similar to mine is: http://www.nabble.com/kern-35580:-creating-directories-on-large-UFS2--%3E-boom-t3203420.html but that is on NetBSD. Does anyone know if what I'm describing is a current bug in FreeBSD 6.1 or a problem with the 3ware card or something else. Thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
