NFS client over udp
Good Day! I have a reproducible memory leak when using nfs client with an old nfs server using udp protocol. I'm running rsync every hour from a mounted nfs volume to an ufs local volume. Each time rsync is running wired memory is increased. Wired memory is rising when rsync is in getblk or biord state. When rsync is complete memory is not freed and lately all memory is in active or wired state and system starts swapping. I didn't see such behavior when client os was RELEASE-8.0. Then i switched to STABLE-8.1 of late summer and found this leak so i upgraded to STABLE-8.2Prerelease and got the same leak. vmstat -m shows nothing big. client version: FreeBSD imap1.***.com 8.2-PRERELEASE FreeBSD 8.2-PRERELEASE #0: Thu Feb 17 13:54:25 MSK 2011 root@imap1..com:/usr/obj/usr/src/sys/IMAP1 amd64 i tried different mounting options: 1 - rw,rsize=32768,wsize=32768,nfsv3,intr,mntudp,rdirplus, readdirsize=65536,noauto,noexec 2 - rw,nfsv3,mntudp,noexec i also tried setting -tso -txcsum -rxcsum for igb network card Regards, Kirill ___ 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: NFS client over udp
On Fri, Feb 18, 2011 at 05:27:00AM -0800, Kirill Yelizarov wrote: > I have a reproducible memory leak when using nfs client with an old > nfs server using udp protocol. I'm running rsync every hour from a > mounted nfs volume to an ufs local volume. Each time rsync is running > wired memory is increased. Wired memory is rising when rsync is in > getblk or biord state. When rsync is complete memory is not freed and > lately all memory is in active or wired state and system starts > swapping. I didn't see such behavior when client os was RELEASE-8.0. > Then i switched to STABLE-8.1 of late summer and found this leak so i > upgraded to STABLE-8.2Prerelease and got the same leak. vmstat -m > shows nothing big. > > client version: FreeBSD imap1.***.com 8.2-PRERELEASE FreeBSD > 8.2-PRERELEASE #0: Thu Feb 17 13:54:25 MSK 2011 > root@imap1..com:/usr/obj/usr/src/sys/IMAP1 amd64 > > i tried different mounting options: 1 - > rw,rsize=32768,wsize=32768,nfsv3,intr,mntudp,rdirplus, > readdirsize=65536,noauto,noexec 2 - rw,nfsv3,mntudp,noexec > > i also tried setting -tso -txcsum -rxcsum for igb network card Is ZFS in use on the system which sees rising wired memory? -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: NFS client over udp
--- On Fri, 2/18/11, Jeremy Chadwick wrote: > From: Jeremy Chadwick > Subject: Re: NFS client over udp > To: "Kirill Yelizarov" > Cc: freebsd-stable@freebsd.org > Date: Friday, February 18, 2011, 5:05 PM > On Fri, Feb 18, 2011 at 05:27:00AM > -0800, Kirill Yelizarov wrote: > > I have a reproducible memory leak when using nfs > client with an old > > nfs server using udp protocol. I'm running rsync every > hour from a > > mounted nfs volume to an ufs local volume. Each time > rsync is running > > wired memory is increased. Wired memory is rising when > rsync is in > > getblk or biord state. When rsync is complete memory > is not freed and > > lately all memory is in active or wired state and > system starts > > swapping. I didn't see such behavior when client os > was RELEASE-8.0. > > Then i switched to STABLE-8.1 of late summer and found > this leak so i > > upgraded to STABLE-8.2Prerelease and got the same > leak. vmstat -m > > shows nothing big. > > > > client version: FreeBSD imap1.***.com 8.2-PRERELEASE > FreeBSD > > 8.2-PRERELEASE #0: Thu Feb 17 13:54:25 MSK 2011 > > root@imap1..com:/usr/obj/usr/src/sys/IMAP1 > amd64 > > > > i tried different mounting options: > 1 - > > > rw,rsize=32768,wsize=32768,nfsv3,intr,mntudp,rdirplus, > > readdirsize=65536,noauto,noexec 2 - > rw,nfsv3,mntudp,noexec > > > > i also tried setting -tso -txcsum -rxcsum for igb > network card > > Is ZFS in use on the system which sees rising wired > memory? No, ufs only. > > -- > | Jeremy Chadwick > > j...@parodius.com > | > | Parodius Networking > http://www.parodius.com/ | > | UNIX Systems Administrator > Mountain View, CA, USA | > | Making life hard for others since 1977. > PGP 4BD6C0CB > | > > ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On Thu, Feb 17, 2011 at 13:11:33 +0100, Damien Fleuriot wrote: > On 2/17/11 12:10 PM, Oliver Brandmueller wrote: > > Hi, > > > > On Thu, Feb 17, 2011 at 12:07:17PM +0100, Damien Fleuriot wrote: > >> It looks rather unhappy: > >> > >> mybsd root /usr/ports/sysutils/smartmontools > >> # > >> /usr/local/sbin/smartctl -a /dev/da0 > >> smartctl 5.40 2010-10-16 r3189 [FreeBSD 8.2-RC3 amd64] (local build) > >> Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net > >> > >> /dev/da0: No such file or directory > >> Smartctl: please specify device type with the -d option. > > > > Thanx for the test and the quick reply! I'm really getting crazy on > > this. All the SAS controllers seems to have nifty RAID features and > > stuff... *sigh* > > > > Thanx again, > > Oliver > > > > What is sad is that these controllers are becoming very mainstream now, > we're getting them more and more on Dell servers , and the fbsd project > still struggles with them (for reasons I don't know, might be LSI's > fault, might be a lack of resources or interest...) LSI has actually been working on the driver, and has almost completed their version of it. It will go into FreeBSD in the near future. In the mean time I have merged the mps(4) driver into -stable. Ken -- Kenneth Merry k...@freebsd.org ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On Thu, Feb 17, 2011 at 15:21:48 +0100, Ollivier Robert wrote: > According to Damien Fleuriot: > > I destroyed the logical volume and built mps copied from -current (I opened > > a thread on stable@ a few weeks ago about this) but my "patch" was > > *nowhere* as big as this. > > Here Ken's patch: > > amd64/conf/GENERIC |1 > conf/files |5 > dev/bwn/if_bwn.c |4 > dev/mps/mpi/mpi2.h | 1121 ++ > dev/mps/mpi/mpi2_cnfg.h | 2646 > +++ > dev/mps/mpi/mpi2_hbd.h | 114 + > dev/mps/mpi/mpi2_history.txt | 382 ++ > dev/mps/mpi/mpi2_init.h | 454 +++ > dev/mps/mpi/mpi2_ioc.h | 1414 ++ > dev/mps/mpi/mpi2_ra.h| 86 + > dev/mps/mpi/mpi2_raid.h | 302 > dev/mps/mpi/mpi2_sas.h | 285 > dev/mps/mpi/mpi2_targ.h | 441 +++ > dev/mps/mpi/mpi2_tool.h | 391 ++ > dev/mps/mpi/mpi2_type.h | 99 + > dev/mps/mps.c| 1821 + > dev/mps/mps_ioctl.h | 106 + > dev/mps/mps_pci.c| 365 + > dev/mps/mps_sas.c| 2007 > dev/mps/mps_table.c | 493 > dev/mps/mps_table.h | 53 > dev/mps/mps_user.c | 944 +++ > dev/mps/mpsvar.h | 390 ++ > dev/siba/siba_bwn.c |2 > dev/sis/if_sisreg.h |2 > mips/mips/mp_machdep.c |2 > modules/Makefile |1 > modules/mps/Makefile | 14 > > There may be some patches that are not really related to mps (siba? > if_sisreg?). Yeah, they weren't really related. Someone went through and eliminated a few instances of double semicolons, and one of them was in the mps driver. I just merged the whole change since it was rather harmless. Ken -- Kenneth Merry k...@freebsd.org ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On Thu, Feb 17, 2011 at 11:07:21 -0800, Rumen Telbizov wrote: > Hello Damien, list: > > I've been following this discussion with great interest and I hope the > result of it > will be the merge of a stable driver in STABLE branch soon. > > I brought this not a long ago ( > http://lists.freebsd.org/pipermail/freebsd-stable/2011-January/061237.html) > and I was hoping to have this driver in 8.x before 8.3 release. It is in -stable now, and so should be in 8.3. We didn't make it in time for 8.2 unfortunately. > > What is sad is that these controllers are becoming very mainstream now, > > we're getting them more and more on Dell servers , and the fbsd project > > still struggles with them (for reasons I don't know, might be LSI's > > fault, might be a lack of resources or interest...) > > > > I couldn't agree more. I've been testing those (9211-8i) myself here on a > bunch of SuperMicro > servers and I'd say that I am very pleased with the performance of those > HBAs (not the mention the > price ~$230-250 CAD). On a 12 x SAS disks with a direct attached backplane > 826A (6Gbit SAS2.0) > in RAID0 across all of them (md linux software raid) I was able to squeeze * > 2.1GBytes/s* sequential write > (dd kind of style write). With the same setup and SATA disks I get to > 1.2GByte/s. I did use 2 controllers > to accomodate ports for all the disks. I get the same speed with ZFS and > 9.0-CURRENT. > > On a related note I must say that I do have serious problems with the > bandwidth when I use > the SAS expander version of this backplane (826E26) (I cannot get more than > 200-250 MBytes/s). > I've been investigating this problem with LSI's help and still no > conclusion. It looks like I am using > only one channel. > > Anyway this was just my humble attempt to encourage the MFC of this driver. > I think the card is > pretty good. I'd like to hear other people's opinion on this HBA though. MFC is done, try it out and let me know if there are any problems. Thanks, Ken -- Kenneth Merry k...@freebsd.org ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On 2/18/11 5:49 PM, Kenneth D. Merry wrote: > On Thu, Feb 17, 2011 at 11:07:21 -0800, Rumen Telbizov wrote: >> Hello Damien, list: >> >> Anyway this was just my humble attempt to encourage the MFC of this driver. >> I think the card is >> pretty good. I'd like to hear other people's opinion on this HBA though. > > MFC is done, try it out and let me know if there are any problems. > > Thanks, > > Ken CVSup'ing as we speak ;) When you say -stable, I assume that's 8.2-RC3 yes ? I'm not very familiar with the whole CVSup / MFC / release process... ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On Fri, Feb 18, 2011 at 17:53:11 +0100, Damien Fleuriot wrote: > > > On 2/18/11 5:49 PM, Kenneth D. Merry wrote: > > On Thu, Feb 17, 2011 at 11:07:21 -0800, Rumen Telbizov wrote: > >> Hello Damien, list: > >> > >> Anyway this was just my humble attempt to encourage the MFC of this driver. > >> I think the card is > >> pretty good. I'd like to hear other people's opinion on this HBA though. > > > > MFC is done, try it out and let me know if there are any problems. > > > > Thanks, > > > > Ken > > CVSup'ing as we speak ;) > > When you say -stable, I assume that's 8.2-RC3 yes ? No, that is in a separate branch that is frozen. This won't be in 8.2, we would have had to have gotten it in in December to make 8.2. This is in stable/8. > I'm not very familiar with the whole CVSup / MFC / release process... Ken -- Kenneth Merry k...@freebsd.org ___ 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"
mps(4) driver (LSI 6Gb SAS) commited to stable/8
I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb SAS hardware. It is only included in GENERIC on amd64, since that is the only architecture that I know of that it has been tested on. It may work on i386, if anyone would like to try it out. There are known endian issues, so testing on a big-endian platform (like powerpc) won't work. If you'd like to help fix the endian issues, let me know. Integrated RAID support is not included in this version of the driver, but LSI has almost completed their version of the driver that does include IR support. That will hopefully be going into -current in the next few weeks. There are lots of changes in their version of the driver, particularly in the probe code. There are also a couple of othere issues with the driver that I am planning to fix in -current today and merge back into stable/8 in a few days. In particular I have fixes for these issues: - I/O locks up when you run out of S/G chain frames. - The device queue is not frozen on errors. - For some firmware revisions, the firmware will not return all outstanding commands for a device when the device goes away. Cleanup logic is needed. Let me know if you run into any issues. Ken -- Kenneth Merry k...@freebsd.org ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
> Date: Fri, 18 Feb 2011 09:57:11 -0700 > From: "Kenneth D. Merry" > Sender: owner-freebsd-sta...@freebsd.org > > On Fri, Feb 18, 2011 at 17:53:11 +0100, Damien Fleuriot wrote: > > > > > > On 2/18/11 5:49 PM, Kenneth D. Merry wrote: > > > On Thu, Feb 17, 2011 at 11:07:21 -0800, Rumen Telbizov wrote: > > >> Hello Damien, list: > > >> > > >> Anyway this was just my humble attempt to encourage the MFC of this > > >> driver. > > >> I think the card is > > >> pretty good. I'd like to hear other people's opinion on this HBA though. > > > > > > MFC is done, try it out and let me know if there are any problems. > > > > > > Thanks, > > > > > > Ken > > > > CVSup'ing as we speak ;) > > > > When you say -stable, I assume that's 8.2-RC3 yes ? > > No, that is in a separate branch that is frozen. This won't be in 8.2, we > would have had to have gotten it in in December to make 8.2. > > This is in stable/8. > > > I'm not very familiar with the whole CVSup / MFC / release process... To be very clear, stable/8 is tagged "RELENG_8" in cvs, so you need to specify a tag of "RELENG_8" in your supfile. *default release=cvs tag=RELENG_8 -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
2011/2/18 Kenneth D. Merry : > > MFC is done, try it out and let me know if there are any problems. > Oh ! thank you, i have a supermicro X8DT-6F at work, i'll test that asap. ___ 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: LSI SAS 2008 (mfi) on SuperMicro X8SI6-F
On 2/18/11 6:28 PM, Kevin Oberman wrote: >> Date: Fri, 18 Feb 2011 09:57:11 -0700 >> From: "Kenneth D. Merry" >> Sender: owner-freebsd-sta...@freebsd.org >> >> On Fri, Feb 18, 2011 at 17:53:11 +0100, Damien Fleuriot wrote: >>> >>> >>> On 2/18/11 5:49 PM, Kenneth D. Merry wrote: On Thu, Feb 17, 2011 at 11:07:21 -0800, Rumen Telbizov wrote: > Hello Damien, list: > > Anyway this was just my humble attempt to encourage the MFC of this > driver. > I think the card is > pretty good. I'd like to hear other people's opinion on this HBA though. MFC is done, try it out and let me know if there are any problems. Thanks, Ken >>> >>> CVSup'ing as we speak ;) >>> >>> When you say -stable, I assume that's 8.2-RC3 yes ? >> >> No, that is in a separate branch that is frozen. This won't be in 8.2, we >> would have had to have gotten it in in December to make 8.2. >> >> This is in stable/8. >> >>> I'm not very familiar with the whole CVSup / MFC / release process... > > To be very clear, stable/8 is tagged "RELENG_8" in cvs, so you need to > specify a tag of "RELENG_8" in your supfile. > *default release=cvs tag=RELENG_8 Hi Kevin and thanks for your reply, As I just told Kenneth (switched to private exchanges to not spam the list with meaningless stuff), I'm afraid I don't get a sys/dev/mps/ folder when I sync against RELENG_8 nas# grep release /etc/cvsup/stable-supfile *default release=cvs tag=RELENG_8 #src-release nas# ls -lad /usr/src/sys/dev/mp* drwxr-xr-x 3 root wheel 512 Feb 18 19:17 /usr/src/sys/dev/mpt Oh wait, it occurs to me the mirror I sync on might not be up to date yet... SUPHOST=cvsup1.fr.freebsd.org SUPFILE=/etc/cvsup/stable-supfile ___ 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: statd/lockd startup failure
I've seen this intermittently for mountd. I think the problem is that
the code finds an unused port for udp/ip6 and then tries to use the
same port# for tcp/ip6, udp/ip4, tcp/ip4. All three daemons have
essentially the same function for doing this.
The attached patches changes the behaviour so that it tries to
get an unused port for each of the 4 cases.
(This all applies to the "wildcard" case, where no port# or
hosts have been specified as command args.)
If you have the chance to try these patches, please let us know
how they work for you?
rick
ps: I lost track of the thread, so I don't know who started it, but
hopefully, they are on the cc list?
--- usr.sbin/mountd/mountd.c.sav 2011-02-17 21:45:32.0 -0500
+++ usr.sbin/mountd/mountd.c 2011-02-17 23:23:37.0 -0500
@@ -510,6 +510,7 @@ create_service(struct netconfig *nconf)
int r;
int registered = 0;
u_int32_t host_addr[4]; /* IPv4 or IPv6 */
+ int mallocd_svcport = 0;
if ((nconf->nc_semantics != NC_TPI_CLTS) &&
(nconf->nc_semantics != NC_TPI_COTS) &&
@@ -620,7 +621,7 @@ create_service(struct netconfig *nconf)
sin->sin_addr.s_addr = htonl(INADDR_ANY);
res->ai_addr = (struct sockaddr*) sin;
res->ai_addrlen = (socklen_t)
- sizeof(res->ai_addr);
+ sizeof(struct sockaddr_in);
break;
case AF_INET6:
sin6 = malloc(sizeof(struct sockaddr_in6));
@@ -631,10 +632,12 @@ create_service(struct netconfig *nconf)
sin6->sin6_addr = in6addr_any;
res->ai_addr = (struct sockaddr*) sin6;
res->ai_addrlen = (socklen_t)
- sizeof(res->ai_addr);
+ sizeof(struct sockaddr_in6);
break;
default:
- break;
+ syslog(LOG_ERR, "bad addr fam %d",
+ res->ai_family);
+ exit(1);
}
} else {
if ((aicode = getaddrinfo(NULL, svcport_str,
@@ -700,6 +703,7 @@ create_service(struct netconfig *nconf)
svcport_str = malloc(NI_MAXSERV * sizeof(char));
if (svcport_str == NULL)
out_of_mem();
+mallocd_svcport = 1;
if (getnameinfo(res->ai_addr,
res->ai_addr->sa_len, NULL, NI_MAXHOST,
@@ -715,6 +719,12 @@ create_service(struct netconfig *nconf)
exit(1);
}
+ if (mallocd_svcport != 0) {
+free(svcport_str);
+svcport_str = NULL;
+mallocd_svcport = 0;
+ }
+
servaddr.buf = malloc(res->ai_addrlen);
memcpy(servaddr.buf, res->ai_addr, res->ai_addrlen);
servaddr.len = res->ai_addrlen;
--- usr.sbin/rpc.statd/statd.c.sav 2011-02-17 23:36:15.0 -0500
+++ usr.sbin/rpc.statd/statd.c 2011-02-17 23:37:53.0 -0500
@@ -233,6 +233,7 @@ create_service(struct netconfig *nconf)
int r;
int registered = 0;
u_int32_t host_addr[4]; /* IPv4 or IPv6 */
+ int mallocd_svcport = 0;
if ((nconf->nc_semantics != NC_TPI_CLTS) &&
(nconf->nc_semantics != NC_TPI_COTS) &&
@@ -326,7 +327,7 @@ create_service(struct netconfig *nconf)
sin->sin_addr.s_addr = htonl(INADDR_ANY);
res->ai_addr = (struct sockaddr*) sin;
res->ai_addrlen = (socklen_t)
- sizeof(res->ai_addr);
+ sizeof(struct sockaddr_in);
break;
case AF_INET6:
sin6 = malloc(sizeof(struct sockaddr_in6));
@@ -336,10 +337,13 @@ create_service(struct netconfig *nconf)
sin6->sin6_port = htons(0);
sin6->sin6_addr = in6addr_any;
res->ai_addr = (struct sockaddr*) sin6;
- res->ai_addrlen = (socklen_t) sizeof(res->ai_addr);
+ res->ai_addrlen = (socklen_t)
+ sizeof(struct sockaddr_in6);
break;
default:
- break;
+ syslog(LOG_ERR, "bad addr fam %d",
+ res->ai_family);
+ exit(1);
}
} else {
if ((aicode = getaddrinfo(NULL, svcport_str,
@@ -401,6 +405,7 @@ create_service(struct netconfig *nconf)
svcport_str = malloc(NI_MAXSERV * sizeof(char));
if (svcport_str == NULL)
out_of_mem();
+mallocd_svcport = 1;
if (getnameinfo(res->ai_addr,
res->ai_addr->sa_len, NULL, NI_MAXHOST,
@@ -416,6 +421,12 @@ create_service(struct netconfig *nconf)
exit(1);
}
+ if (mallocd_svcport != 0) {
+free(svcport_str);
+svcport_str = NULL;
+mallocd_svcport = 0;
+ }
+
servaddr.buf = malloc(res->ai_addrlen);
memcpy(servaddr.buf, res->ai_addr, res->ai_addrlen);
servaddr.len = res->ai_addrlen;
--- usr.sbin/rpc.lockd/lockd.c.sav 2011-02-17 23:29:48.0 -0500
+++ usr.sbin/rpc.lockd/lockd.c 2011-02-17 23:35:47.0 -0500
@@ -403,6 +403,7 @@ create_service(struct netconfig *nconf)
int r;
int registered = 0;
u_int32_t host_addr[4]; /* IPv4 or IPv6 */
+ int mallocd_svcport = 0;
if ((nconf->nc_semantics != NC_TPI_CLTS) &&
(nconf->nc_semantics != NC_TPI_COTS) &&
@@ -497,7 +498,7 @@ create_service(struct netconfig *nconf)
sin->sin_addr.s_addr = htonl(INADDR_ANY);
res->ai_addr = (struct sockaddr*) sin;
res->ai_addrlen = (socklen_t)
- sizeof(res->ai_addr);
+ sizeof(struct sockaddr_in);
break;
case AF_I
On The Grind *New Music Update*
B. Ezy is back again with a BeatsBeast produced track "On The Grind" ft. Ganksta Clyde.Ganksta Clyde recently signed a deal with Def Jam last summer.Stay Tuned for more great music from B. Ezy and BeatsBeast Update Contact Info: http://www.reverbnation.com/c/fr7/artist_158288?eid=A158288_7576270_30674416&fsc=791e9d14a39 Unsubscribe: http://www.reverbnation.com/c/fr2/artist_158288?eid=A158288_7576270_30674416&fsc=791e9d14a39 Report Abuse: http://www.reverbnation.com/c/fr6/artist_158288?eid=A158288_7576270_30674416&fsc=791e9d14a39 Privacy Policy: http://www.reverbnation.com/fan_reach/privacy/artist_158288 Physical inquiries can be sent to: po box 777, eastpointe, MI, 48021, US If our email is in your Spam/Junk Folder, please add beatsbe...@emailhosting.com to your address book. Powered by FanReach Pro ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, 18 Feb 2011, Kenneth D. Merry wrote: KDM> I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb KDM> SAS hardware. [snip] Again, thank you very much Ken. I'm planning to stress test this on 846 case filled with 12 (yet) WD RE4 disks organized as raidz2, and will post the results. Any hints to particularly I/O stressing patterns? Out of my mind, I'm planning multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what else could you suppose? -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Sat, Feb 19, 2011 at 01:08:41AM +0300, Dmitry Morozovsky wrote: > On Fri, 18 Feb 2011, Kenneth D. Merry wrote: > > KDM> I just merged the mps(4) driver to stable/8, for those of you with LSI > 6Gb > KDM> SAS hardware. > > [snip] > > Again, thank you very much Ken. I'm planning to stress test this on 846 case > filled with 12 (yet) WD RE4 disks organized as raidz2, and will post the > results. > > Any hints to particularly I/O stressing patterns? Out of my mind, I'm > planning > multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what else > could you suppose? Please be aware of a performance issue affecting certain models of WD RE4 disks. Specifics are still sketchy, but you should read the thread "immense delayed write to file system (ZFS and UFS2), performance issues" in full to get an idea of the problem: http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/thread.html#54185 There's confirmation of the problem here, with the statement that WD gave at least one person a firmware image that fixed the problem: http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/054489.html Buyer beware. :-) And remember, it's not an issue with the brand/vendor, just certain models. Caviar Black drives don't appear affected (and don't let the TLER stuff make you lose focus), which is one reason why I advocate them. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Sat, Feb 19, 2011 at 01:08:41 +0300, Dmitry Morozovsky wrote: > On Fri, 18 Feb 2011, Kenneth D. Merry wrote: > > KDM> I just merged the mps(4) driver to stable/8, for those of you with LSI > 6Gb > KDM> SAS hardware. > > [snip] > > Again, thank you very much Ken. I'm planning to stress test this on 846 case > filled with 12 (yet) WD RE4 disks organized as raidz2, and will post the > results. > > Any hints to particularly I/O stressing patterns? Out of my mind, I'm > planning > multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what else > could you suppose? The best stress test I have found has been to just do a single sequential write stream with ZFS. i.e.: cd /path/to/zfs/pool dd if=/dev/zero of=foo bs=1M Just let it run for a long period of time and see what happens. What model controller do you have, and what firmware do you have on it? I have run into some bugs with the LSI 2.0 firmware, notably that you'll get IOC Busy errors as well as some bogus invalid LBA errors with SATA disks. (I'm guessing it wouldn't happen with SAS disks.) The 8.0 firmware is better, but the version for the 9211-8i is not able to recognize large numbers (more than 20) drives. (I reported that to LSI and they supplied a fix.) Ken -- Kenneth Merry k...@freebsd.org ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, Feb 18, 2011 at 02:38:32PM -0800, Jeremy Chadwick wrote: > > > Please be aware of a performance issue affecting certain models of WD > RE4 disks. Specifics are still sketchy, but you should read the thread > "immense delayed write to file system (ZFS and UFS2), performance > issues" in full to get an idea of the problem: > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/thread.html#54185 > > There's confirmation of the problem here, with the statement that WD > gave at least one person a firmware image that fixed the problem: > > http://lists.freebsd.org/pipermail/freebsd-stable/2010-January/054489.html I'm not sure if this is exactly the same issue, but I also had to flash some WD drives a few month ago. There was a bad firmware version on some 2TB RE4-GP models; disks kept getting removed from RAID volumes due to write timeouts. > Buyer beware. :-) And remember, it's not an issue with the > brand/vendor, just certain models. Disks these days are no longer just disks, but complete computers with ram, many processors, and the associated software issues... -- Francois Tigeot ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, 18 Feb 2011, Jeremy Chadwick wrote: JC> > KDM> I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb JC> > KDM> SAS hardware. JC> > JC> > [snip] JC> > JC> > Again, thank you very much Ken. I'm planning to stress test this on 846 case JC> > filled with 12 (yet) WD RE4 disks organized as raidz2, and will post the JC> > results. JC> > JC> > Any hints to particularly I/O stressing patterns? Out of my mind, I'm planning JC> > multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what else JC> > could you suppose? JC> JC> Please be aware of a performance issue affecting certain models of WD JC> RE4 disks. Specifics are still sketchy, but you should read the thread JC> "immense delayed write to file system (ZFS and UFS2), performance JC> issues" in full to get an idea of the problem: Well, my disks are (possibly happily ;) not RE4-GP but real RE4 (yellow labels, Raid Edition Ready) But thanks, I'll take additional time to log smartctl data during the tests... -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, 18 Feb 2011, Kenneth D. Merry wrote: KDM> > KDM> I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb KDM> > KDM> SAS hardware. KDM> > KDM> > [snip] KDM> > KDM> > Again, thank you very much Ken. I'm planning to stress test this on 846 case KDM> > filled with 12 (yet) WD RE4 disks organized as raidz2, and will post the KDM> > results. KDM> > KDM> > Any hints to particularly I/O stressing patterns? Out of my mind, I'm planning KDM> > multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what else KDM> > could you suppose? KDM> KDM> The best stress test I have found has been to just do a single sequential KDM> write stream with ZFS. i.e.: KDM> KDM> cd /path/to/zfs/pool KDM> dd if=/dev/zero of=foo bs=1M KDM> KDM> Just let it run for a long period of time and see what happens. Well, provided that I'm plannign to use ZFSv28 to be in place, wouldn't be /dev/random more appropriate? -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Sat, Feb 19, 2011 at 02:05:33AM +0300, Dmitry Morozovsky wrote: > On Fri, 18 Feb 2011, Kenneth D. Merry wrote: > > KDM> > KDM> I just merged the mps(4) driver to stable/8, for those of you > with LSI 6Gb > KDM> > KDM> SAS hardware. > KDM> > > KDM> > [snip] > KDM> > > KDM> > Again, thank you very much Ken. I'm planning to stress test this on > 846 case > KDM> > filled with 12 (yet) WD RE4 disks organized as raidz2, and will post > the > KDM> > results. > KDM> > > KDM> > Any hints to particularly I/O stressing patterns? Out of my mind, I'm > planning > KDM> > multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what > else > KDM> > could you suppose? > KDM> > KDM> The best stress test I have found has been to just do a single sequential > KDM> write stream with ZFS. i.e.: > KDM> > KDM> cd /path/to/zfs/pool > KDM> dd if=/dev/zero of=foo bs=1M > KDM> > KDM> Just let it run for a long period of time and see what happens. > > Well, provided that I'm plannign to use ZFSv28 to be in place, wouldn't be > /dev/random more appropriate? No -- /dev/urandom maybe, but not /dev/random. /dev/urandom will also induce significantly higher CPU load than /dev/zero will. Don't forget that ZFS is a processor-centric (read: no offloading) system. I tend to try different block sizes (starting at bs=8k and working up to bs=256k) for sequential benchmarks. The "sweet spot" on most disks I've found is 64k. Otherwise use benchmarks/bonnie++. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, Feb 18, 2011 at 5:13 PM, Jeremy Chadwick wrote: > No -- /dev/urandom maybe, but not /dev/random. /dev/urandom will also > induce significantly higher CPU load than /dev/zero will. Don't forget > that ZFS is a processor-centric (read: no offloading) system. > /dev/urandom is linked to /dev/random. Is there some other difference I'm not aware of, or are you confusing it with Linux's random? -- Adam Vande More ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
> Date: Fri, 18 Feb 2011 15:13:06 -0800 > From: Jeremy Chadwick > Sender: owner-freebsd-sta...@freebsd.org > > On Sat, Feb 19, 2011 at 02:05:33AM +0300, Dmitry Morozovsky wrote: > > On Fri, 18 Feb 2011, Kenneth D. Merry wrote: > > > > KDM> > KDM> I just merged the mps(4) driver to stable/8, for those of you > > with LSI 6Gb > > KDM> > KDM> SAS hardware. > > KDM> > > > KDM> > [snip] > > KDM> > > > KDM> > Again, thank you very much Ken. I'm planning to stress test this on > > 846 case > > KDM> > filled with 12 (yet) WD RE4 disks organized as raidz2, and will post > > the > > KDM> > results. > > KDM> > > > KDM> > Any hints to particularly I/O stressing patterns? Out of my mind, > > I'm planning > > KDM> > multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- > > what else > > KDM> > could you suppose? > > KDM> > > KDM> The best stress test I have found has been to just do a single > > sequential > > KDM> write stream with ZFS. i.e.: > > KDM> > > KDM> cd /path/to/zfs/pool > > KDM> dd if=/dev/zero of=foo bs=1M > > KDM> > > KDM> Just let it run for a long period of time and see what happens. > > > > Well, provided that I'm plannign to use ZFSv28 to be in place, wouldn't be > > /dev/random more appropriate? > > No -- /dev/urandom maybe, but not /dev/random. /dev/urandom will also > induce significantly higher CPU load than /dev/zero will. Don't forget > that ZFS is a processor-centric (read: no offloading) system. > > I tend to try different block sizes (starting at bs=8k and working up to > bs=256k) for sequential benchmarks. The "sweet spot" on most disks I've > found is 64k. Otherwise use benchmarks/bonnie++. When FreeBSD updated its random number engine a couple of years ago, random and urandom became the same thing. Unless I am missing something, a switch should make no difference. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: ober...@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 ___ 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: statd/lockd startup failure
On 02/18/2011 10:08, Rick Macklem wrote: The attached patches changes the behaviour so that it tries to get an unused port for each of the 4 cases. Am I correct in assuming that what you're proposing is to (potentially) have different ports for all 4 combinations? I would suggest that this is not the right way to solve the problem. If I misunderstand, I apologize. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, Feb 18, 2011 at 04:05:21PM -0800, Kevin Oberman wrote: > > Date: Fri, 18 Feb 2011 15:13:06 -0800 > > From: Jeremy Chadwick > > Sender: owner-freebsd-sta...@freebsd.org > > > > On Sat, Feb 19, 2011 at 02:05:33AM +0300, Dmitry Morozovsky wrote: > > > On Fri, 18 Feb 2011, Kenneth D. Merry wrote: > > > > > > KDM> > KDM> I just merged the mps(4) driver to stable/8, for those of you > > > with LSI 6Gb > > > KDM> > KDM> SAS hardware. > > > KDM> > > > > KDM> > [snip] > > > KDM> > > > > KDM> > Again, thank you very much Ken. I'm planning to stress test this > > > on 846 case > > > KDM> > filled with 12 (yet) WD RE4 disks organized as raidz2, and will > > > post the > > > KDM> > results. > > > KDM> > > > > KDM> > Any hints to particularly I/O stressing patterns? Out of my mind, > > > I'm planning > > > KDM> > multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- > > > what else > > > KDM> > could you suppose? > > > KDM> > > > KDM> The best stress test I have found has been to just do a single > > > sequential > > > KDM> write stream with ZFS. i.e.: > > > KDM> > > > KDM> cd /path/to/zfs/pool > > > KDM> dd if=/dev/zero of=foo bs=1M > > > KDM> > > > KDM> Just let it run for a long period of time and see what happens. > > > > > > Well, provided that I'm plannign to use ZFSv28 to be in place, wouldn't > > > be > > > /dev/random more appropriate? > > > > No -- /dev/urandom maybe, but not /dev/random. /dev/urandom will also > > induce significantly higher CPU load than /dev/zero will. Don't forget > > that ZFS is a processor-centric (read: no offloading) system. > > > > I tend to try different block sizes (starting at bs=8k and working up to > > bs=256k) for sequential benchmarks. The "sweet spot" on most disks I've > > found is 64k. Otherwise use benchmarks/bonnie++. > > When FreeBSD updated its random number engine a couple of years ago, > random and urandom became the same thing. Unless I am missing something, > a switch should make no difference. You and Adam's comments are both valid. I tend to work on a multitude of OSes (specifically Solaris, Linux, and FreeBSD), so I tend to use what behaves the same universally (/dev/urandom in this case). Sorry for the mix-up/noise. -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Feb 18, 2011, at 3:27 PM, Adam Vande More wrote: > /dev/urandom is linked to /dev/random. Is there some other difference I'm > not aware of, or are you confusing it with Linux's random? There is no difference between the two on FreeBSD, although anyone using the platform is hoping that Yarrow is "good enough". Wikipedia has a fine article on the subject: http://en.wikipedia.org/wiki//dev/random Regards, -- -Chuck ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, Feb 18, 2011 at 11:42 AM, Kenneth D. Merry wrote: > > I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb > SAS hardware. Thank you Ken for getting this done. Any plan to support the LSI 9240 (skinny) cards? if its a matter of hardware to develop with, contact me off list and I can provide you with a development system. thx -- Bill ___ 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"
8.2-RC3-amd64 install hangs on Dell T110
If I've come to the wrong list with this, please redirect me. I have a brand new Dell T110, 2.53ghz Xeon 3440, 8gb [2x4gb] ram, 4x1tb Hitachi SAS hd, Apple USB keyboard and mouse [just to cover all the hardware] Booting 8.2-RC3 amd64 disc1 looks good through all the bright-white text, but it's hard to read scrolling by that fast :) then shows one line of normal-bright text: /stand/sysinstall running as init on vty0 then hangs, never gets to the blue install screens. This is new hardware to me, but it loads Ubuntu 10.04 amd64 and OpenBSD 4.8 amd64 fine, so I'm assuming it's not flaky hardware. I'd be happy to try any patches or debugging tips, but this is my only amd64 box and since I can't yet get FreeBSD onto it, it would have to be something I don't have to build. Thanks. -- Ron McDowell San Antonio TX ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Sat, 19 Feb 2011, Dmitry Morozovsky wrote: On Fri, 18 Feb 2011, Kenneth D. Merry wrote: KDM> I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb KDM> SAS hardware. [snip] Again, thank you very much Ken. I'm planning to stress test this on 846 case filled with 12 (yet) WD RE4 disks organized as raidz2, and will post the results. Any hints to particularly I/O stressing patterns? Out of my mind, I'm planning multiple parallel -j'ed builds, parallel tars, *SQL benchmarks -- what else could you suppose? benchmarks/iozone is nice, and you can get nifty graphs out of it. It walks through various block sizes and is very long running. It can probably tickle lots of stuff. The results are also pretty informative - you can see very clearly in the graphs whatever your weak spots are. http://www.iozone.org/ Charles -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ 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" ___ 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: mps(4) driver (LSI 6Gb SAS) commited to stable/8
On Fri, Feb 18, 2011 at 19:46:54 -0500, Bill Desjardins wrote: > On Fri, Feb 18, 2011 at 11:42 AM, Kenneth D. Merry wrote: > > > > I just merged the mps(4) driver to stable/8, for those of you with LSI 6Gb > > SAS hardware. > > Thank you Ken for getting this done. Any plan to support the LSI 9240 > (skinny) cards? if its a matter of hardware to develop with, contact > me off list and I can provide you with a development system. That'll be up to LSI most likely. If it has the mpt2 interface, then I'm sure they'll support it through the mps driver. If it has the MegaRAID interface, then the mfi driver would need to be modified. Ken -- Kenneth Merry k...@freebsd.org ___ 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"
