toasters

toasters@lists.teaparty.net

13520 discussions

回复: FreeBSD client NFS problems
by William ding 07 Apr '00

07 Apr '00

Hi Mike : We use NFS V3 UDP and set NMBCLUSTER=40960 at kernel config , but always shutdown,could you give us some advice ? Thanks a lot -----Original Message----- 发件人: Mike Horwath <drechsau(a)tiny.net> 收件人: William ding <ding(a)staff.163.com> 抄送: toasters(a)mathworks.com <toasters(a)mathworks.com> 日期: 2000年4月6日 7:14 主题: Re: FreeBSD client NFS problems >On Thu, Apr 06, 2000 at 07:45:53PM -0700, William ding wrote: >> I have two FreeBSD clients NFS mounting a volume from a Filer. >> The versions are 3.4 and 4.0. >> >> When NFS is being used the memory usage of both machines >> climbs steadily and a reboot occurs (about 2-3 times per >> day). >> >> Is anyone aware of this problem and know of any patches >> or new versions that may fix this problem ? > >Are you mounting V2 or V3 and over UDP or TCP? > >I bet things would be dandy at V2 UDP. > >-- >Mike Horwath Admin & Manager @ VISI.com WORK: drechsau(a)visi.com >IRC: Drechsau http://www.visi.com/ HOME: drechsau(a)geeks.org >The only Minnesota ISP with public statistics: http://noc.visi.com/ > Garbage In -- Gospel Out. - berkeley fortune(6) >

1 0

Re: snapshots dates
by Fred Ab 06 Apr '00

06 Apr '00

Looks fine on my machine (Ultra5) and Netapp is a n old 520 and old version of OS: NetApp Release 5.1.2R3: Wed Nov 25 17:20:58 PST 1998 ultrax05--ab[52] pwd /user/abc/.snapshot ultrax05--ab[53] ls -l total 520 drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.0/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.1/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.2/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.3/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.4/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.5/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.6/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 hourly.7/ drwxrwxrwx 101 abc nobody 20480 Apr 5 18:33 nightly.0/ drwxrwxrwx 101 abc nobody 20480 Apr 4 14:47 nightly.1/ drwxrwxrwx 100 abc nobody 20480 Apr 3 16:26 nightly.2/ drwxrwxrwx 100 abc nobody 20480 Mar 31 16:19 weekly.0/ drwxrwxrwx 100 abc nobody 20480 Mar 22 12:30 weekly.1/ ===}Date: Thu, 06 Apr 2000 14:33:45 -0700 ===}From: Frank Gilmurray <frank(a)erg.sri.com> ===}X-Accept-Language: en ===}Mime-Version: 1.0 ===}To: toasters(a)mathworks.com ===}Cc: bryan.anderson(a)netapp.com ===}Subject: snapshots dates ===}Content-Transfer-Encoding: 7bit ===} ===}>From a Solaris 7 system we're seeing the same dates on all our snapshots ===}(but 'snap list' on the filer gives the correct dates). The filer date ===}is correct. Has anyone else seen this? Is there a fix or workaround? ===} ===}Thanks much, Frank ===} ===}PS Is there an archive of the toaster messages? ===} ===} ===}quetzalcoatl:/vol1# ls -l .snapshot ===}total 88 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 hourly.0 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 hourly.1 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 hourly.2 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 hourly.3 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 hourly.4 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 hourly.5 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 nightly.0 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 nightly.1 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 nightly.2 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 weekly.0 ===}drwxr-xr-x 4 root root 4096 Mar 22 11:12 weekly.1 ===}quetzalcoatl:/vol1#

1 0

RE: Legato NetApp client
by Hackett, Roger 06 Apr '00

06 Apr '00

Thanks for the reply Arthur. The NetApp client is a very different beast from any other Legato client I've worked with. Though the Legato ClientPak for NetApp README references an na_install executable that is supposed to install nsrexecd on the NetApp, there is no such process running on the NetApp (determined by issuing rc_toggle_basic followed by ps on the filer console while a backup was in progress). All that seems to be running on the filer is a java thread(s) related to the backup. This makes sense as the ClientPak documentation also says the it interfaces to java engine that runs on the filer. The na_recover command actually executes on the administrative host (apparently communicating to the java engine on the filer) rather than the filer itself. There is no interactive mode available. later... Roger -----Original Message----- From: Arthur Darren Dunham [mailto:add@netcom.com] Sent: Thursday, April 06, 2000 11:42 AM To: Roger.Hackett(a)mms.gov Subject: Re: Legato NetApp client > > We have a NetApp F760 running ONTAP 5.3.5 and the Legato NetWorker ClientPak > for NetApp, release 5.5 that we are configuring for deployment. In my > initial tests I have been able to setup the NetApp as a Legato client, > schedule backups from our Legato server, do manual backups from the admin > host's mount point of specific NetApp volumes and restore entire save sets. > > My problem/question concerns individual file restores. How does one > determine if a specific file is in a specific save set? The Legato NetApp > client docs state the you can use the mminfo command on the Legato host and > specify file names (mminfo -c filer_name -N /vol/volx/file_name) but both > empirical tests and the mminfo manpage show that the -N option is for the > save set name (such as /vol/vol0 or /vol/vol1) and no individual file > information is returned. The results are essentially the same as using the > Indexes button of nwadmin, you get a list of save set names and save set > ids. Correct. mminfo peruses the media database (not the file database) and has no information about individual files. I have been able to restore a single file (na_recover -s nsrhost -S > ssid -a /vol/vol0/qtree_name/filename) by listing each different ssid until > the request succeeds. Hm.. I don't have the netapp client, so I'm not sure how this differs... The normal unix client is interactive if you don't specify a file. After cd'ing into a directory, you can 'versions filename'. It will display the differnet versions of that file that are on different tapes. You could also do 'recover -s nsrhost -t <date>' and get back the last version of the file that was prior to that date. -- Darren Dunham ddunham(a)taos.com Unix System Administrator Taos - The SysAdmin Company Got some Dr Pepper? Santa Clara, CA < Please move on, ...nothing to see here, please disperse >

1 0

回复: FreeBSD client NFS problems
by William ding 06 Apr '00

06 Apr '00

We use "nfsiod -n 20" when starup... but after 5 hours, it will crash! -----Original Message----- 发件人: Nick Hilliard <nick(a)iol.ie> 收件人: ding(a)staff.163.com <ding(a)staff.163.com> 抄送: toasters(a)mathworks.com <toasters(a)mathworks.com> 日期: 2000年4月6日 7:01 主题: Re: FreeBSD client NFS problems >> I have two FreeBSD clients NFS mounting a volume from a Filer. >> The versions are 3.4 and 4.0. >> >> When NFS is being used the memory usage of both machines >> climbs steadily and a reboot occurs (about 2-3 times per >> day). > >Sounds odd. Are you sure that this has got to do with NFS usage? I >haven't used 4.0 in production, but 3.x was pretty solid, and the only times >that these boxes are rebooted is for kernel upgrades. > >How do you define "out of memory", and what sort of things are these boxes >doing? > >Nick >

2 1

improving filer performance
by Todd C. Merrill 06 Apr '00

06 Apr '00

I am trying to (what else?) improve the performance of the filers that I have. Here are the configs and the environment in which they run. My specific questions follow: I have two F740's with 14x 18GB FC-AL disks and a trunked 4x 100 Mb/s ethernet card. These filers serve software development sandboxes with a few million files (median file size about 4 kB), not more than a few thousand in the largest directories. These filers are used for both CIFS and NFS client builds; NFS traffic is limited to UDP only (`options nfs.tcp.enable off`) to keep the network overhead down on that protocol. Mix is about 60-75% NFS; the rest, CIFS. Running ONTAP 5.3.4R3P2. CPU load is more often than not above 50%, often 75-90% or more; usually 3,000 - 5,000 ops/; cache age is rarely above 3--most often 1 or 0. Consistency points are usually at the maximum of once every 10 seconds (as measured by disk writes with `sysstat`). I was poking around on the SPEC pages, and in the footnotes to the NetApp entries are these parameters: options nosnap 1 # to disable periodic snapshot creation, for reproducibility options nosnapdir 1 # to avoid inserting .snapshot entry when reading directories options raid.scrub.enable off # to disable periodic RAID scrubs, for reproducibility options minra 1 # to minimize file read-ahead options udp_lg_dgram.xmit_cksum.offload 1 # to offload checksum computations onto the Gigabit NIC Openboot settings on the F740: setenv java? false # to disable the Java Virtual Machine http://www.spec.org/osg/sfs97/results/res98q3/sfs97-980805-00008.html http://www.spec.org/osg/sfs97/results/res99q2/sfs97-19990416-00045.html I have a few questions: 1a. Regarding snapshots, many of my development sandboxes are "disposable" so I don't care about snapshots. The first two options might help me. In addition, if I set `snap reserve volX 0`, will that actually turn off snapshots, and reduce overhead on the filer? The options only seem to turn off *automatic* snapshots and the *display* of the ".snapshot" directory. 1b. Would disabling these two options *prevent* me from `cd`ing into the .snapshot directory? Even though it is visible by default at the root of the mount point, you can `cd` into the directory ".snapshot" at any point: 37 machine:/devel/scratch>ls -a . .. .snapshot toddc 38 machine:/devel/scratch>cd toddc 39 machine:/devel/scratch/toddc>ls -a . Testing.doc devtools .. dump.image.gz 40 machine:/devel/scratch/toddc>cd .snapshot 41 machine:/devel/scratch/toddc/.snapshot>pwd /devel/scratch/toddc/.snapshot 42 machine:/devel/scratch/toddc/.snapshot>ls backup hourly.1 nightly.0 hourly.0 hourly.2 1c. In addition, I'm thinking of breaking up my 14-disk filer from a RAID 13d+1p configuration into, say, two RAID groups and two volumes as 3d+1p and 9d+1p. (Multiple RAID groups are allowed per volume; I assume multiple volumes per RAID group is still disallowed?) The former would have the stuff I need snapshotted and the latter the stuff I don't. I have a churn rate of about 30-40%. Thoughts? 2. What does "options minra 1" buy me? What is the number when minra=off, the default? (If it's just a boolean, nevermind!) Given I have a development environment with lots of small files, it seems as if turning this option on will benefit me a lot. However, some more information on this would help. 3. Does the udp_lg_dgram.xmit_cksum.offload option also apply to quad-ethernet cards? Will it help if the ports are trunked with a virtual interface? 4. Why is my filer running Java? If I disable that, would we see any administration impact? (These filers are administered solely via the CLI.) I do see the messages file logs [Java Thread]: TimeDaemon: timed: adjusting time messages all the time. Would I loose the ability to keep the filer in time sync? What else might I loose? To prevent a knee-jerk reaction, for the purposes of this discussion, upgrading my filer to an F760 is not an option. ;) I want to leverage what I have now, as best I can. I thought about opening a tech support call, and still may, but I thought some real life input from the trenches would be useful as a start. Until next time... The Mathworks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill(a)mathworks.com http://www.mathworks.com ---

4 6

Legato NetApp client
by Hackett, Roger 06 Apr '00

06 Apr '00

We have a NetApp F760 running ONTAP 5.3.5 and the Legato NetWorker ClientPak for NetApp, release 5.5 that we are configuring for deployment. In my initial tests I have been able to setup the NetApp as a Legato client, schedule backups from our Legato server, do manual backups from the admin host's mount point of specific NetApp volumes and restore entire save sets. My problem/question concerns individual file restores. How does one determine if a specific file is in a specific save set? The Legato NetApp client docs state the you can use the mminfo command on the Legato host and specify file names (mminfo -c filer_name -N /vol/volx/file_name) but both empirical tests and the mminfo manpage show that the -N option is for the save set name (such as /vol/vol0 or /vol/vol1) and no individual file information is returned. The results are essentially the same as using the Indexes button of nwadmin, you get a list of save set names and save set ids. I have been able to restore a single file (na_recover -s nsrhost -S ssid -a /vol/vol0/qtree_name/filename) by listing each different ssid until the request succeeds. It looks like we will depend on snapshots for individual file restores and treat the Legato backups as "disaster recovery" only. -- Roger Hackett ACS-GSG Minerals Management Service - Gulf of Mexico Region U.S. Department of the Interior roger.hackett(a)mms.gov

1 0

FreeBSD client NFS problems
by William ding 06 Apr '00

06 Apr '00

I have two FreeBSD clients NFS mounting a volume from a Filer. The versions are 3.4 and 4.0. When NFS is being used the memory usage of both machines climbs steadily and a reboot occurs (about 2-3 times per day). Is anyone aware of this problem and know of any patches or new versions that may fix this problem ? William ding

4 3

RE: Can VIFs work with 3Com switches?
by Bond, Andrew 06 Apr '00

06 Apr '00

Hi Chris, Yes, the 3300 works with the filer. 3300 firmware must be rev 2.0 or above. Regards, Andrew > -----Original Message----- > From: owner-dl-toasters(a)netapp.com > [mailto:owner-dl-toasters@netapp.com]On Behalf Of Chris Thompson > Sent: 05 April 2000 21:18 > To: toasters(a)mathworks.com > Subject: Can VIFs work with 3Com switches? > > > This is thinking a few months into the future for us, but it might be > useful to know the answer now... > > Can one use VIFs in ONTAP together with the port trunking > facilities of > a 3Com SuperStack 3300 switch to treat two or more 100BaseT > connections > as a single interface, with load balancing at both ends? Has > anyone any > experience with such a configuration? > > Chris Thompson University of Cambridge > Computing Service, > Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, > Phone: +44 1223 334715 United Kingdom. >

1 0

Can VIFs work with 3Com switches?
by Chris Thompson 06 Apr '00

06 Apr '00

This is thinking a few months into the future for us, but it might be useful to know the answer now... Can one use VIFs in ONTAP together with the port trunking facilities of a 3Com SuperStack 3300 switch to treat two or more 100BaseT connections as a single interface, with load balancing at both ends? Has anyone any experience with such a configuration? Chris Thompson University of Cambridge Computing Service, Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.

2 1

RE: EMC Celerra vs NetApp Filer
by Sam Schorr 04 Apr '00

04 Apr '00

Interesting. I got a different answer from my EMC engineering people. The following is a quote: "Stripes can exist either within the Sym ("meta-volume") or outside the Sym using OS (or volume management) tools. Within the Sym, if a stripe is built across Mirrored volumes, the stripe remains available provided that one does not lose both halves of the same mirror. Example, four mirrored pairs (A/a, B/b, C/c, and D/d) with a stripe built across the four. Up to four disks could be lost as long as one of each pair is still good. We will not build a meta-volume such that 2 or more parts reside on the same physical - this violates our configuration rules. Outside the Sym the same holds true provided that one does not build stripes with multiple pieces coming from the same physical. The net is - as long as the underlying parity (mirror or otherwise) maintains the availability of the parts of a stripe, the whole stripe will remain available." --srs -----Original Message----- From: Steve Gremban [mailto:gremban@msp.sc.ti.com] Sent: Tuesday, April 04, 2000 11:04 AM To: toasters@mathworks. com Subject: Re: EMC Celerra vs NetApp Filer On an EMC if a disk goes out on one side of a mirror (we'll call it side A), side A will be offline (all of the disks in side A, not just the bad drive). Therefore, any new writes will be seen on side B but not on the drives of side A and you can't use side A drives to recover from subsequent side B drive failures. My EMC SE said that only if both sides of the mirror have simultaneous drive failures taking them both down at the same time is there a chance of recovering and that it would take a lot of work. (this assumes that the bad drives weren't mirrors of each other) Brian Tao wrote: > On Mon, 3 Apr 2000, Bruce Sterling Woodcock wrote: > > > > I don't see how? When one mirror loses a disk, the whole thing is > > lost; you switch over to the other mirror, which has n-1 disks as > > the RAID 4 array. So your initial chance of failure is 2n-1 and > > then n-1 for a second failure whereas RAID 4 is just n followed by > > n-1 for the second failure To be somewhat anal about it, the initial chance of failure of mirrored partitions is 2(n-1). :) But you're right, you have a higher probability of being put at risk using a mirror (just needs 1 disk going bad out of 2n-2 disks) than with RAID4 (1 disk bad out of n disks). Once that 1st disk is lost the probabilities of a second failure are the same for both (n-1). If EMC had actually implemented their mirroring like Brian Tao mentions below then their mirroring would be much more reliable than RAID4. > > > I think you're talking about RAID 0+1 (taking a RAID-0 set and > mirroring it on another RAID-0 set, which is just silly). RAID 1+0 > does the mirroring first, then the striping/concatenation: > > +----+----+ +--------------+ +------------+ > | 1A | 1B | | RAID-1 set 1 | | | > +----+----+ +--------------+ | | > | 2A | 2B | | RAID-1 set 2 | | | > +----+----+ +--------------+ | | > | 3A | 3B | | RAID-1 set 3 | | | > +----+----+ +--------------+ | | > | 4A | 4B | --> | RAID-1 set 4 | --> | RAID 0 | > +----+----+ +--------------+ |(7 "drives")| > | 5A | 5B | | RAID-1 set 5 | | | > +----+----+ +--------------+ | | > | 6A | 6B | | RAID-1 set 6 | | | > +----+----+ +--------------+ | | > | 7A | 7B | | RAID-1 set 7 | | | > +----+----+ +--------------+ +------------+ > [etc...] > > The A's and B's are drives of a mirrored pair. You could lose, > say, drives 1A, 2A, 4B, 5B and 7A and still have a functional RAID 0, > because no single mirror is completely broken. You could lose the > entire shelf containing the A drives and not have an outage (something > from which today's Netapps cannot automatically recover, clustering or > no clustering). Having mirrored pairs in RAID 4 (i.e., having > mirrored data and parity drives) and the ability to concurrently > rebuild multiple broken mirrors to hot spares would really give Netapp > a leg up on other NAS vendors, IMHO. > > > Oh, are the drives mirror images of each-other too? I didn't > > realize that. So if Drive 1 in Mirror A fails, breaking the mirror, > > and then Drive 2 in Mirror B fails, Mirror B will be smart enough to > > switch over to Drive 2 in Mirror A? > > As far as the RAID 0 is concerned, single drive failures within > each mirrored pair does not result in that stripe being down, because > the remaining half of the mirror is still online. If you lose, say, > drives 4A and 4B in a RAID 1+0, then you're toast. In RAID 1+4 (or > 1+5), you would still have the parity drive. > > > -- > Brian Tao (BT300, taob(a)risc.org) > "Though this be madness, yet there is method in't"

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