Re: recommended setup for amd64 7-STABLE with ZFS, Samba 3.2 and possibly ACLs?

[Ben Stuyts]

On 30 sep 2008, at 12:46, Jeremy Chadwick wrote:


On Tue, Sep 30, 2008 at 12:08:48PM +0200, Holger Kipp wrote:

- email (imap)


I've had good experience with dovecot; I tend to stay away from Cyrus
products (disgusting code with a history of security issues), and
Courier (no interest).


I had to disable mmap access in dovecot, or it would coredump  
periodically. (mmap_disable = yes in dovecot.conf) I found that to be  
a problem only on ZFS. I don't know if that's been fixed yet. Apart  
from that it works great.


Ben

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

Re: recommended setup for amd64 7-STABLE with ZFS, Samba 3.2 and possibly ACLs?

[Ben Stuyts]

On 1 okt 2008, at 12:12, Jeremy Chadwick wrote:


On Wed, Oct 01, 2008 at 10:42:32AM +0200, Ben Stuyts wrote:

I had to disable mmap access in dovecot, or it would coredump
periodically. (mmap_disable = yes in dovecot.conf) I found that to  
be a
problem only on ZFS. I don't know if that's been fixed yet. Apart  
from

that it works great.


RELENG_7 had this problem fixed in rev 1.31.2.2, dated 2008/04/26.

Here's the proper file in cvsweb so you can see it yourself:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/cddl/contrib/opensolaris/uts/common/fs/zfs/zfs_vnops.c

Have you tried re-enabling mmap in dovecot on a system with a kernel
build after those dates?


No, thanks for pointing that out. I have missed that. My 7-stable  
kernel is from July 16, so I will re-enable it and report back.


Ben

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

Re: recommended setup for amd64 7-STABLE with ZFS, Samba 3.2 and possibly ACLs?

[Ben Stuyts]

On 1 okt 2008, at 12:12, Jeremy Chadwick wrote:


On Wed, Oct 01, 2008 at 10:42:32AM +0200, Ben Stuyts wrote:

I had to disable mmap access in dovecot, or it would coredump
periodically. (mmap_disable = yes in dovecot.conf)


Have you tried re-enabling mmap in dovecot on a system with a kernel
build after those dates?


It's been running for a day now wit mmap enabled, and it works fine  
now. Again thanks for pointing this out.


Ben

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

Re: Problems with em0 failing to initialize on stable?

[Ben Stuyts]

Hi,

On 17 apr 2008, at 13:20, Jeremy Chadwick wrote:


On Thu, Apr 17, 2008 at 06:32:32PM +0900, [EMAIL PROTECTED] wrote:
I am running 7-STABLE with machines that are net booted.  On  
occasion,

that is not with any level of predictability, this happens:

em0: Hardware Initialization Failed
em0: Unable to initialize the hardware

which of course stops the machine in its tracks.  A normal dmesg is
also included.

Any steps I should take to help debug this?


George, can you provide the following?

* Motherboard type and model (a URL to the board would be good)
* kenv | grep smbios
* pciconf -lv


I have seen this too. A couple of times on a new server here. Maybe  
one in two or three reboots. So far, it only happens after a reboot,  
but not after a hard reset or power cycle. This board has 3 em network  
if's. Two on the board itself, and one on a daughter card on the ipmi  
add-on card. It is always em0 that is giving trouble. The board is a  
Supermicro X7DBP-i: 


uname -a:
FreeBSD mars.altus-escon.com 7.0-STABLE FreeBSD 7.0-STABLE #1: Wed  
Apr  9 18:13:43 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/ 
src/sys/MARS  amd64


Here is the other data you requested:

kenv | grep smbios:
smbios.bios.reldate="05/29/2007"
smbios.bios.vendor="Phoenix Technologies LTD"
smbios.bios.version="6.00"
smbios.chassis.maker="Supermicro"
smbios.chassis.serial="0123456789"
smbios.chassis.tag=" "
smbios.chassis.version="0123456789"
smbios.planar.maker="Supermicro"
smbios.planar.product="X7DBP"
smbios.planar.serial="0123456789"
smbios.planar.version="PCB Version"
smbios.socket.enabled="2"
smbios.socket.populated="2"
smbios.system.maker="Supermicro"
smbios.system.product="X7DBP"
smbios.system.serial="0123456789"
smbios.system.uuid="53d19f64-d663-a017-8922-0030487b887e"
smbios.system.version="0123456789"

pciconf -lv:
[EMAIL PROTECTED]:0:0:0:	class=0x06 card=0x838015d9 chip=0x25d88086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000P Chipset Memory Controller Hub'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:2:0:	class=0x060400 card=0x chip=0x25f78086  
rev=0xb1 hdr=0x01

vendor = 'Intel Corporation'
device = '5000 Series Chipset PCIe x8 Port 2-3'
class  = bridge
subclass   = PCI-PCI
[EMAIL PROTECTED]:0:4:0:	class=0x060400 card=0x chip=0x25f88086  
rev=0xb1 hdr=0x01

vendor = 'Intel Corporation'
device = '5000 Series Chipset PCIe x8 Port 4-5'
class  = bridge
subclass   = PCI-PCI
[EMAIL PROTECTED]:0:6:0:	class=0x060400 card=0x chip=0x25f98086  
rev=0xb1 hdr=0x01

vendor = 'Intel Corporation'
device = '5000 Series Chipset PCIe x8 Port 6-7'
class  = bridge
subclass   = PCI-PCI
[EMAIL PROTECTED]:0:8:0:	class=0x088000 card=0x838015d9 chip=0x1a388086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 5000 Series Chipset DMA Engine'
class  = base peripheral
[EMAIL PROTECTED]:0:16:0:	class=0x06 card=0x838015d9 chip=0x25f08086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 Series Chipset Error Reporting Registers'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:16:1:	class=0x06 card=0x838015d9 chip=0x25f08086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 Series Chipset Error Reporting Registers'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:16:2:	class=0x06 card=0x838015d9 chip=0x25f08086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 Series Chipset Error Reporting Registers'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:17:0:	class=0x06 card=0x838015d9 chip=0x25f18086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 Series Chipset Reserved Registers'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:19:0:	class=0x06 card=0x838015d9 chip=0x25f38086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 Series Chipset Reserved Registers'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:21:0:	class=0x06 card=0x838015d9 chip=0x25f58086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 Series Chipset FBD Registers'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:22:0:	class=0x06 card=0x838015d9 chip=0x25f68086  
rev=0xb1 hdr=0x00

vendor = 'Intel Corporation'
device = '5000 Series Chipset FBD Registers'
class  = bridge
subclass   = HOST-PCI
[EMAIL PROTECTED]:0:29:0:	class=0x0c0300 card=0x838015d9 chip=0x26888086  
rev=0x09 hdr=0x00

vendor = 'Intel Corporation'
device = '631xESB/632xESB/3100 Chipset USB Universal Host  
Controller'

class  = serial bus
su

Re: Problems with em0 failing to initialize on stable?

[Ben Stuyts]

On 17 apr 2008, at 16:11, Jeremy Chadwick wrote:


On Thu, Apr 17, 2008 at 02:02:51PM +0200, Ben Stuyts wrote:

On 17 apr 2008, at 13:20, Jeremy Chadwick wrote:

On Thu, Apr 17, 2008 at 06:32:32PM +0900, [EMAIL PROTECTED] wrote:
I am running 7-STABLE with machines that are net booted.  On  
occasion,

that is not with any level of predictability, this happens:

em0: Hardware Initialization Failed
em0: Unable to initialize the hardware

which of course stops the machine in its tracks.  A normal dmesg is
also included.

Any steps I should take to help debug this?


George, can you provide the following?

* Motherboard type and model (a URL to the board would be good)
* kenv | grep smbios
* pciconf -lv


I have seen this too. A couple of times on a new server here. Maybe  
one in
two or three reboots. So far, it only happens after a reboot, but  
not after
a hard reset or power cycle. This board has 3 em network if's. Two  
on the
board itself, and one on a daughter card on the ipmi add-on card.  
It is

always em0 that is giving trouble. The board is a Supermicro X7DBP-i:
<http://www.supermicro.com/products/motherboard/xeon1333/5000P/X7DBP-i.cfm 
>


I'm wondering if the IPMI add-on is what's doing it.  However, the  
IPMI

cards compatible with the X7DBP all have a dedicated NIC (versus
piggybacking on top of the existing mainboards' NICs, which almost
always causes problems of the mysterious sort).  I'm not sure, but I
don't think em0 will be that NIC.


Correct, em0 and em1 are on the mainboard. em2 is on the daughter- 
daughtercard and also single use for the OS. And then there's a 4th  
nic which is the ipmi interface. It is completely separate. (I have  
the SIM1U-3B & SIM1U-3D daughter cards: <http://www.supermicro.com/products/accessories/addon/SIM.cfm 
>


Both you and George have boards that use the 82563EB.  jv@ will have  
to

help with this one.  I wonder if it's a BIOS bug of some kind, where
something on the NIC isn't getting reset by the BIOS on a soft boot...


Let me know if there's anything I can do to help. I can test patches  
during evening hours when this server is mostly idle.


Ben

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

Panic after hung rsync, probably zfs related

[Ben Stuyts]

Hi,

While doing an rsync from a zfs filesystem to an external usb hd (also  
zfs), the rsync processes hung in zfs state. I could not kill these  
processes, although the rest of the server seemingly continued to run  
fine. The reboot command did not work. Next I tried a shutdown now  
command. This caused a panic:


...
Stopping dhcpd.
Shutting down local daemons:.
Stopping named.
Waiting for PIDS: 106830 second watchdog timeout expired. Shutdown  
terminated.

Tue May 13 21:02:50 CEST 2008
May 13 21:02:50  mars init: /bin/sh on /etc/rc.shutdown  
terminated abnormally, going to single user mode

panic: vrele: negative ref cnt
cpuid = 6
Uptime: 8d3h8m21s
Physical memory: 8178 MB
Dumping 3679 MB: 3664 3648 3632 3616 3600 3584 3568 3552 3536 3520  
3504 3488 3472 3456 3440 3424 3408 3392 3376 3360 3344 3328 3312 3296  
3280 3264 3248
   atl 
 trap 12: page fault while in kernel mode

cpuid = 2; apic id = 02
fau
=Fta tvailr tduoaulb laed dfraeuslst
= r0ixp8
v f0axuflftf fcfofdfef  8   0=6 esbuap9e3r
girssopr  =r e0axdf fifnfsftfrfufcftbi5o4n8,f fp0a
 er bnpo t=  p0rxe1s0e0n0t

xipnusitdr u=c t0i;o na ppioci nitde r=  =0 00
 8:0x8
stack pointer   = 0x10:0xf8c50a50
frame pointer   = 0x10:0xfb54c450
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 44 (irq19: uhci1+)
trap number = 12

Yes, it printed all that gibberish. ("double fault" I think it says?)  
At this point, the server completely hung, and I could not do a bt  
unfortunately. I had to reset the server. After reboot, savecore did  
not find a kernel dump. I ran the rsync again and could not reproduce  
the problem. Although I've had zfs related problems before, this one  
was new to me. Any idea what happened here?


Other info on this machine follows below.

Thanks,
Ben


[mars:~]133: uname -a
FreeBSD mars.altus-escon.com 7.0-STABLE FreeBSD 7.0-STABLE #2: Mon Apr  
21 08:45:56 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/ 
sys/MARS  amd64

[mars:~]134: cat /boot/loader.conf
console="comconsole"
zfs_load="YES"
vfs.root.mountfrom="zfs:tank"
vfs.zfs.prefetch_disable=1
vm.kmem_size="1536M"
vm.kmem_size_max="1536M"
vfs.zfs.arc_max="768M"

[mars:~]135: dmesg
Copyright (c) 1992-2008 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 7.0-STABLE #2: Mon Apr 21 08:45:56 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/MARS
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(R) CPU   E5335  @ 2.00GHz (2000.08-MHz K8- 
class CPU)

  Origin = "GenuineIntel"  Id = 0x6f7  Stepping = 7
   
Features 
= 
0xbfebfbff 
< 
FPU 
,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 
=0x4e33d

  AMD Features=0x20100800
  AMD Features2=0x1
  Cores per package: 4
usable memory = 8575598592 (8178 MB)
avail memory  = 8285937664 (7902 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP): APIC ID:  1
 cpu2 (AP): APIC ID:  2
 cpu3 (AP): APIC ID:  3
 cpu4 (AP): APIC ID:  4
 cpu5 (AP): APIC ID:  5
 cpu6 (AP): APIC ID:  6
 cpu7 (AP): APIC ID:  7
ioapic0  irqs 0-23 on motherboard
ioapic1  irqs 24-47 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413,  
RF5413)

acpi0:  on motherboard
acpi0: [ITHREAD]
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:  on acpi0
p4tcc0:  on cpu0
cpu1:  on acpi0
p4tcc1:  on cpu1
cpu2:  on acpi0
p4tcc2:  on cpu2
cpu3:  on acpi0
p4tcc3:  on cpu3
cpu4:  on acpi0
p4tcc4:  on cpu4
cpu5:  on acpi0
p4tcc5:  on cpu5
cpu6:  on acpi0
p4tcc6:  on cpu6
cpu7:  on acpi0
p4tcc7:  on cpu7
pcib0:  port 0xcf8-0xcff on acpi0
pci0:  on pcib0
pcib1:  at device 2.0 on pci0
pci1:  on pcib1
pcib2:  irq 16 at device 0.0 on pci1
pci2:  on pcib2
pcib3:  irq 16 at device 0.0 on pci2
pci3:  on pcib3
pcib4:  at device 0.0 on pci3
pci4:  on pcib4
pcib5:  irq 18 at device 2.0 on pci2
pci5:  on pcib5
em0:  port  
0x2000-0x201f mem 0xd800-0xd801 irq 18 at device 0.0 on pci5

em0: Using MSI interrupt
em0: Ethernet address: 00:30:48:7b:88:7e
em0: [FILTER]
em1:  port  
0x2020-0x203f mem 0xd802-0xd803 irq 19 at device 0.1 on pci5

em1: Using MSI interrupt
em1: Ethernet address: 00:30:48:7b:88:7f
em1: [FILTER]
pcib6:  at device 0.3 on pci1
pci6:  on pcib6
puc0:  port  
0x3030-0x3037,0x3028-0x302f,0x3020-0x3027,0x3018-0x301f, 
0x3010-0x3017,0x3000-0x300f irq 24 at device 

Re: Panic after hung rsync, probably zfs related

[Ben Stuyts]

On 13 mei 2008, at 21:53, Xin LI wrote:

| While doing an rsync from a zfs filesystem to an external usb hd  
(also

| zfs), the rsync processes hung in zfs state. I could not kill these
| processes, although the rest of the server seemingly continued to  
run

| fine. The reboot command did not work. Next I tried a shutdown now
| command. This caused a panic:

Sound like you somehow run out of memory, there is an known issue with
ZFS which causes livelock when there is memory pressure.  Which rsync
version are you using?  With rsync 3.x the memory usage would drop
drastically which would help to prevent this from happening.


I'm running rsync 3.0.0. Two weeks ago I already increased the memory  
in this machine from 4 to 8 GB, but I did not change any loader.conf  
variables.


BTW, The wired memory goes all over the place in this machine: even  
when it's mostly idle it varies between 300 MB and 3.5 GB. That's why  
I added 4 more GB.


Ben

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

Re: Panic after hung rsync, probably zfs related

[Ben Stuyts]

On 14 mei 2008, at 10:50, Kostik Belousov wrote:


BTW, The wired memory goes all over the place in this machine: even
when it's mostly idle it varies between 300 MB and 3.5 GB. That's why
I added 4 more GB.

3.5Gb wired ? Do you run amd64 ?

Does wired memory drops lower after you change the load ?


Yes, it was in my original message.

Ben

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

Re: Panic after hung rsync, probably zfs related

[Ben Stuyts]

On 14 mei 2008, at 10:15, Kris Kennaway wrote:

| While doing an rsync from a zfs filesystem to an external usb hd  
(also

| zfs), the rsync processes hung in zfs state. I could not kill these
| processes, although the rest of the server seemingly continued to  
run

| fine. The reboot command did not work. Next I tried a shutdown now
| command. This caused a panic:
Sound like you somehow run out of memory, there is an known issue  
with

ZFS which causes livelock when there is memory pressure.  Which rsync
version are you using?  With rsync 3.x the memory usage would drop
drastically which would help to prevent this from happening.


This isn't known to cause a double fault though.  Unfortunately we  
probably need more information than was available in order to proceed.


Yes, I agree. But I don't know what to do in this sort of case where  
the machine is completely wedged.


Ben

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

Re: Panic after hung rsync, probably zfs related

[Ben Stuyts]

On 14 mei 2008, at 10:50, Kostik Belousov wrote:


3.5Gb wired ? Do you run amd64 ?


Yes.


Does wired memory drops lower after you change the load ?



Sorry, forgot to answer this in my previous msg.

It is very unpredictable, and I have not found a pattern. It is a  
small business server, and both during non-office and regular office  
hours the wired memory varies between the numbers above.


Ben

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

Re: Xorg keyboard and mouse hung

[Ben Stuyts]

On 10 jun 2009, at 18:58, Paul Schmehl wrote:

--On Wednesday, June 10, 2009 10:02:39 -0500 Ben Stuyts > wrote:



I've upgrade two FreeBSD 7-stable workstations to the latest kernel/
world of today, and now the mouse and keyboard don't react anymore in
the Xorg / KDE login window. Mouse doesn't move, keyboard characters
don't appear in the login prompt. I can still switch back with ctl- 
alt-
F1 to a console login, and there both the keyboard and mouse still  
work.


I have attached dmesg.boot and Xorg.0.log. I'm not using a xorg.conf
as the default settings used to work fine.

Any ideas?


Sure.  In your Xorg.0.log file:

"(==) ModulePath set to "/usr/local/lib/xorg/modules"
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
	If no devices become available, reconfigure HAL or disable  
AllowEmptyInput"


add dbus_enable="YES" and hald_enable="YES" to /etc/rc.conf.  Then  
start them both manually (/usr/local/etc/rc.d/hald start and /usr/ 
local/etc/rc.d/dbus start).  Then restart X (Ctrl-Alt-Bkspc)


I missed that somehow in UPDATING. Thanks!

Kind regards,
Ben

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Multiple USB drives stability question

[Ben Stuyts]

Jeff,

On 15 aug 2009, at 05:04, Jeff Richards wrote:

(da6:umass-sim6:6:0:0): SYNCHRONIZE CACHE(10). CDB: 35 0 0 0 0 0 0 0  
0 0

...

I've had lots of stability issues with USB drives until I added some  
quirks to prevent the SYNCHRONIZE CACHE from happening. For example:


Index: cam/scsi/scsi_da.c
===
RCS file: /usr/ncvs/src/sys/cam/scsi/scsi_da.c,v
retrieving revision 1.224.2.6
diff -r1.224.2.6 scsi_da.c
539a540,547
> * LaCie external 250GB Hard drive designed by Porsche
> * PR: usb/121474
> */
>{T_DIRECT, SIP_MEDIA_FIXED, "SAMSUNG", "HM250JI", "*"},
>/*quirks*/ DA_Q_NO_SYNC_CACHE
>},
>{
>/*

You might try that, and see if it improves your situation.

Ben

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

ZFS v13 on FreeBSD 7 release/fixit iso's?

[Ben Stuyts]

Hi,

I've recently upgraded a few FreeBSD-7-stable servers, and I see ZFS  
v13 has made it into the tree. From what I can tell, the existing 7.2  
release & fixit cd's do not support v13 yet.


I'd rather not upgrade the pools without a rescue cd available... Are  
there any 7-stable iso's available which support zfs v13?


Ben

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS v13 on FreeBSD 7 release/fixit iso's?

[Ben Stuyts]

On 16 okt 2009, at 18:47, Michael Proto wrote:


On Fri, Oct 16, 2009 at 11:58 AM, Ben Stuyts  wrote:


I've recently upgraded a few FreeBSD-7-stable servers, and I see  
ZFS v13 has
made it into the tree. From what I can tell, the existing 7.2  
release &

fixit cd's do not support v13 yet.

I'd rather not upgrade the pools without a rescue cd available...  
Are there

any 7-stable iso's available which support zfs v13?


How about ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200906/ ?


Thanks!

Ben

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: ZFS v13 on FreeBSD 7 release/fixit iso's?

[Ben Stuyts]

On 16 okt 2009, at 20:57, Vincent Hoffman wrote:


Michael Proto wrote:

On Fri, Oct 16, 2009 at 11:58 AM, Ben Stuyts  wrote:

I've recently upgraded a few FreeBSD-7-stable servers, and I see  
ZFS v13 has
made it into the tree. From what I can tell, the existing 7.2  
release &

fixit cd's do not support v13 yet.

I'd rather not upgrade the pools without a rescue cd available...  
Are there

any 7-stable iso's available which support zfs v13?


How about ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/200906/ ?


or indeed from
http://pub.allbsd.org/FreeBSD-snapshots/


Hey, that's neat, thanks! The second site is a lot more up to date  
than the former.


Ben

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Error in buildworld: stable/10/usr.bin/find

[Ben Stuyts]

Hi,

I am updating a few 10-stable FreeBSD servers to r326767, and buildworld fails 
with:

/usr/src/usr.bin/find/function.c:902:5: error: use of undeclared identifier 
'exitstatus'
exitstatus = 1;
^

Unless I’m mistaken, I think this is caused by svn commit: r326763 - 
stable/10/usr.bin/find. Could somebody please have a look at this?

Thanks,
Ben

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

Re: Error in buildworld: stable/10/usr.bin/find

[Ben Stuyts]

> On 11 Dec 2017, at 16:00, Ben Stuyts  wrote:
> 
> Hi,
> 
> I am updating a few 10-stable FreeBSD servers to r326767, and buildworld 
> fails with:
> 
> /usr/src/usr.bin/find/function.c:902:5: error: use of undeclared identifier 
> 'exitstatus'
>exitstatus = 1;
>^
> 
> Unless I’m mistaken, I think this is caused by svn commit: r326763 - 
> stable/10/usr.bin/find. Could somebody please have a look at this?

Fixed (reverted) in r326790.

Ben

___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"

mt stuck in cbwait

[Ben Stuyts]

Hi,
During the nightly backup the tape drive gave some errors and now the 
mt process seems to be stuck in cbwait mode. ps -axl says:

0 44326 1   0  -6  0   916  348 cbwait D ??0:00.00 mt 
-f /dev/nsa0 rewind

I tried several different KILL's but got nowhere. I manually ejected 
the tape and put another back in again, but that didn't wake it up 
either. Is there anything else I can try before rebooting the server 
and killing 198 days of uptime?

uname -a:
FreeBSD earth.altus-escon.com 4.10-BETA FreeBSD 4.10-BETA #12: Mon Apr 
19 06:48:13 CEST 2004 
[EMAIL PROTECTED]:/home2/obj/usr/src/sys/EARTH  i386

Drive:
sa0 at ahc0 bus 0 target 3 lun 0
sa0:  Removable Sequential Access SCSI-2 device
sa0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit)
SCSI controller:
ahc0:  port 0xa800-0xa8ff mem 
0xdfffa000-0xdfffafff irq 11 at device 9.0 on pci0

Errors:
Nov  3 02:46:22  earth /kernel: (sa0:ahc0:0:3:0): WRITE 
FILEMARKS. CDB: 10 0 0 0 2 0
Nov  3 02:46:22  earth /kernel: (sa0:ahc0:0:3:0): MEDIUM 
ERROR info:2 csi:0,0,87,42 asc:15,2
Nov  3 02:46:22  earth /kernel: (sa0:ahc0:0:3:0): 
Positioning error detected by read of medium
Nov  3 02:46:22  earth /kernel: (sa0:ahc0:0:3:0): failed to 
write terminating filemark(s)
...
Nov  3 03:02:37  earth /kernel: (sa0:ahc0:0:3:0): tape is 
now frozen- use an OFFLINE, REWIND or MTEOM command to clear this 
state.
Nov  3 05:02:49  earth /kernel: (sa0:ahc0:0:3:0): SCB 0x6 - 
timed out
Nov  3 05:02:49  earth /kernel: (sa0:ahc0:0:3:0): Queuing a 
BDR SCB
Nov  3 05:02:49  earth /kernel: (sa0:ahc0:0:3:0): Bus Device 
Reset Message Sent
Nov  3 05:02:49  earth /kernel: (sa0:ahc0:0:3:0): no longer 
in timeout, status = 34b
Nov  3 07:02:49  earth /kernel: (sa0:ahc0:0:3:0): SCB 0xe - 
timed out
etc...

With kind regards,
Ben
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: ATA mkIII first official patches - please test!

[Ben Stuyts]

On 3 Feb 2005, at 21:52, Søren Schmidt wrote:
o   ATA RAID can only read metadata not write them. This means that
arrays can be picked up from the BIOS, but they cannot be 
created
from FreeBSD. This is being worked on for the final release as 
is
RAID5 support for Promise/Highpoing/SiI controllers.
Will RAID mirrors built using atacontrol on standard ata controllers 
still work? Specifically in my case on 5.3-stable:

atapci0:  port 
0xf000-0xf00f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 31.1 on 
pci0
ata0: channel #0 on atapci0
ata1: channel #1 on atapci0
ad0: 117246MB  [238216/16/63] at ata0-master 
UDMA100
ad2: 117246MB  [238216/16/63] at ata1-master 
UDMA100

and:
[aurora:~]138: sudo atacontrol status 0
ar0: ATA RAID1 subdisks: ad0 ad2 status: READY
Thanks,
Ben
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Can't boot after adding tx2plus interface

[Ben Stuyts]

Hi,

I am trying to add a Promise Tx2plus card to my FreeBSD releng_6  
system. Without the card, it works fine. See dmesg at the end of this  
message. But after adding the card and hooking up a few drives, the  
loader seems confused about the boot device, and I get the following  
error (transcripted by hand):


Can't work out which disk we are booting from.
Guessed BIOS device 0x nout found by probes, defaulting to  
disk0:
panic: free: guard1 [EMAIL PROTECTED] from /sources/src/sys/boot/i386/ 
loader/../../common/module.c:958

--> Press a key on the console to reboot <--

I tried to boot from CD, but this also fails with the TX2plus card  
present. As soon as it starts loading from the CD, it resets. Just a  
black screen, and back to the bios memory test. No error messages  
visible.


If I just add the card without adding any drives to it, booting works  
correctly and sees the new ata channels. The difference is probably  
that the card's bios is not loaded, and so the FreeBSD loader does  
not get confused.


Any ideas what else I can try?

Thanks,
Ben

dmesg output without the tx2plus:

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-STABLE #0: Wed Mar 14 00:47:38 CET 2007
[EMAIL PROTECTED]:/wd/obj/usr/src/sys/AURORA
ACPI APIC Table: 
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.40GHz (2411.60-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
   
Features=0xbfebfbff,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>

  Features2=0x4400>
  Logical CPUs per core: 2
real memory  = 1610547200 (1535 MB)
avail memory = 1564856320 (1492 MB)
ioapic0: Changing APIC ID to 2
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
ath_hal: 0.9.20.3 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413,  
RF5413)

acpi0:  on motherboard
acpi0: Power Button (fixed)
cpu0:  on acpi0
acpi_button0:  on acpi0
pcib0:  port 0xcf8-0xcff,0x1000-0x10bf on acpi0
pci0:  on pcib0
agp0:  mem 0xe800-0xefff at  
device 0.0 on pci0

pcib1:  at device 1.0 on pci0
pci1:  on pcib1
pci1:  at device 0.0 (no driver attached)
pcib2:  at device 3.0 on pci0
pci2:  on pcib2
em0:  port  
0xa000-0xa01f mem 0xfa00-0xfa01 irq 18 at device 1.0 on pci2

em0: Ethernet address: 00:20:ed:83:19:ca
uhci0:  port 0xb000-0xb01f  
irq 16 at device 29.0 on pci0

uhci0: [GIANT-LOCKED]
usb0:  on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1:  port 0xb400-0xb41f  
irq 19 at device 29.1 on pci0

uhci1: [GIANT-LOCKED]
usb1:  on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2:  port 0xb800-0xb81f  
irq 18 at device 29.2 on pci0

uhci2: [GIANT-LOCKED]
usb2:  on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
uhci3:  port 0xbc00-0xbc1f  
irq 16 at device 29.3 on pci0

uhci3: [GIANT-LOCKED]
usb3:  on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
ehci0:  mem  
0xfa20-0xfa2003ff irq 23 at device 29.7 on pci0

ehci0: [GIANT-LOCKED]
usb4: EHCI version 1.0
usb4: companion controllers, 2 ports each: usb0 usb1 usb2 usb3
usb4:  on ehci0
usb4: USB revision 2.0
uhub4: Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub4: 8 ports with 8 removable, self powered
umass0: Western Digital External HDD, rev 2.00/0.00, addr 2
pcib3:  at device 30.0 on pci0
pci3:  on pcib3
fwohci0:  mem 0xfa104000-0xfa1047ff, 
0xfa10-0xfa103fff irq 22 at device 10.0 on pci3

fwohci0: OHCI version 1.10 (ROM=1)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:20:ed:0a:00:86:78:40
fwohci0: Phy 1394a available S400, 3 ports.
fwohci0: Link S400, max_rec 2048 bytes.
firewire0:  on fwohci0
fwe0:  on firewire0
if_fwe0: Fake Ethernet address: 02:20:ed:86:78:40
fwe0: Ethernet address: 02:20:ed:86:78:40
fwe0: if_start running deferred for Giant
sbp0:  on firewire0
fwohci0: Initiate bus reset
fwohci0: node_id=0xc800ffc0, gen=1, CYCLEMASTER mode
firewire0: 1 nodes, maxhop <= 0, cable IRM = 0 (me)
firewire0: bus manager 0 (me)
isab0:  at device 31.0 on pci0
isa0:  on isab0
atapci0:  port  
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 31.1 on pci0

ata0:  on atapci0
ata1:  on atapci0
atapci1:  port  
0xc000-0xc007,0xc400-0xc403,0xc800-0xc807,0xcc00-0xcc03,0xd000-0xd00f  
irq 18 at device 31.2 on pci0

ata2:  on atapci1
ata3:  on atapci1
pci0:  at device 31.3 (no driver attached)
pcm0:  port 0xd800-0xd8ff,0xdc00-0xdc3f mem  
0xfa201000-0xfa2011ff,0xfa202000-0xfa2020ff irq 17 at device 31.5 on  
pci0

Any known problems with a 3C996B-T?

[Ben Stuyts]

Hi,

I am about to upgrade one of our servers (running 4-stable) with a  
1000Base-T network card, and the 3Com 3C996B-T looks interesting.  
This is for a small office server (e-mail, files, printers,  
webserver) serving about 25 pc's running a variety of Win2K, FreeBSD  
and Mac OS X.


I found some messages in the past indicating there were some problems  
with this card on FreeBSD. Are these problems solved? I also did not  
see this exact card in the hardware list, although the 3c996-SX and  
3c996-T are mentioned.


Otherwise, any recommendations?

With kind regards,
Ben

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

Stable on Supermicro server?

[Ben Stuyts]

Hi,
I am planning on building a FreeBSD server with a Supermicro 5013C-T 1U 
server. It has a Supermicro P4SCE motherboard, with a P4 of around 2.8 
GHz, and 512MB or 1 GB memory. I am planning on adding two Western 
Digital Raptor 74 GB SATA drives in mirror.

It will be mainly used as a web server for 5-10 sites, running Apache 
with php and mySql, and a (probably not heavily loaded) mail server.

Perhaps the disks are a bit overkill for this, but I like the 5 year 
warranty, and the server will be located in a data center where I can't 
easily go.

Will this combination work with -stable? Is it truly stable? Are there 
any known problems?

Thanks for any info,
Ben
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: Stable on Supermicro server?

[Ben Stuyts]

On 14 Jul 2004, at 02:12, Chris Foote wrote:
On Tue, 13 Jul 2004, Ben Stuyts wrote:
I am planning on building a FreeBSD server with a Supermicro 5013C-T 
1U server. It has a Supermicro P4SCE motherboard, with a P4 of around 
2.8 GHz, and 512MB or 1 GB memory. I am planning on adding two 
Western Digital Raptor 74 GB SATA drives in mirror.

The SATA RAID controller, although it provides a 'legacy' option
which should expose the RAID as an ordinary device, doesn't work
despite the fact that both disk drives' LEDs flash when RAID 1 is
enabled ;-(  The RAID isn't supported by almost any operating system.
So I'm not sure I understand fully: is there a way to connect the sata 
drives to the onboard ich5 controller, and make them work as separate 
(not raid) devices? In that case I could use vinum.

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