Date: Fri, 21 Dec 2001 11:06:46 -0500 From: Sam Suh <sam@bigstudios.com> To: freebsd-questions@freebsd.org Subject: NFS broken? Message-ID: <3C235E16.C139FDF1@bigstudios.com>
next in thread | raw e-mail | index | archive | help
Hi, everyone.
I don't know if I am the first one to suspect this but I think there
maybe a problem with NFS in 4.4 stable. I recently setup the RAID 5
machine which will serve as file server. I have 512MB ram with 650MHz
PIII and 5 IDE drives ( 1 system drive of 20GB, 4 RAID composed of 3
RAID volume and one hot spare. Each has 93GB WD Caviar 1000BB ), Adaptec
2400A. I have created RAID volume and small partition of system drive as
NFS volume. I been having difficulties with SGI and 4.1 machine seeing
this volume correctly. Given the nature of our shop, it is norm to have
over 900+ files within single directory. Present file server on IRIX
does not have any problems with these; however, new 4.4 based RAID
machine I have created displays much problems. For examples, after
mounting RAID volume on IRIX or 4.1 machine, ls on directories with many
files simply wouldn't turn up. IRIX will set there forever and finally
tells me this:
IRIX /n/exportedNFS/$ ls
total 0
IRIX /n/exportedNFS/$
On 4.1, matter is more complicated. It becomes a zombie process and
wouldn't even die. Not to mention not letting umount the NFS in
question. So, naturally, I thought it may something to do with NFS
configuration or RAID card. However, configurations are checked out fine
and rpcinfo informs me it is up and running OK. Puzzled, I did exported
the system drive partition (/tmp) and tried to mount on 4.1 and IRIX.
They are both mounted fine but simple 'ls' will produce same result.
Worse, I experienced a crash when I did a test with copying some files
from RAID volume to new share on system drive. Before I had chance to
look at the error, it rebooted itself. When booted, I saw fsck was doing
salvage on new share. Now I am really alarmed.
Now, I am not sure if it is something to do with hardware anymore. Does
anyone know of any bugs introduced to 4.4 stable distribution?
Below is my rc.conf, exports and dmesg
<rc.conf>
ifconfig_bge0="inet 192.168.75.108 netmask 255.255.255.0"
defaultrouter="192.168.75.254"
kern_securelevel_enable="NO"
linux_enable="YES"
moused_type="auto"
saver="blank"
sendmail_enable="NO"
sshd_enable="YES"
hostname="4.4 machine"
portmap_enable="YES"
nfs_server_enable="YES"
nfs_server_flags="-u -t -n 4"
mountd_flags="-r"
nfs_client_enable="YES"
nfs_client_flags="-n 4"
usbd_enable="YES"
nisdomainname="bigstudios.com"
nis_client_enable="YES"
local_startup="/usr/local/etc/rc.d"
<exports>
/jobs
/tmp
<dmesg output>
Copyright (c) 1992-2001 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 4.4-RELEASE #0: Tue Sep 18 11:57:08 PDT 2001
murray@builder.FreeBSD.org:/usr/src/sys/compile/GENERIC
Timecounter "i8254" frequency 1193182 Hz
CPU: Pentium III/Pentium III Xeon/Celeron (651.48-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x681 Stepping = 1
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory = 536858624 (524276K bytes)
avail memory = 518107136 (505964K bytes)
Preloaded elf kernel "kernel" at 0xc048c000.
Preloaded elf module "bcmphy.ko" at 0xc048c09c.
Preloaded elf module "if_bge.ko" at 0xc048c13c.
Pentium Pro MTRR support enabled
md0: Malloc disk
Using $PIR table, 6 entries at 0xc00f0c80
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcib0: <Host to PCI bridge> on motherboard
pci0: <PCI bus> on pcib0
pcib2: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0
on pci0
pci1: <PCI bus> on pcib2
pci1: <3D Labs model 000a graphics accelerator> at 0.0 irq 11
isab0: <VIA 82C596B PCI-ISA bridge> at device 4.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <VIA 82C596 ATA66 controller> port 0xd800-0xd80f at device 4.1
on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
pci0: <unknown card> (vendor=0x1274, dev=0x1371) at 10.0 irq 5
bge0: <Broadcom BCM5700 Gigabit Ethernet> mem 0xd6800000-0xd680ffff irq
10 at device 11.0 on pci0
bge0: Ethernet address: 00:04:76:3b:4a:08
miibus0: <MII bus> on bge0
bcmphy0: <BCM5401 10/100/1000baseTX PHY> on miibus0
bcmphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX,
1000baseTX-FDX, auto
pcib3: <PCI to PCI bridge (vendor=1044 device=a500)> at device 12.0 on
pci0
pci2: <PCI bus> on pcib3
asr0: <Adaptec Caching SCSI RAID> mem 0xd8000000-0xd9ffffff irq 11 at
device 12.1 on pci0
asr0: major=154
asr0: ADAPTEC 2400A FW Rev. 370L, 4 channel, 256 CCBs, Protocol I2O
pcib1: <Host to PCI bridge> on motherboard
pci3: <PCI bus> on pcib1
orm0: <Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff on isa0
fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on
isa0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model Generic PS/2 mouse, device ID 0
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on
isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
ad0: 27199MB <ST328040A> [55262/16/63] at ata0-master UDMA33
acd0: CDROM <MATSHITA CR-593> at ata1-master using PIO4
Mounting root from ufs:/dev/ad0s1a
da0 at asr0 bus 0 target 0 lun 0
da0: <ADAPTEC RAID-5 370L> Fixed Direct Access SCSI-2 device
da0: Tagged Queueing Enabled
da0: 190792MB (390742016 512 byte sectors: 255H 63S/T 24322C)
WARNING: / was not properly dismounted
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C235E16.C139FDF1>