freebsd-upgrade from 6.2 to 6.3 errors

[Gert Lynge - Inter-Data A/S]

Hi

Just followed 
http://www.daemonology.net/blog/2007-11-10-freebsd-minor-version-upgrade.html 
very careful to upgrade my box from 6.2 to 6.3 (btw. great work by Colin 
Percival). Now uname shows:
# uname -a
FreeBSD ws.inter-data.dk 6.3-RELEASE-p1 FreeBSD 6.3-RELEASE-p1 #0: Wed Feb 13 
02:56:56 UTC 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP  i386

...as expected. The problems is that at the final sh freebsd-update.sh -f 
freebsd-update.conf install it said:
# sh freebsd-update.sh -f freebsd-update.conf install
Installing updates...ln: ///usr/share/man/man4/em.4.gz: No such file or 
directory
rmdir: ///usr/src/gnu/usr.bin/gzip: Directory not empty

Should I be concerned?
The system seems to run fine, but man pages (i.e. man em or man arp) still 
states FreeBSD 6.2 at the final line. Is this wrong?
What about the two errors. Do I need to clean something up after 
freebsd-update?:

# ls -l /usr/share/man/man4/em*
-rwxr--r-x  1 root  wheel  5391 Jun 29  2007 /usr/share/man/man4/em.4
-r--r--r--  2 root  wheel  2879 Mar 14  2007 /usr/share/man/man4/emSAVE.4.gz

# ls -l /usr/src/gnu/usr.bin/gzip
total 64
-rw-r--r--  1 root  wheel  10701 May  3  2004 gzip.h.orig
-rw-r--r--  1 root  wheel  31707 Aug 13  2004 inflate.c.orig
-rw-r--r--  1 root  wheel   9229 Aug 28  1999 unlzh.c.orig
-rw-r--r--  1 root  wheel   8212 Aug 28  1999 unpack.c.orig

Thank you in advantage...

With kind regards

Gert Lynge
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

SV: RAID1 synchronisation - howto OR not necessary?

[Gert Lynge]

The disks themselves handle the checksumming to detect bad blocks.
With modern disks it is *very* rare that a block on the disk goes bad
without the disk being able to report it it as such.  
This means that if you have a functioning RAID1 setup and one of the
disks report a bad block, then the controller can simply read the
corresponding block from the other disk, and rewrite it to the disk
with the bad block.  If a disk has problems writing a block it will
transparently re-map the block to another.
The problems can occur when one disk in a RAID-array has failed and you
try to rebuild it from the other disk(s). If you then encounter a bad block
on that disk you have a problem since you don't have a good copy of that
block.
This is what verification (which, btw, is not the same as synchronization)
tries to prevent by reading every block on each disk on a regular basis. 
Then the RAID controller can recover the data on any bad blocks from the
other disk(s) in the array.

I've been wondering how to do this with a BIOS assisted soft raid for some
time.
I have a server with ad4 ad6 in a mirror detected as ar0:

ws# atacontrol status ar0
ar0: ATA RAID1 subdisks: ad4 ad6 status: READY

ws# cat /var/run/dmesg.boot
[...]
ar0: 76316MB Intel MatrixRAID RAID1 status: READY
ar0: disk0 READY (master) using ad4 at ata2-master
ar0: disk1 READY (mirror) using ad6 at ata3-master
[...]


...and was wondering if dd could not do the job for me?

ws# man dd
[...]
EXAMPLES
 Check that a disk drive contains no bad blocks:
   dd if=/dev/ad0 of=/dev/null bs=1m
[...]


What if I run:
dd if=/dev/ad4 /of=/dev/null bs=1m
dd if=/dev/ad6 /of=/dev/null bs=1m

...once a week - will that not verify that the two drives can read all
blocks?

It would be nice to limit the load (the throughput of dd) though - anyone
know if that is possible? Maybe by pipeing through a second command (I guess
a throughput limiter could easily be programmed?).

Regards
Gert Lynge

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]

Rare / random hangs with FreeBSD 6.2-RELEASE-p4

[Gert Lynge]

Hi

Running a FreeBSD 6.2 with mainly MySQL, Apache and PHP (kept up to date
with manual freebsd-update / portupgrade).

The hardware is SuperMicro SuperServer 5015MT+ with 2GB of ECC RAM and a
Intel Core 2 Quad 6700. Running a BIOS assisted soft mirror with SATA
disks...

After aprox 2 weeks the server hangs. There is no dumps at /var/crash as the
server seems to lock up while dumping. Details below - unfortunately I don't
always get a picture of the console as I'm not always the rebooter.
There is no hang-related notes i FreeBSD logs, and nothing at all in IPMI
and BIOS logs.

Earlier I had the server running with HTTP Accept Filters on, but then it
reboots 4-5 times a day! I've also been running xcache (php accelrator), but
that was disabled during the latest hang.

Do You have any suggestions?
Does this seems to be hardware or software related?
Anything I could try to figure out what is going on?
Unfortunately the server is in production.

Thank You for any help.

Regards
Gert Lynge

 Hang 1
panic: vm_fault: fault on nofault entry, addr: e92cf000
cpuid = 3
Uptime: 10d0h24m25s
Dumping 2046 MB (2 chunks)
  chunk 0: 1MB (150 pages) ... Ok
  chunk 1: 2046MB (523744 pages)_
---
 Hang 2:
Fatal trap 12: page fault while in kernel mode
Cupid = 2; apic id = 2
Fault virtual address = 0x5a
Fault code = supervisor read, page not present
Instruction pointer = 0x20:0xc07e40a3
Stack pointer = 0x28:0xe6a35b74
Frame pointer = 0x28:0xe6a35c40
Code segment = base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, def32 1, gran 1
Processor eflags = interrupt enabled, resume, IOPL = 0
Current process = 44 (pagezero)
Trap number = 12
Panic: page fault
Cupid = 2
Uptime 17d22h47m51s
Dumping 2048 MB (2 chunks)
  Chunk 0: 1MB (150 pages)ipfw: 
ipfw: xx
---
 uname -a
FreeBSD x.x.x 6.2-RELEASE-p4 FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55
UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
i386
---
 cat /etc/rc.conf
defaultrouter=x.x.x.x
font8x14=cp865-8x14
font8x16=cp865-8x16
font8x8=cp865-8x8
hostname=x.x.x
ifconfig_em1=inet x.x.x.x  netmask x.x.x.x
saver=daemon
usbd_enable=YES
keymap=danish.cp865
keyrate=fast
sshd_enable=YES
firewall_enable=YES
firewall_type=x
firewall_logging=YES
ntpd_enable=YES
ntpd_sync_on_start=YES
mysql_enable=YES
apache22_enable=YES
#apache22_http_accept_enable=YES
inetd_enable=YES
clear_tmp_enable=YES
#log_in_vain=1
sendmail_enable=YES
rsyncd_enable=YES
syslogd_flags=-a x.x.x.x/x:*
clamav_freshclam_enable=YES
local_startup=/usr/local/etc/rc.d
dumpdev=/dev/ar0s1b
---
 cat /var/run/dmesg.boot
Copyright (c) 1992-2007 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 6.2-RELEASE-p4 #0: Thu Apr 26 17:55:55 UTC 2007
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP
Timecounter i8254 frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM)2 Quad CPUQ6700  @ 2.66GHz (2660.01-MHz 686-class
CPU)
  Origin = GenuineIntel  Id = 0x6fb  Stepping = 11
 
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA
,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
  Features2=0xe3bdSSE3,RSVD2,MON,DS_CPL,VMX,EST,TM2,b9,CX16,b14,b15
  AMD Features=0x2000LM
  AMD Features2=0x1LAHF
  Cores per package: 4
real memory  = 2146304000 (2046 MB)
avail memory = 2095165440 (1998 MB)
ACPI APIC Table: PTLTD  APIC  
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
ioapic0 Version 2.0 irqs 0-23 on motherboard
ioapic1 Version 2.0 irqs 24-47 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
acpi0: PTLTD   RSDT on motherboard
acpi0: Power Button (fixed)
Timecounter ACPI-fast frequency 3579545 Hz quality 1000
acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0
cpu0: ACPI CPU on acpi0
cpu1: ACPI CPU on acpi0
cpu2: ACPI CPU on acpi0
cpu3: ACPI CPU on acpi0
pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0
pci0: ACPI PCI bus on pcib0
pcib1: ACPI PCI-PCI bridge irq 16 at device 1.0 on pci0
pci1: ACPI PCI bus on pcib1
pcib2: ACPI PCI-PCI bridge irq 17 at device 28.0 on pci0
pci9: ACPI PCI bus on pcib2
pcib3: ACPI PCI-PCI bridge at device 0.0 on pci9
pci10: ACPI PCI bus on pcib3
pci9: base peripheral, interrupt controller at device 0.1 (no driver
attached)
pcib4: ACPI PCI-PCI bridge irq 17 at device 28.4 on pci0
pci13: ACPI PCI bus on pcib4
em0: Intel(R) PRO/1000 Network Connection Version - 6.2.9 port
0x4000-0x401f mem 0xe020-0xe021 irq 16 at device 0.0 on pci13
em0: Ethernet address: 00:30:48:8d:1f:5e
pcib5: ACPI PCI-PCI bridge irq 16 at device 28.5 on pci0
pci14: ACPI PCI bus on pcib5
em1: Intel(R) PRO/1000 Network Connection Version - 6.2.9 port
0x5000-0x501f mem 0xe030

RE: Server rebooting itself

[Gert Lynge]

I have a 6.1 machine (AMD X2-5200) that reboots itself from time to time
for
no apparent reason.

Using HTTP accept filters by any chance?

I am investigating a similar problem - running FreeBSD 6.2 on a SupreMicro
server.
Rebooted randomly from 1-2 times a week to 3-4 times a day. Seemed to be
load related...
No kernel dump, nothing i logs, nothing in the IPMI-cards log. Actually no
clues at all :-/.

I think I narrowed it down to HTTP Accept Filters with the Apache server.
When I disabled those the problem disapered (running without reboots for 9
days now)...
I still need to confirm it 100% by re-enabling it - but I want more uptime
on the box first (just to be sure).

Regards
Gert Lynge


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]