[releng_8 tinderbox] failure on i386/i386
TB --- 2010-09-05 06:17:15 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-09-05 06:17:15 - starting RELENG_8 tinderbox run for i386/i386 TB --- 2010-09-05 06:17:15 - cleaning the object tree TB --- 2010-09-05 06:17:59 - cvsupping the source tree TB --- 2010-09-05 06:17:59 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/RELENG_8/i386/i386/supfile TB --- 2010-09-05 06:55:16 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2010-09-05 06:55:16 - ERROR: unable to cvsup the source tree TB --- 2010-09-05 06:55:16 - 1.18 user 28.98 system 2280.93 real http://tinderbox.freebsd.org/tinderbox-releng_8-RELENG_8-i386-i386.full ___ 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: Why is NFSv4 so slow?
- Original Message - > On Wed, Sep 01, 2010 at 11:46:30AM -0400, Rick Macklem wrote: > > > > > > I am experiencing similar issues with newnfs: > > > > > > 1) I have two clients that each get around 0.5MiB/s to 2.6MiB/s > > > reading > > > from the NFS4-share on Gbit-Lan > > > > > > 2) Mounting with -t newnfs -o nfsv3 results in no performance gain > > > whatsoever. > > > > > > 3) Mounting with -t nfs results in 58MiB/s ! (Netcat has similar > > > performance) ??? not a hardware/driver issue from my pov > > > > Ok, so it does sound like an issue in the experimental client and > > not NFSv4. For the most part, the read code is the same as > > the regular client, but it hasn't been brought up-to-date > > with recent changes. > > Do you (or will you soon) have some patches I/we could test? I'm > willing to try anything to avoid mounting ten or so subdirectories in > each of my mount points. > One other thing you could do is run this in a loop while you have a slow read running. The client threads must be blocked somewhere a lot if the read rate is so slow. (Then take a look at "xxx" and please email it to me too.) ps axHl >> xxx sleep 1 rick ___ 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: Why is NFSv4 so slow?
>
> Do you (or will you soon) have some patches I/we could test? I'm
> willing to try anything to avoid mounting ten or so subdirectories in
> each of my mount points.
>
Attached is a small patch for the only difference I can spot in the read
code between the regular and experimental NFS client.
I have asked jhb@ to try and do some testing, to see if he can reproduce
it. If he does reproduce it, maybe he can figure out what is going on.
(I don't think I'll have any further patches to try, unless he spots
something.)
> > One thing you could try is building a kernel without SMP enabled
> > and see if that helps? (I only have single core hardware, so I won't
> > see any SMP races.) If that helps, I can compare the regular vs
> > experimental client for smp locking in the read stuff.
>
> I can try disabling SMP too. Should that really matter, if you're not
> even pegging one CPU? The locks shouldn't have *that* much overhead...
>
> -- Rick C. Petty
>
If running UMP fixes the problem, it is most likely a missing lock that
allows a race to put things in a weird state. But for these things, it
is often something I'd never expect that turns out to be the culprit.
rick
--- fs/nfsclient/nfs_clbio.c.sav 2010-09-04 10:46:06.0 -0400
+++ fs/nfsclient/nfs_clbio.c 2010-09-04 10:47:06.0 -0400
@@ -510,10 +510,7 @@
rabp = nfs_getcacheblk(vp, rabn, biosize, td);
if (!rabp) {
error = newnfs_sigintr(nmp, td);
-if (error)
-return (error);
-else
-break;
+return (error ? error : EINTR);
}
if ((rabp->b_flags & (B_CACHE|B_DELWRI)) == 0) {
rabp->b_flags |= B_ASYNC;
___
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: apcupsd, USB and FreeBSD 8.1 aren't getting along
At 04:44 PM 9/3/2010, Ben Schumacher wrote: All- It seems that something about the combination of FreeBSD 8.1 and apcupsd connecting to an APC Back-UPS RS 1500. Here's what I've got: 1. FreeBSD 8.1 (source compiled up to RELENG_8_1 for security fixes) 2. apcupsd 3.14.8 compiled from FreeBSD Ports 3. APC Back-UPS RS 1500 Hi, I am running RELENG_8 with such a ups. 8.1-STABLE FreeBSD 8.1-STABLE #1: Wed Sep 1 11:42:00 EDT 2010 % apcaccess APC : 001,038,0989 DATE : 2010-09-04 07:32:09 -0400 HOSTNAME : backup3.sentex.ca VERSION : 3.14.8 (16 January 2010) freebsd UPSNAME : RAPIDS CABLE: USB Cable MODEL: Back-UPS RS 1500 UPSMODE : Stand Alone STARTTIME: 2010-09-01 12:05:12 -0400 STATUS : ONLINE LINEV: 117.0 Volts LOADPCT : 38.0 Percent Load Capacity BCHARGE : 100.0 Percent TIMELEFT : 83.5 Minutes MBATTCHG : 10 Percent MINTIMEL : -1 Minutes MAXTIME : 0 Seconds SENSE: Medium LOTRANS : 097.0 Volts HITRANS : 132.0 Volts ALARMDEL : 30 seconds BATTV: 26.9 Volts LASTXFER : Low line voltage NUMXFERS : 1 XONBATT : 2010-09-01 16:27:30 -0400 TONBATT : 0 seconds CUMONBATT: 26 seconds XOFFBATT : 2010-09-01 16:27:56 -0400 SELFTEST : NO STATFLAG : 0x0708 Status Flag MANDATE : 2007-09-07 SERIALNO : 8B0736R21784 BATTDATE : 2007-09-07 NOMINV : 120 Volts NOMBATTV : 24.0 Volts NOMPOWER : 865 Watts FIRMWARE : 8.g9a.D USB FW:g9a APCMODEL : Back-UPS RS 1500 END APC : 2010-09-04 07:32:37 -0400 I just leave the DEVICE line blank UPSNAME STATN UPSCABLE usb UPSTYPE usb DEVICE LOCKFILE /var/spool/lock ONBATTERYDELAY 7 BATTERYLEVEL 10 MINUTES -1 TIMEOUT 0 ANNOY 10 ANNOYDELAY 10 NOLOGON disable KILLDELAY 2 NETSERVER on NISIP 127.0.0.1 NISPORT 3551 EVENTSFILE /var/log/apcupsd.events EVENTSFILEMAX 100 UPSCLASS standalone UPSMODE disable STATTIME 600 STATFILE /var/log/apcupsd.status LOGSTATS off DATATIME 600 FACILITY local2 UPSNAME RAPIDS SENSITIVITY H WAKEUP 010 SLEEP 000 RETURNCHARGE 00 BEEPSTATE T SELFTEST 336 You dont need to do any symlinks in /dev # usbconfig -d 5.2 dump_device_desc ugen5.2: Conversion> at usbus5, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0110 bDeviceClass = 0x bDeviceSubClass = 0x bDeviceProtocol = 0x bMaxPacketSize0 = 0x0008 idVendor = 0x051d idProduct = 0x0002 bcdDevice = 0x0106 iManufacturer = 0x0003 iProduct = 0x0001 iSerialNumber = 0x0002 <8B0736R21784 > bNumConfigurations = 0x0001 ---Mike Mike Tancsa, tel +1 519 651 3400 Sentex Communications,m...@sentex.net Providing Internet since 1994www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike ___ 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"
