NFS woes: getting worse?
I have duplicated on two pairs of machines a case whereby you have two -current machines as of ~20:00 UTC 1999/Jan/14 which cannot interoperate via NFS without corruption. To repeat: create a ports tree on one, mount it on the other. Have the client 'cd /usr/ports/x11/XFree86-contrib; make'. As soon as it extracts the distfile and starts working, it blows up: === Configuring for XFree86-contrib-3.3.3 mv -f Makefile Makefile.bak imake -DUseInstalled -I/usr/X11R6/lib/X11/config make Makefiles making Makefiles in programs... mv -f Makefile Makefile.bak making Makefiles in programs/ico... mv -f Makefile Makefile.bak make: don't know how to make Makefiles. Stop making Makefiles in programs/listres... mv -f Makefile Makefile.bak etc. Softupdates and version -2 mounts do not affect the problem, and it builds fine on a local disk. I have done some work with ktrace and tcpdump and can see that files are being returned shorter from the NFS server than they really are. For example, on the server machine's local disk, ktrace showed one file read this way: 14820 make RET read 0 14820 make RET read 8192/0x2000 14820 make RET read 8192/0x2000 14820 make RET read 2845/0xb1d 14820 make RET read 0 On the client side, I isolated the same part of the corresponding ktrace and saw that it got: 13748 make RET read 0 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 512/0x200 13748 make RET read 114/0x72 13748 make RET read 0 18034 bytes read by the NFS client, 19229 bytes read on the local system! The file shown in the kdump output above is Makefile (see path below), and we can see that it's true size is 19229. This is just one instance of the problem. skynyrd:/usr/ports/x11/XFree86-contrib/work/contrib# ls -l programs/ico/ total 64 -rw-r--r-- 1 root wheel282 Jun 4 1994 Imakefile -rw-r--r-- 1 root wheel 19229 Jan 14 19:53 Makefile SO, it looks like there is some sort of arithmetic error going on? I have copious amounts of debugging info here, but have to run at the moment. If someone else can reproduce the problem I can send-pr all of it Sigh. -Chris To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Looking for Suggestion on Booting FreeBSD 3.0 on a Gigabyte GA-6BXDS board with Dual Pentiun II and Adaptec 7895 Ultra Wide SCSI-3 Controlers
Hi David, Cory, Dave, Folks: I thought it was about time to try out FreeBSD, most likely 3.0, so I picked up a PC board from Gigabyte, the GA-6BXDS Dual Scsi-3 that has an onboard Adaptec 7895 controler. About a year ago you (David) said Justin was working on a 7895 scsi controler. I didn't see anything in the FreeBSD handbook on support for the Adaptic 7895 (seems to be getting rather out of date). Now I've read from Cory that you need a CAM scsi driver. Last I see it was still only available as patches. Why is it taking so long to get it integrated into the current src? So I have to get an IDE drive and install onto that, get the CAM patches (from where?), run patch, etc... and linux supports it a standard controler? I can't believe this. Perhaps you could update me on the 7895 support and perhaps have some suggestion on setting up this board to run FreeBSD. For example can I boot the 3.0 FreeBSD off of a CDROM on the scsi adapters; I sort of doubt it. Is the FreeBSD getting the information it needs from Gigabyte and Adaptec so that these boards are well supported? -piet To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NFS woes: getting worse?
SO, it looks like there is some sort of arithmetic error going on? I have copious amounts of debugging info here, but have to run at the moment. If someone else can reproduce the problem I can send-pr all of it At this point, filing a PR is not going to help much. Diving into the code and working out what's going wrong is what it's going to take. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ m...@smith.net.au \\ The race is long, and in the \\ msm...@freebsd.org \\ end it's only with yourself. \\ msm...@cdrom.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: Looking for Suggestion on Booting FreeBSD 3.0 on a Gigabyte
On 15-Jan-99 Piet Delaney wrote: () I thought it was about time to try out () FreeBSD, most likely 3.0, so I picked up a PC () board from Gigabyte, the GA-6BXDS Dual Scsi-3 () that has an onboard Adaptec 7895 controler. () About a year ago you (David) said Justin was working () on a 7895 scsi controler. I didn't see anything () in the FreeBSD handbook on support for the Adaptic () 7895 (seems to be getting rather out of date). () Now I've read from Cory that you need a CAM scsi () driver. Last I see it was still only available as () patches. Why is it taking so long to get it integrated () into the current src? So I have to get an IDE drive and () install onto that, get the CAM patches (from where?), () run patch, etc... and linux supports it a standard () controler? I can't believe this. 3.0-RELEASE and newer uses CAM as default supporting 7895 and a bunch of other newer Adaptec chipsets. We have three machines here with an Asus P2B-S motherboard that run fine. We have recently upgraded all of them to the 3.0-CURRENT tree as we run a local CVS archive. Seems like your information is pretty old. We have decided to use -CURRENT for what is usually called a production machine that won´t run very critical applications these days (our own fax server, our own news server, experimental database server). So we will see if it runs stable enough for our purpose. For now, it looks very good and we didn't experience any serious problems yet. () Perhaps you could update me on the 7895 support () and perhaps have some suggestion on setting up this () board to run FreeBSD. For example can I boot the () 3.0 FreeBSD off of a CDROM on the scsi adapters; () I sort of doubt it. My 3.0-RELEASE CD-ROM had no problems booting on the machines mentioned above. They also had no problems with running a custom install :-) Look at http://www.freebsd.org/ (which is always a good starting point for asking most main questions about FreeBSD) at the release information for 3.0. It says: 1. What's new since 2.2.X-RELEASE - All changes described here are unique to the 3.0 branch unless specifically marked as [MERGED] features. 1.1. KERNEL CHANGES --- o The 2.2.x SCSI subsystem has been almost entirely replaced with a new CAM (Common Access Method) SCSI system which offers improved performance, better error recovery and support for more SCSI controllers. (and it says more, of course, but I didn´t to quote that all) There is also a 2.2-CAM tree available, but I have no experiences with that, look at ftp.freebsd.org. Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher Partnerfax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13http://www.freibergnet.de/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Changes to ahc driver broke kernel
There were some changes made to ahc driver made on 1/13/99 And i can no longer boot a current kernel A kernel from 1/12/99 works fine When booting after : SMP: AP CPU #1 Launched It stalls for awhile and then I get these messages (probe4:ahc0:0:4:0) SCB 0x5 timed out in message phase SEQADDR == 0x155 (probe4:ahc0:0:4:0) BDR message in message buffer ahc0: Issued Channel A Bus Reset. 3 SCBs aborted and on and on This is a Intel PR440FX with builtin adaptec scsi and dual PPro processors Also on board is a DPT SCSI PM2124A Raid controller (no RAID drives). The adaptec usually has a cdrom hooked to it, sometime a exabyte and aux harddrive FreeBSD is installed on the disk controlled by the DPT Thanks Manfred = ||man...@netcom.com|| ||p...@infinex.com || ||Ph. (415) 681-6235|| = To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Current doesn't build in texinfo
Pascal Hofstee wrote: config.h: No such file or directory *** Error code 1 Fixed! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: make buildworld break on texinfo
Joe Abley wrote: m.c:19: config.h: No such file or directory *** Error code 1 Fixed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NFS woes: getting worse?
* From: Chris Timmons skyn...@opus.cts.cwu.edu * make: don't know how to make Makefiles. Stop I've seen similar things, but they went away when I reduced the load (other compilations in my case) on the server. How busy is your server? Satoshi To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Changes to ahc driver broke kernel
There were some changes made to ahc driver made on 1/13/99 And i can no longer boot a current kernel You'll have to give me more information so that I can reproduce the problem here. A good start would be to send a complete dmesg from the system using a kernel that boots correctly for you. -- Justin To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: NFS woes: getting worse?
On Thu, Jan 14, 1999 at 08:03:46PM -0800, Chris Timmons wrote: I have duplicated on two pairs of machines a case whereby you have two -current machines as of ~20:00 UTC 1999/Jan/14 which cannot interoperate via NFS without corruption. [...] 18034 bytes read by the NFS client, 19229 bytes read on the local system! The file shown in the kdump output above is Makefile (see path below), and we can see that it's true size is 19229. This is just one instance of the problem. [...] Same problems here -- or even worse. Running -current on a NFS-server and several diskless clients attached to it (I like the silence at my desk), I get truncated files and NFS-writes with a lot of ^...@^@^...@^@^@ and some other garbage in it. The ^...@^@^...@^@^...@-pages stuff seems to be reported as a kernel bug already. I tried several options: NFS-3/2, tcp/udp, hard/soft, (w/o) intr -- without success. At the time (src-cur.3702.gz/~12th Jan) even vi is not usable at all on the client side with a couple of files. Being very busy at the moment I don't have time to track this down myself. Bjoern To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
