toasters

toasters@lists.teaparty.net

13520 discussions

Re: Gotcha on multiple network interfaces
by svawter＠c-cube.com 04 Jan '01

04 Jan '01

What you should use for a failover link is create a vif in single mode with e7 & e0, favoring e7. vif create single f0 e7 e0 vif favor e7 ifconfig f0 hostname flowcontrol full netmask 255.255.255.0 or perhaps: vif create single f0 e7 ifconfig f0 hostname flowcontrol full netmask 255.255.255.0 vif favor e7 vif add f0 e0 Steve Vawter voice: 408-490-5310 fax: 408-490-8615 Staff UNIX Systems Administrator Steve.Vawter(a)C-Cube.COM --> --> From brian(a)paradyne.com Thu Jan 4 09:56:51 2001 --> From: "Brian L. Brush" <brian(a)paradyne.com> --> X-Mailer: Mozilla 4.7 [en] (X11; U; SunOS 5.8 sun4u) --> To: toasters(a)mathworks.com --> Subject: Gotcha on multiple network interfaces --> --> --> If you have multiple network interfaces on your filers, this information --> may be useful to you. If you're thorough about reading the documentation --> and clever about checking your results, you may have discovered it for --> yourself. --> --> While testing our new F760 cluster, we have discovered that if the filer --> has two interfaces on the same subnet and the default gateway resides on --> that subnet, the default route in the filer's routing table will choose --> the interface with the lower number. --> --> In particular, using the "setup" command, we configured an F760 with --> on-board 100Mbps e0 and GigE e7 on the same subnet. Using "netstat -r", --> we determined that the default route was using e0, which was not what we --> wanted--the 100Mbps was intended to be a backup link, not for regular --> production use: --> --> pow> netstat -r --> Routing tables --> --> Internet: --> Destination Gateway Flags Refs Use Interface --> default 135.90.100.254 UG 1 61 e0 --> 127 localhost UG 1 9 lo --> localhost localhost UH 1 0 lo --> 135.90.100/24 link#1 UC 0 0 e0 --> 135.90.100.254 0:50:50:3f:18:1f UHL 1 0 e0 --> 135.90.100.255 link#1 UHL 1 46 e0 --> --> After some experimentation, we settled on editing /etc/rc to configure --> e0 after both configuring e7 and adding the default route; we also --> turned off routed: --> --> #Auto-generated by setup Wed Dec 20 19:16:53 GMT 2000 --> hostname pow --> ifconfig e7 `hostname`-e7 flowcontrol full netmask 255.255.255.0 --> route add default 135.90.100.254 1 --> ifconfig e0 `hostname`-e0 mediatype auto netmask 255.255.255.0 --> #routed on --> options dns.domainname is.paradyne.com --> options dns.enable on --> options nis.domainname is.paradyne.com --> options nis.enable on --> savecore --> exportfs -a --> nfs on --> --> Now we have the results we wanted; all outbound packets should use the --> gig link, according to netstat: --> --> pow> netstat -r --> Routing tables --> --> Internet: --> Destination Gateway Flags Refs Use Interface --> default 135.90.100.254 UG 5 2148 e7 --> 127 localhost UG 1 261 lo --> localhost localhost UH 1 0 lo --> 135.90.100/24 link#2 UC 0 0 e7 --> 135.90.100.254 0:50:50:3f:18:1f UHL 1 0 e7 --> 135.90.100.255 link#2 UHL 1 1794 e7 --> --> Looking at the systems we had in production, we realized that, as a --> result of this oversight, they had been sending all outbound traffic via --> their fast ethernet interfaces rather than gig! Aaargh! --> --> --Brian L. Brush --> Senior Systems Administrator --> Paradyne Corporation -->

1 0

RE: Gotcha on multiple network interfaces
by Premanshu Jain 04 Jan '01

04 Jan '01

Yes..I also observed the same problem and finally disabled the e0 interface. prem -----Original Message----- From: Brian L. Brush [mailto:brian@paradyne.com] Sent: Thursday, January 04, 2001 7:20 AM To: toasters(a)mathworks.com Subject: Gotcha on multiple network interfaces If you have multiple network interfaces on your filers, this information may be useful to you. If you're thorough about reading the documentation and clever about checking your results, you may have discovered it for yourself. While testing our new F760 cluster, we have discovered that if the filer has two interfaces on the same subnet and the default gateway resides on that subnet, the default route in the filer's routing table will choose the interface with the lower number. In particular, using the "setup" command, we configured an F760 with on-board 100Mbps e0 and GigE e7 on the same subnet. Using "netstat -r", we determined that the default route was using e0, which was not what we wanted--the 100Mbps was intended to be a backup link, not for regular production use: pow> netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Interface default 135.90.100.254 UG 1 61 e0 127 localhost UG 1 9 lo localhost localhost UH 1 0 lo 135.90.100/24 link#1 UC 0 0 e0 135.90.100.254 0:50:50:3f:18:1f UHL 1 0 e0 135.90.100.255 link#1 UHL 1 46 e0 After some experimentation, we settled on editing /etc/rc to configure e0 after both configuring e7 and adding the default route; we also turned off routed: #Auto-generated by setup Wed Dec 20 19:16:53 GMT 2000 hostname pow ifconfig e7 `hostname`-e7 flowcontrol full netmask 255.255.255.0 route add default 135.90.100.254 1 ifconfig e0 `hostname`-e0 mediatype auto netmask 255.255.255.0 #routed on options dns.domainname is.paradyne.com options dns.enable on options nis.domainname is.paradyne.com options nis.enable on savecore exportfs -a nfs on Now we have the results we wanted; all outbound packets should use the gig link, according to netstat: pow> netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Interface default 135.90.100.254 UG 5 2148 e7 127 localhost UG 1 261 lo localhost localhost UH 1 0 lo 135.90.100/24 link#2 UC 0 0 e7 135.90.100.254 0:50:50:3f:18:1f UHL 1 0 e7 135.90.100.255 link#2 UHL 1 1794 e7 Looking at the systems we had in production, we realized that, as a result of this oversight, they had been sending all outbound traffic via their fast ethernet interfaces rather than gig! Aaargh! --Brian L. Brush Senior Systems Administrator Paradyne Corporation

1 0

RE: Sun photon (fcal) disks on toaster?
by Traitel, Eyal 04 Jan '01

04 Jan '01

Games like this could be fun indeed, but I doubt if our code supports them... Anyway - you can always try to boot a regular PC with our Intel platform floppies... :) Eyal. ---------------------------------------------------------------------- eTraitel - I'm the new eBuzzword around !!! ---------------------------------------------------------------------- Eyal Traitel - Filer Escalation Engineer CNA, MCSE, CSA, NACA Network Appliance BV Holland Office Center Kruisweg 799b 2132 NG, Hoofddorp The Netherlands Office: +31 23 567 9685 Cellular: +31 6 5497 2568 Email: eyal(a)netapp.com ---------------------------------------------------------------------- Get answers NOW! - NetApp On the Web - http://now.netapp.com ---------------------------------------------------------------------- -----Original Message----- From: Jason S. Cash [mailto:cash@udel.edu] Sent: Thursday, January 04, 2001 2:48 PM To: toasters(a)mathworks.com Subject: Sun photon (fcal) disks on toaster? Has anyone successfully hooked Sun photon disk arrays to a netapp? I have a bunch of these sitting around at the moment a f740 that it might be amusing to see how fast they can go (if at all). Management might be willing to buy us some 840s to act as heads for these arrays if it will work :) TIA, Jason /* Jason S. Cash - Systems Programmer IT/Network and Systems Services University of Delaware, Newark Delaware */

1 0

Sun photon (fcal) disks on toaster?
by Jason S. Cash 04 Jan '01

04 Jan '01

Has anyone successfully hooked Sun photon disk arrays to a netapp? I have a bunch of these sitting around at the moment a f740 that it might be amusing to see how fast they can go (if at all). Management might be willing to buy us some 840s to act as heads for these arrays if it will work :) TIA, Jason /* Jason S. Cash - Systems Programmer IT/Network and Systems Services University of Delaware, Newark Delaware */

1 0

Filer + Netscape Messaging Server
by Brian L. Brush 03 Jan '01

03 Jan '01

We are considering using a filer to provide the message stores for our Netscape (soon to be iPlanet) Messaging Server. Of course, neither Netscape (iPlanet) nor NetApp supports such a configuration. Can anyone offer relevant insight or experience? For a couple of years we have been using a similarly unsupported configuration to provide storage space for Rational ClearCase. While we've had no insuperable problems, I don't relish the prospect of hitting a brick wall on those rare occasions when we request support--for the application, not the configuration. --Brian L. Brush Senior Systems Administrator Paradyne Corporation

1 0

Re: Bad Solaris performance over time
by hill＠communitytelephone.com 03 Jan '01

03 Jan '01

On Tue, 2 Jan 2001, Chris Lamb wrote: ->One box handled incoming SMTP and all local delivery (sendmail+procmail) ->and POP, the other handled some unholy number of Majordomo lists. I mean, ->this was with hardware that nowadays people scoff at, running ancient ->software releases and NFS V2 over a single network interface. I find it ->impossible to believe that a 4-way UltraII and an F760 can't handle the ->load. (Yeah, the average mail message with all the crap "modern" mailers ->add on is probably several Kb larger, but that's almost never the real ->bottleneck.) That was supposed to be part of my point, the machine we have can more the adequetly handle the load. :) The stats http://static-content-01.communitytelephone.net/~hill/server_stats show that the machine doesn't breathe hard all day long. It seems that something happens over time and at some point hits critical mass, which causes the performance to become very bad. -> ->Some questions that may be a bit obvious: Is your 2.6 box patched to ->current levels? Yes. Patch revisions are posted at the above URL. ->Why NFS V2? This was a typo, it is really V3. ->How much NVRAM in the filer? 32Mb. The filer weekly_log is at the above URL. ->Is the network bogged down, or the switch misconfigured? We see no errors on the switch, or the servers network interfaces. ->How many network interfaces, of what type/speed? Filer has a Gigabit interface. Solaris servers has 100Mb. You can see the throughput information at the above URL file: nx.se. ->What does snoop/tcpdump/your network sniffer say? I haven't tried this yet. It looked like there was going to be way too much information to sort through. I will gather it the next time the system begins to act up. ->How many disks in the volume that contains /var/mail? 14 ->Is this filer running CIFS & NFS, or is it purely an NFS box? NFS only ->If /var/mail is on the filer, what about home directories (i.e., is ->your mailer bogging doing ".forward" lookups)? home directories are on the netapp as well. Again I must state it is not a general performance problem, but something that happens over time. -> Are you using NIS and/or DNS on the filer? No. ->What version of sendmail/qmail/whatever? Latest smail. ->Are you using procmail for delivery? Why not? :-) Yes. ->Is disk scrubbing kicking in? Are you taking snapshots too frequently? ->Do you have cron jobs walking the filesystem or other network clients ->hitting the filer or the network when these slowdowns are observed on ->the ->mail server? And really, why NFS V2? I appreciate what you are getting at here, but I don't believe that sort of thing is happening. It you look at the stats for the filer the performance of it stays stable through the trouble period with the one server. Also, all other servers continue to perform well. I believe the server stats show that things like these aren't occuring as well. We are using V3 mounts I typo'd my earlier email. ->(I'm not really a smartass, I just play one on the Internet. :-) These ->are just some of the questions I'd look to answer before poking at ->/etc/system. We did do that. We feel stronghly that there is a bug in Solaris or in the interaction between it and the netapp which cause our performance problems to occur. We tried to massage /etc/system parameters to keep from occuring. Again, I must point out our server ran great when we have /var/mail on local storage. We only began to see this problem after moving it to the filer and only after 24 - 30 hours of operation. I have found a bug ID on sunsolve that described similarities to our problem, but we already have the patch that was supposed to fix that bug. I include it here so you can get a feel for the actual problem from someone elses perspective. Even though our problem is not an exact match we do have similarities with it. We also have similarities to a posting on toasters Date: Tue, 10 Aug 1999 08:05:18 -0700 (PDT) From: Nick Christenson <npc(a)sendmail.com> To: toasters(a)mathworks.com Subject: NFS client tuning, problem and resolution. ------------------------ Sun Bug ID 4034003 --------------------------- Some time ago I got email from someone on a system w/ 37,000 users who had problem using mail from it's mailserver, both CPU were very busy and the system had slowed to a crawl at peak times. The systems gets +/- 70K sendmail calls, 130K pop3 calls a day, mail lives ona NFSv3 capable network appliance server. Mail is delivered to the home directories, not to /var/mail. He ran kernel profiling and found crcmp() topping the list: granularity: each sample hit covers 2 byte(s) for 0.12% of 8.65 seconds % cumulative self self total time seconds seconds calls ms/call ms/call name 39.2 3.39 3.39 crcmp [1] 2.8 3.63 0.24 locked_pgcopy [2] 2.5 3.85 0.22 splx [3] 1.8 4.01 0.16 bcopy [4] 1.7 4.16 0.15 mutex_enter [5] 1.7 4.31 0.15 disp_getwork [6] 1.6 4.45 0.14 dnlc_purge_vp [7] 1.5 4.58 0.13 nfs3_access [8] 1.5 4.71 0.13 ross625_vac_segflush [9] 1.3 4.82 0.11 blkclr [10] 1.3 4.93 0.11 idle [11] 1.0 5.02 0.09 mutex_adaptive_enter [12] While the information is not complete, here's what I think happens, all users access the same rnode ("/export/home", mail is delivered to the home directies) a large access cache is built and here's where we serialize:, in nfs3_access() : [common/fs/nfs/nfs3_vnops.c] ........ mutex_enter(&rp->r_statelock); for (acp = rp->r_acc; acp != NULL; acp = acp->next) { /* * Look for an entry by comparing credentials. */ if (crcmp(acp->cred, cr) == 0) { if ((acp->known & acc) == acc) { #ifdef DEBUG nfs3_access_cache_hits++; #endif if ((acp->allowed & acc) == acc) { mutex_exit(&rp->r_statelock); return (0); } mutex_exit(&rp->r_statelock); return (EACCES); } break; } } mutex_exit(&rp->r_statelock); And further down, if we have a cache miss, we do the same all over again. (As we unlock, we need to recheck whether a new entry was added, so the list is rechecked, again holding the r_statelock) Now, that algorithm works fine in the typical case where users access their own files; or whena few users do. It does *not* work when you have 37K users accessing a single file. As long as the node is cached and the kernel doesn't reap kernel memory, the list will grow out of bounds and access to this node will get increasingly slow. This theory was tested by switching to NFSv2 mounts. This fixed the problem. Attached is a program that shows the behaviour somewhat. It calls "access()" on a file (specified on the command line) as many different users. The file must exist on a NFSv3 filesystem, the program must be run as root and the file must be openable as root on the client. One sample run printed this: 0 18860 500 5680 1000 4798 1500 3963 2000 3071 2500 2425 3000 1552 3500 863 and this tells that after running access(file, F_OK) as 4000 different uids, there's a really high penalty for the first users that called access. In this case for uid(0) searching the cache costs 18ms. It seems that this cache should not be allowed to grow out of bounds, currently it's ownly limited by kernel memory. -Work Around- Use NFSv2 mounts on filesystems that are used by lots of users such as "/var/mail". michael.eisler@Eng 1997-02-24 The above aork around is fine as long as the server is not a Solaris 2.5[.1] or 2.6 system. Since the ACL protocol has an ACCESS procedure for NFS V2, a Solaris 2.5 or alter system will also use the ACL cache system. ---------------------- End Sun Bug ID 4034003 ------------------------- We did try using V2 mounts as a test, and we still experienced the problem. --Jamie Hill -> ->-- Chris -> ->-- ->Chris Lamb, Unix Guy ->MeasureCast, Inc. ->503-241-1469 x247 -><skeezics(a)measurecast.com> -> ->

1 0

Problem to integrate F740 into a Windows 2000 domain (2)
by benny.wistrom＠cn.saab.se 03 Jan '01

03 Jan '01

Hi again! I have tried once again and I get the following messages when I try to integrate my filer into a Windows 2000 domain. CIFS server is beginning domain installation. CIFS server is locating PDC. Wed Jan 3 12:03:31 GMT [rc]: Connection with DC \\ZAMIRA established Wed Jan 3 12:03:31 GMT [rc]: Connection with DC \\ZAMIRA terminated Wed Jan 3 12:03:31 GMT [rc]: CIFS - Filer retrying authentication with backup password. Wed Jan 3 12:03:33 GMT [rc]: Connection with DC \\ZAMIRA established Wed Jan 3 12:03:33 GMT [rc]: Connection with DC \\ZAMIRA terminated Wed Jan 3 12:03:33 GMT [rc]: CIFS - Filer retrying installation. Wed Jan 3 12:03:35 GMT [rc]: Connection with DC \\ZAMIRA established CIFS could not start. See log. CIFS local server is shutting down... Wed Jan 3 12:03:35 GMT [rc]: Connection with DC \\ZAMIRA terminated zam> Wed Jan 3 12:03:35 GMT [rc]: CIFS - Filer's security information differs from domain controller. Wed Jan 3 12:03:36 GMT [nbns_timer]: All CIFS name registrations complete for local server What does the message "CIFS - Filer's security information differs from domain controller." mean? Any suggestions? -- Regards: Benny Wiström CSC Phone: +46 13 4653647 Systemadministrator 581 88 Linköping Fax: +46 13 185771 Benny.Wistrom(a)cn.saab.se Sweden Mobile: +46 13 4653647 Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. -Calvin & Hobbes (Bill Watterson) Talk sense to a fool and he calls you foolish. -- Euripides

2 1

RE: NFS server timeouts on the clients- on new 840's
by Fox, Adam 03 Jan '01

03 Jan '01

After checking the duplex settings (and that can't be stressed enough), you may also want to check the the rsize and wsize of your NFS connections. There was a change right around 5.3.5 (I believe) that changed the default rsize and wsize on the server from 8192 to 32768. Some networks have trouble with the larger transaction sizes and it causes timeouts. A way to test this would be to do an NFS mount from your sun with the mount options rsize=8192,wsize=8192. If this helps, then that's probably your issue. You can then tell the filer to change the size on the server side with options nfs.udp.xfersize This info can be found at: http://now.netapp.com/Knowledgebase/solutionarea.asp?id=ba668eb2-9bbd-11d4-9 2f7-080020c8339b&resource=&number=5&isExternal=0 Just another thing to check. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Krause, Oliver [mailto:OKrause@netapp.com] > Sent: Wednesday, January 03, 2001 6:07 AM > To: 'Premanshu Jain'; Smith, (CS) Michael > Cc: 'arr(a)oceanwave.com'; 'toasters(a)mathworks.com' > Subject: RE: NFS server timeouts on the clients- on new 840's > > > Looks like a common half-/full-duplex mismatch. Check your > network. On the > filer check your interface with ifstat <interface> and look > for CRC errors. > Always run your filer AND switchport in 100b-tx (not auto). > Sometimes this > connection is done right and people forget to check between > the switch and > the client ... > > Oliver > > > -----Original Message----- > > From: Premanshu Jain [mailto:PrJain@shastanets.com] > > Sent: Mittwoch, 3. Januar 2001 05:15 > > To: 'Mike Smith' > > Cc: 'arr(a)oceanwave.com'; 'toasters(a)mathworks.com' > > Subject: NFS server timeouts on the clients- on new 840's > > > > > > Hi mike, > > I just migrated from 740 to 840 and face this problem on the > > two Sun ultra > > 4500 NFS clients. Here are the error messages... > > _________________________________ > > 19:48:01 mthood last message repeated 10 times > > Jan 2 19:49:29 mthood unix: NFS server filebot not > > responding still trying > > Jan 2 19:49:29 mthood unix: NFS server filebot ok > > Jan 2 20:01:43 mthood xntpd[184]: time reset (step) 0.133869 s > > Jan 2 20:02:46 mthood unix: NFS server filebot not > > responding still trying > > Jan 2 20:02:46 mthood unix: NFS server filebot ok > > Jan 2 20:05:49 mthood automountd[135]: > > filebot:/vol/sw/.view.dat: No such > > file or directory > > Jan 2 20:05:49 mthood last message repeated 1 time > > Jan 2 20:07:42 mthood unix: NFS server filebot not > > responding still trying > > Jan 2 20:07:42 mthood unix: NFS server filebot ok > > Jan 2 20:08:42 mthood unix: NFS server filebot not > > responding still trying > > Jan 2 20:08:42 mthood unix: NFS server filebot ok > > _______________________ > > Can you bail me out of this issues. Both Sun systems are now running > > very-very slow . > > Thanks > > prem > > > > -----Original Message----- > > From: Mike Smith [mailto:mikesmit@netapp.com] > > Sent: Sunday, December 31, 2000 4:15 PM > > To: arr(a)oceanwave.com; toasters(a)mathworks.com > > Subject: Re: NFS server timeouts on the clients > > > > > > Based upon the description there is no way to tell exactly > > what the problem is. First off if you are using 10baseT > > then the 2M transfer will take 2 seconds. If you are using > > 100baseT (full duplex) then it will take 0.2 seconds. > > > > If you are using 10baseT then the transfer time is correct. > > If you are using 100baseT (full duplex) then I would take > > a look at the duplex settings on the filer side and then the > > switch side. If either side is not set exactly as the other side > > then it is possible you have a duplex mismatch. In which case > > I would simply manually set the port that the filer is connected > > to to full duplex. Then set the filer to full duplex manually: > > > > ifconfig e0 mediatype 100tx-fd > > > > Try the transfer again. You should see favorable results. > > Note: sometimes autonegotiation works ok but for the most > > part a lot of us stick to using manually set 100tx-fd on both the > > switch side and the filer side. Hope that helps. > > If not you might try contacting NetApp customer support and opening > > a case > > > > Mike Smith > > NetApp Escalations Engineer. > > mikesmit(a)netapp.com > > > > ----- Original Message ----- > > From: <arr(a)oceanwave.com> > > To: <toasters(a)mathworks.com> > > Sent: Sunday, December 31, 2000 3:10 PM > > Subject: NFS server timeouts on the clients > > > > > > > I have an brand new F720 running 5.3.6R2. We're exporting > > two qtrees via > > NFS > > > and CIFS. When the system is almost completely quiet, I > > try to tar up > > about > > > 2M of stuff and it takes FIVE minutes. I also see NFS > > timeout errors on > > all > > > NFS clients (the one I'm doing the tar from is specifically > > solaris 8, but > > I > > > see the timeouts on linux as well). > > > > > > I've tried NFS v2 and v3, both TCP and UDP, and nothing > > seems to help. > > netstat > > > doesn't seem to show packet collisions (the netowrk > > ispretty much dead), > > not a > > > lot of errors (<10%). I'm seeing writes about every 10 > > seconds (which > > should > > > mean good performance), and the CPU is mostly idle. Why > > the hell does a > > tar > > > of 2M take so bloody long? I can understand if I was > > moving a gig or so, > > but > > > 2M?! > > > > > > I've included important info (this was after I had changed > > to v2 UDP). Is > > > there something else I should look at? > > > > > > > > > >nfsstat -c > > > > > > Server rpc: > > > TCP: > > > calls badcalls nullrecv badlen xdrcall > > > 0 0 0 0 0 > > > > > > UDP: > > > calls badcalls nullrecv badlen xdrcall > > > 1354 0 0 0 0 > > > > > > Server nfs: > > > calls badcalls > > > 1306 0 > > > > > > Server nfs V2: (1306 calls) > > > null getattr setattr root lookup > > readlink read > > > 1 0% 372 28% 2 0% 0 0% 194 15% 0 0% > > 293 22% > > > wrcache write create remove rename link > > symlink > > > 0 0% 440 34% 2 0% 1 0% 0 0% 0 0% > > 0 0% > > > mkdir rmdir readdir statfs > > > 0 0% 0 0% 1 0% 0 0% > > > > > > Server nfs V3: (0 calls) > > > null getattr setattr lookup access > > readlink read > > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > > 0 0% > > > write create mkdir symlink mknod > > remove rmdir > > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > > 0 0% > > > rename link readdir readdir+ fsstat > > fsinfo pathconf > > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > > 0 0% > > > commit > > > 0 0% > > > > > > NFS V2 non-blocking request statistics: > > > null getattr setattr root lookup > > readlink read > > > 1 100% 372 100% 2 100% 0 0% 194 100% 0 0% > > 141 48% > > > wrcache write create remove rename link > > symlink > > > 0 0% 440 100% 1 50% 1 100% 0 0% 0 0% > > 0 0% > > > mkdir rmdir readdir statfs > > > 0 0% 0 0% 1 100% 0 0% > > > > > > NFS V3 non-blocking request statistics: > > > null getattr setattr lookup access > > readlink read > > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > > 0 0% > > > write create mkdir symlink mknod > > remove rmdir > > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > > 0 0% > > > rename link readdir readdir+ fsstat > > fsinfo pathconf > > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > > 0 0% > > > > > > NFS reply cache statistics: > > > TCP: > > > In progress Delay hits Misses Idempotent > > Non-idempotent > > > 0 0 0 0 0 > > > UDP: > > > In progress Delay hits Misses Idempotent > > Non-idempotent > > > 0 5 732 7 42 > > > > > > > > > >sysstat 1 > > > > > > CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s > > Cache > > > in out read write > read write > > age > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 3% 1 0 0 0 1 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 3% 32 0 0 5 3 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 6% 0 0 0 0 0 48 128 > 0 0 > > 19 > > > 2% 0 0 0 31 0 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 3% 4 0 0 2 1 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 2% 1 0 0 16 0 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > 3% 2 0 0 1 1 0 0 > 0 0 > > 19 > > > 5% 0 0 0 0 0 32 152 > 0 0 > > 19 > > > 2% 0 0 0 0 0 0 0 > 0 0 > > 19 > > > > > > > > > > > > >sysconfig -r > > > > > > Volume vol0 (root) > > > > > > RAID group 0 > > > > > > RAID Disk HA.ID HA SHELF BAY CHAN Used > (MB/blks) Phys > > (MB/blks) > > > --------- ----- ------------ ---- > > -------------- ---------- > > ---- > > > parity 1.3 1 0 3 FC:A 34500/70656000 > > 35003/71687368 > > > data 1.2 1 0 2 FC:A 34500/70656000 > > 35003/71687368 > > > data 1.0 1 0 0 FC:A 34500/70656000 > > 35003/71687368 > > > data 1.5 1 0 5 FC:A 34500/70656000 > > 35003/71687368 > > > data 1.6 1 0 6 FC:A 34500/70656000 > > 35003/71687368 > > > data 1.1 1 0 1 FC:A 34500/70656000 > > 35003/71687368 > > > > > > Spare disks > > > > > > RAID Disk HA.ID HA SHELF BAY CHAN Used > (MB/blks) Phys > > (MB/blks) > > > --------- ----- ------------ ---- > > -------------- ---------- > > ---- > > > spare 1.4 1 0 4 FC:A 0 > > 35003/71687368 > > > > > > > > > > netstat -s > > > > > > tcp: > > > 19180 packets sent > > > 16501 data packets (3116859 bytes) > > > 647 data packets (355343 bytes) retransmitted > > > 804 ack-only packets (114 delayed) > > > 0 URG only packets > > > 0 window probe packets > > > 1156 window update packets > > > 76 control packets > > > 22021 packets received > > > 15990 acks (for 3112800 bytes) > > > 187 duplicate acks > > > 0 acks for unsent data > > > 13688 packets (5178316 bytes) received in-sequence > > > 618 completely duplicate packets (890780 bytes) > > > 0 old duplicate packets > > > 10 packets with some dup. data (10 bytes duped) > > > 50 out-of-order packets (61320 bytes) > > > 0 packets (0 bytes) of data after window > > > 0 window probes > > > 0 window update packets > > > 1 packet received after close > > > 0 discarded for bad checksums > > > 0 discarded for bad header offset fields > > > 0 discarded because packet too short > > > 13 connection requests > > > 27 connection accepts > > > 3 bad connection attempts > > > 0 listen queue overflows > > > 32 connections established (including accepts) > > > 40 connections closed (including 1 drop) > > > 8 embryonic connections dropped > > > 15825 segments updated rtt (of 16329 attempts) > > > 531 retransmit timeouts > > > 0 connections dropped by rexmit timeout > > > 0 persist timeouts > > > 0 connections timed out in persist > > > 8 keepalive timeouts > > > 0 keepalive probes sent > > > 8 connections dropped by keepalive > > > 3594 correct ACK header predictions > > > 3474 correct data packet header predictions > > > 1758 PCB cache misses > > > 0 segments dropped at untrusted interface > > > 0 connection requests closed at filter > > > udp: > > > 3671023 datagrams received > > > 0 with incomplete header > > > 0 with bad data length field > > > 0 with bad checksum > > > 0 dropped due to no socket > > > 137 broadcast/multicast datagrams dropped due to no socket > > > 0 dropped due to full socket buffers > > > 3670886 delivered > > > 3665023 datagrams output > > > ip: > > > 7921585 total packets received > > > 0 bad header checksums > > > 0 with size smaller than minimum > > > 0 with size larger than maximum > > > 0 with data size < data length > > > 0 with header length < data size > > > 0 with data length < header length > > > 0 with bad options > > > 0 with incorrect version number > > > 0 packets with spoofed source address > > > 0 packets arrived on wrong port > > > 6499598 fragments received > > > 0 fragments dropped (dup or out of space) > > > 0 malformed fragments dropped > > > 0 overlapping fragments discarded > > > 3966 fragments dropped after timeout > > > 2272723 packets reassembled ok > > > 3693053 packets for this host > > > 790 packets for unknown/unsupported protocol > > > 0 packets forwarded > > > 867 packets not forwardable > > > 0 redirects sent > > > 3685059 packets sent from this host > > > 0 packets sent with fabricated ip header > > > 0 output packets dropped due to no bufs, etc. > > > 0 output packets discarded due to no route > > > 412593 output datagrams fragmented > > > 862312 fragments created > > > 0 datagrams that can't be fragmented > > > icmp: > > > 0 calls to icmp_error > > > 0 errors not generated 'cuz old message was icmp > > > Output histogram: > > > echo reply: 7 > > > 0 messages with bad code fields > > > 0 messages < minimum length > > > 0 bad checksums > > > 0 messages with bad length > > > Input histogram: > > > echo reply: 2 > > > echo: 7 > > > time exceeded: 790 > > > 7 message responses generated > > > > > > > > > > netstat -i > > > > > > Name Mtu Network Address > > Ipkts Ierrs > > Opkts > > > Oerrs Collis Queue > > > e8* 1500 none none 0 > > 0 0 > > > 0 0 0 > > > e0 1500 192.168.1 myhost 7929745 > > 5917 > > > 4 0 with incorrect version number > > > 0 packets with spoofed source address > > > 0 packets arrived on wrong port > > > 6499598 fragments received > > > 0 fragments dropped (dup or out of space) > > > 0 malformed fragments dropped > > > 0 overlapping fragments discarded > > > 3966 fragments dropped after timeout > > > 2272723 packets reassembled ok > > > 3693053 packets for this host > > > 790 packets for unknown/unsupported protocol > > > 0 packets forwarded > > > 867 packets not forwardable > > > 0 redirects sent > > > 3685059 packets sent from this host > > > 0 packets sent with fabricated ip header > > > 0 output packets dropped due to no bufs, etc. > > > 0 output packets discarded due to no route > > > 412593 output datagrams fragmented > > > 862312 fragments created > > > 0 datagrams that can't be fragmented > > > icmp: > > > 0 calls to icmp_error > > > 0 errors not generated 'cuz old message was icmp > > > Output histogram: > > > echo reply: 7 > > > 0 messages with bad code fields > > > 0 messages < minimum length > > > 0 bad checksums > > > 0 messages with bad length > > > Input histogram: > > > echo reply: 2 > > > echo: 7 > > > time exceeded: 790 > > > 7 message responses generated > > > > > > > > > > > > > > >

1 0

Re: Problem to integrate F740 into a Windows 2000 domain (2)
by benny.wistrom＠cn.saab.se 03 Jan '01

03 Jan '01

Problem solved! Thanks everyone for the input. It worked fine. It turned out that I had missed checking the "Allow pre-Windows 2000 authentication" box when I created the computer account. I also had to remove some files in the /etc directory on the filer because the filer had been part of another domain earlier. -- Regards: Benny Wiström CSC Phone: +46 13 4653647 Systemadministrator 581 88 Linköping Fax: +46 13 185771 Benny.Wistrom(a)cn.saab.se Sweden Mobile: +46 13 4653647 Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us. -Calvin & Hobbes (Bill Watterson) Talk sense to a fool and he calls you foolish. -- Euripides

1 0

RE: NFS server timeouts on the clients- on new 840's
by Krause, Oliver 03 Jan '01

03 Jan '01

Looks like a common half-/full-duplex mismatch. Check your network. On the filer check your interface with ifstat <interface> and look for CRC errors. Always run your filer AND switchport in 100b-tx (not auto). Sometimes this connection is done right and people forget to check between the switch and the client ... Oliver > -----Original Message----- > From: Premanshu Jain [mailto:PrJain@shastanets.com] > Sent: Mittwoch, 3. Januar 2001 05:15 > To: 'Mike Smith' > Cc: 'arr(a)oceanwave.com'; 'toasters(a)mathworks.com' > Subject: NFS server timeouts on the clients- on new 840's > > > Hi mike, > I just migrated from 740 to 840 and face this problem on the > two Sun ultra > 4500 NFS clients. Here are the error messages... > _________________________________ > 19:48:01 mthood last message repeated 10 times > Jan 2 19:49:29 mthood unix: NFS server filebot not > responding still trying > Jan 2 19:49:29 mthood unix: NFS server filebot ok > Jan 2 20:01:43 mthood xntpd[184]: time reset (step) 0.133869 s > Jan 2 20:02:46 mthood unix: NFS server filebot not > responding still trying > Jan 2 20:02:46 mthood unix: NFS server filebot ok > Jan 2 20:05:49 mthood automountd[135]: > filebot:/vol/sw/.view.dat: No such > file or directory > Jan 2 20:05:49 mthood last message repeated 1 time > Jan 2 20:07:42 mthood unix: NFS server filebot not > responding still trying > Jan 2 20:07:42 mthood unix: NFS server filebot ok > Jan 2 20:08:42 mthood unix: NFS server filebot not > responding still trying > Jan 2 20:08:42 mthood unix: NFS server filebot ok > _______________________ > Can you bail me out of this issues. Both Sun systems are now running > very-very slow . > Thanks > prem > > -----Original Message----- > From: Mike Smith [mailto:mikesmit@netapp.com] > Sent: Sunday, December 31, 2000 4:15 PM > To: arr(a)oceanwave.com; toasters(a)mathworks.com > Subject: Re: NFS server timeouts on the clients > > > Based upon the description there is no way to tell exactly > what the problem is. First off if you are using 10baseT > then the 2M transfer will take 2 seconds. If you are using > 100baseT (full duplex) then it will take 0.2 seconds. > > If you are using 10baseT then the transfer time is correct. > If you are using 100baseT (full duplex) then I would take > a look at the duplex settings on the filer side and then the > switch side. If either side is not set exactly as the other side > then it is possible you have a duplex mismatch. In which case > I would simply manually set the port that the filer is connected > to to full duplex. Then set the filer to full duplex manually: > > ifconfig e0 mediatype 100tx-fd > > Try the transfer again. You should see favorable results. > Note: sometimes autonegotiation works ok but for the most > part a lot of us stick to using manually set 100tx-fd on both the > switch side and the filer side. Hope that helps. > If not you might try contacting NetApp customer support and opening > a case > > Mike Smith > NetApp Escalations Engineer. > mikesmit(a)netapp.com > > ----- Original Message ----- > From: <arr(a)oceanwave.com> > To: <toasters(a)mathworks.com> > Sent: Sunday, December 31, 2000 3:10 PM > Subject: NFS server timeouts on the clients > > > > I have an brand new F720 running 5.3.6R2. We're exporting > two qtrees via > NFS > > and CIFS. When the system is almost completely quiet, I > try to tar up > about > > 2M of stuff and it takes FIVE minutes. I also see NFS > timeout errors on > all > > NFS clients (the one I'm doing the tar from is specifically > solaris 8, but > I > > see the timeouts on linux as well). > > > > I've tried NFS v2 and v3, both TCP and UDP, and nothing > seems to help. > netstat > > doesn't seem to show packet collisions (the netowrk > ispretty much dead), > not a > > lot of errors (<10%). I'm seeing writes about every 10 > seconds (which > should > > mean good performance), and the CPU is mostly idle. Why > the hell does a > tar > > of 2M take so bloody long? I can understand if I was > moving a gig or so, > but > > 2M?! > > > > I've included important info (this was after I had changed > to v2 UDP). Is > > there something else I should look at? > > > > > > >nfsstat -c > > > > Server rpc: > > TCP: > > calls badcalls nullrecv badlen xdrcall > > 0 0 0 0 0 > > > > UDP: > > calls badcalls nullrecv badlen xdrcall > > 1354 0 0 0 0 > > > > Server nfs: > > calls badcalls > > 1306 0 > > > > Server nfs V2: (1306 calls) > > null getattr setattr root lookup > readlink read > > 1 0% 372 28% 2 0% 0 0% 194 15% 0 0% > 293 22% > > wrcache write create remove rename link > symlink > > 0 0% 440 34% 2 0% 1 0% 0 0% 0 0% > 0 0% > > mkdir rmdir readdir statfs > > 0 0% 0 0% 1 0% 0 0% > > > > Server nfs V3: (0 calls) > > null getattr setattr lookup access > readlink read > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > 0 0% > > write create mkdir symlink mknod > remove rmdir > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > 0 0% > > rename link readdir readdir+ fsstat > fsinfo pathconf > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > 0 0% > > commit > > 0 0% > > > > NFS V2 non-blocking request statistics: > > null getattr setattr root lookup > readlink read > > 1 100% 372 100% 2 100% 0 0% 194 100% 0 0% > 141 48% > > wrcache write create remove rename link > symlink > > 0 0% 440 100% 1 50% 1 100% 0 0% 0 0% > 0 0% > > mkdir rmdir readdir statfs > > 0 0% 0 0% 1 100% 0 0% > > > > NFS V3 non-blocking request statistics: > > null getattr setattr lookup access > readlink read > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > 0 0% > > write create mkdir symlink mknod > remove rmdir > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > 0 0% > > rename link readdir readdir+ fsstat > fsinfo pathconf > > 0 0% 0 0% 0 0% 0 0% 0 0% 0 0% > 0 0% > > > > NFS reply cache statistics: > > TCP: > > In progress Delay hits Misses Idempotent > Non-idempotent > > 0 0 0 0 0 > > UDP: > > In progress Delay hits Misses Idempotent > Non-idempotent > > 0 5 732 7 42 > > > > > > >sysstat 1 > > > > CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s > Cache > > in out read write read write > age > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 3% 1 0 0 0 1 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 3% 32 0 0 5 3 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 6% 0 0 0 0 0 48 128 0 0 > 19 > > 2% 0 0 0 31 0 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 3% 4 0 0 2 1 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 2% 1 0 0 16 0 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > 3% 2 0 0 1 1 0 0 0 0 > 19 > > 5% 0 0 0 0 0 32 152 0 0 > 19 > > 2% 0 0 0 0 0 0 0 0 0 > 19 > > > > > > > > >sysconfig -r > > > > Volume vol0 (root) > > > > RAID group 0 > > > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys > (MB/blks) > > --------- ----- ------------ ---- > -------------- ---------- > ---- > > parity 1.3 1 0 3 FC:A 34500/70656000 > 35003/71687368 > > data 1.2 1 0 2 FC:A 34500/70656000 > 35003/71687368 > > data 1.0 1 0 0 FC:A 34500/70656000 > 35003/71687368 > > data 1.5 1 0 5 FC:A 34500/70656000 > 35003/71687368 > > data 1.6 1 0 6 FC:A 34500/70656000 > 35003/71687368 > > data 1.1 1 0 1 FC:A 34500/70656000 > 35003/71687368 > > > > Spare disks > > > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys > (MB/blks) > > --------- ----- ------------ ---- > -------------- ---------- > ---- > > spare 1.4 1 0 4 FC:A 0 > 35003/71687368 > > > > > > > netstat -s > > > > tcp: > > 19180 packets sent > > 16501 data packets (3116859 bytes) > > 647 data packets (355343 bytes) retransmitted > > 804 ack-only packets (114 delayed) > > 0 URG only packets > > 0 window probe packets > > 1156 window update packets > > 76 control packets > > 22021 packets received > > 15990 acks (for 3112800 bytes) > > 187 duplicate acks > > 0 acks for unsent data > > 13688 packets (5178316 bytes) received in-sequence > > 618 completely duplicate packets (890780 bytes) > > 0 old duplicate packets > > 10 packets with some dup. data (10 bytes duped) > > 50 out-of-order packets (61320 bytes) > > 0 packets (0 bytes) of data after window > > 0 window probes > > 0 window update packets > > 1 packet received after close > > 0 discarded for bad checksums > > 0 discarded for bad header offset fields > > 0 discarded because packet too short > > 13 connection requests > > 27 connection accepts > > 3 bad connection attempts > > 0 listen queue overflows > > 32 connections established (including accepts) > > 40 connections closed (including 1 drop) > > 8 embryonic connections dropped > > 15825 segments updated rtt (of 16329 attempts) > > 531 retransmit timeouts > > 0 connections dropped by rexmit timeout > > 0 persist timeouts > > 0 connections timed out in persist > > 8 keepalive timeouts > > 0 keepalive probes sent > > 8 connections dropped by keepalive > > 3594 correct ACK header predictions > > 3474 correct data packet header predictions > > 1758 PCB cache misses > > 0 segments dropped at untrusted interface > > 0 connection requests closed at filter > > udp: > > 3671023 datagrams received > > 0 with incomplete header > > 0 with bad data length field > > 0 with bad checksum > > 0 dropped due to no socket > > 137 broadcast/multicast datagrams dropped due to no socket > > 0 dropped due to full socket buffers > > 3670886 delivered > > 3665023 datagrams output > > ip: > > 7921585 total packets received > > 0 bad header checksums > > 0 with size smaller than minimum > > 0 with size larger than maximum > > 0 with data size < data length > > 0 with header length < data size > > 0 with data length < header length > > 0 with bad options > > 0 with incorrect version number > > 0 packets with spoofed source address > > 0 packets arrived on wrong port > > 6499598 fragments received > > 0 fragments dropped (dup or out of space) > > 0 malformed fragments dropped > > 0 overlapping fragments discarded > > 3966 fragments dropped after timeout > > 2272723 packets reassembled ok > > 3693053 packets for this host > > 790 packets for unknown/unsupported protocol > > 0 packets forwarded > > 867 packets not forwardable > > 0 redirects sent > > 3685059 packets sent from this host > > 0 packets sent with fabricated ip header > > 0 output packets dropped due to no bufs, etc. > > 0 output packets discarded due to no route > > 412593 output datagrams fragmented > > 862312 fragments created > > 0 datagrams that can't be fragmented > > icmp: > > 0 calls to icmp_error > > 0 errors not generated 'cuz old message was icmp > > Output histogram: > > echo reply: 7 > > 0 messages with bad code fields > > 0 messages < minimum length > > 0 bad checksums > > 0 messages with bad length > > Input histogram: > > echo reply: 2 > > echo: 7 > > time exceeded: 790 > > 7 message responses generated > > > > > > > netstat -i > > > > Name Mtu Network Address > Ipkts Ierrs > Opkts > > Oerrs Collis Queue > > e8* 1500 none none 0 > 0 0 > > 0 0 0 > > e0 1500 192.168.1 myhost 7929745 > 5917 > > 4 0 with incorrect version number > > 0 packets with spoofed source address > > 0 packets arrived on wrong port > > 6499598 fragments received > > 0 fragments dropped (dup or out of space) > > 0 malformed fragments dropped > > 0 overlapping fragments discarded > > 3966 fragments dropped after timeout > > 2272723 packets reassembled ok > > 3693053 packets for this host > > 790 packets for unknown/unsupported protocol > > 0 packets forwarded > > 867 packets not forwardable > > 0 redirects sent > > 3685059 packets sent from this host > > 0 packets sent with fabricated ip header > > 0 output packets dropped due to no bufs, etc. > > 0 output packets discarded due to no route > > 412593 output datagrams fragmented > > 862312 fragments created > > 0 datagrams that can't be fragmented > > icmp: > > 0 calls to icmp_error > > 0 errors not generated 'cuz old message was icmp > > Output histogram: > > echo reply: 7 > > 0 messages with bad code fields > > 0 messages < minimum length > > 0 bad checksums > > 0 messages with bad length > > Input histogram: > > echo reply: 2 > > echo: 7 > > time exceeded: 790 > > 7 message responses generated > > > > > > > > >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

toasters