toasters

toasters@lists.teaparty.net

1 participants
13523 discussions

NIS problem with netgroup file
by Cheryl Cruddace 25 May '00

25 May '00

I have developed a problem using the netgroup map on our NIS server that resulted in having to copy the netgroup file to the filer and changing the nsswitch.conf file to point to the local file. This first occurred our F740 running OnTap 5.2.3 and continued after I upgraded to 5.3.4R3. The netgroup file used to have a mixture of systems with and without FQDN. Right before this occurred all were set to FQDN. I know there was a bug with using fully qualified names but that was supposedly fixed in later OnTap OS's. Example: Netgroup with FQDN feather.llnl.gov Without FQDN feather The interesting thing is that I can use a file with FQDN on the filer but not on the NIS server. As an experiment, I modified the netgroup file on the NIS server and took out FQDN, pushed out the maps, set the filer to use the maps and I could again mount the home directories on clients. If I changed back to FQDN, it will not let me mount from clients unless I use the netgroup file local to the filer. Any ideas? P.S. I want my mail to go to my alias instead of to a specific machine. How do I change that, unsubscribe and subscribe won't work, will it? Need to be cruddace1(a)llnl.gov instead of cruddace(a)feather.llnl.gov.

1 0

supported Tape Drives
by jmiddlebrooks＠datalink.com 25 May '00

25 May '00

Where could I find a list of qualified tape drives that can be attached to the F700 series filer? Thanks in Advance Jason Middlebrooks Systems Engineer Datalink Corp. 888-933-9327 x2970

1 0

Re: Migrating from NetApp to new NetApp
by Jay Sekora 25 May '00

25 May '00

I second other people's recommendations of rsync. rsync is great. There's another possibility, though, that has some of the same advantages. With rsync, you can do a preliminary copy that does everything while the system is live, and then schedule a hopefully short downtime to update just those things that have changed. Dump/restore should be able to do the same thing. While your filer is up and serving, dump/restore everything at level 0. (You can do this by rsh'ing the dump to the old filer and the restore to the new server, of course.) Then, when you have downtime scheduled, dump/restore at level 1 (making sure there were no intervening level 0 dumps). That way, you're only copying the changes, and the dump/restore will be much quicker. (Obviously, because you're going over the net, this is going to be slower than something like "vol copy". However, you can do the level 0 dump without interrupting service, so probably you only care about the time taken by the level 1 dump.) Basically, that amounts to doing by hand what rsync does automatically. Probably a bit more efficient than rsync (because less general). -j. Jay Sekora <jay(a)ccs.neu.edu> Unix Systems Administrator Northeastern University College of Computer Science

1 0

vol copy speed?
by Steve Losen 25 May '00

25 May '00

We have two F630s in a CF pair, with a total of 7 shelves of 9G drives. We are upgrading to 5.3.5R2P2 and adding 12 36G drives in 2 shelves. We have enough spare slots and spare disks in our existing 7 shelves to depopulate one shelf and leave us with 42 9G disks in 6 shelves 12 36G disks in 2 shelves We want to do some reshuffling of our shelves between the two filers. We plan to copy the following volume to a new volume consisting of 10 36G disks (leaving 2 hot spares). Filesystem kbytes used avail capacity Mounted on /vol/vol0/ 139160864 115462812 23698052 83% /vol/vol0/ /vol/vol0/.snapshot 34790216 12362380 22427836 36% /vol/vol0/.snapshot We are thinking about using vol copy and we would like to preserve all the snapshots. I think it would be faster to copy locally. However, we have 100Mb ethernet between the two filers, so would it be faster to hook up the shelves on different filers and vol copy across the net? If this copy can be done in under, say, 5 hours, we have the luxury of turning off NFS and CIFS and giving vol copy 100% of the CPU. We have to shut down both filers for OS upgrade, recabling shelves, etc., so downtime is inevitable. But if this copy is going to take over 5 hours, that's probably too long. Is there any information about how fast vol copy runs? Am I correct that vol copy does not require a special license? We figure that we have two options here 1) one lengthy downtime where we use vol copy during the downtime. 2) two shorter downtimes. In the first downtime we upgrade the OS and add the 36G shelves. Then we bring the filers back up and run a relatively slow dump/restore that loses snapshots. In the second downtime we run an incremental dump/restore and move the disk shelves to their final locations. If vol copy is "fast enough," option 1 would be easier and less disruptive than option 2. Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

1 0

Fibre Cards?
by jmiddlebrooks＠datalink.com 25 May '00

25 May '00

Do the Netapp F700 series only support Qlogic ISP2100 cards fibre cards? What fibre cards can be used in the Filer? Emulex? JNI? Thanks in Advance Jason Middlebrooks Systems Engineer Datalink Corp. 888-933-9327 x2970

1 0

Re: Migrating from NetApp to new NetApp
by Richard L. Rhodes 25 May '00

25 May '00

I wonder if Netapp would give out a temporary snapmirror license to help migrating data between servers? That's kind of how I migrate data between unix systems via rdist. Rick On 25 May 2000, at 11:15, Cliff Nadler wrote: > > > > Recently i migrated data (over 110GB) from F520 to F760. With a gig > card > > insatlled in both the systems, we acheived 35GB per hour by using vol > copy > > command. I am not sure about F230 taking a gig card. > >

1 0

Stale File Handles
by Jay Orr 25 May '00

25 May '00

AARRRGGHH!!! Ok, so I queried the list about this a year ago (early May '99) but am dealing with it again. Guy Harris was kind enough to help, and if you're out there I could use your help again. We had a power outage a week ago that shut down all our desktop systems - but not our filers and servers. Now, we have at random times during the day a large majority of systems griping : NFS write error on host hardrock: Stale NFS file handle. (file handle: 2ae0500 51356400 20000000 aa5c8 54417810 5c140000 2ae0500 51356400) They all have the same File handle, and the toaster has no error messages in its etc/messages files. I tried rebooting a few systems, but they still generate these error messages. I was trying to figure out what file it is by extracting an INODE number, but what Guy said before doesn't match : >In 5.0, we had to add a file system ID; file handles in 5.0 and later >consist of: > > 32-bit file ID for mount point > 32-bit generation count for mount point > 8-bit snapshot ID in which file resides > 8-bit unused byte > 32-bit file ID for file > 32-bit generation count for file > 32-bit volume ID for file > 32-bit file ID for export point > 32-bit combined snapshot ID and generation number for export > point; > the upper 8 bits of that 32-bit quantity are the snapshot ID > and the lower 24 bits are the generation number. > >The file's file ID (but not the mount point's or export point's file ID) >is *big-endian*; So, any ideas as to how to figure this out? Thanks! ----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO

3 4

RE: Problem in Saving CDE Settings
by Schepers, Jan 25 May '00

25 May '00

Hello all, > I think it´s a problem with the permissions on your home > directory. The dtlogin process (CDE) reads > and writes configuration files in the > homedirectory (~/.dtlogin/..). The owner of the > process is root --> But root > has not permissions on mounted directories! When the problem is caused by a dtlogin process that tries to write as root to the users home directory, then we are talking about a CDE design error. The remedy for the problem lies in changing CDE in such a way that it uses the concerning user identity to read/write files to the users home directory. This is possible since it are divine powers that cause the problem. All other actions like opening up directories, exporting for root with or without subnet stuff are merely an intermediate solution. Yann

1 0

Re: Migrating from NetApp to new NetApp
by Sateesh Mucharla 25 May '00

25 May '00

Kelsey, Recently i migrated data (over 110GB) from F520 to F760. With a gig card insatlled in both the systems, we acheived 35GB per hour by using vol copy command. I am not sure about F230 taking a gig card. Alternately, you could use cpio for data transfer from any unix host. Its very efficient. I am acheiving 7GB per hour on regular network. Cheers Sateesh National Semiconductors > X-envelope-info: <kgc(a)sonic.net> > Date: Wed, 24 May 2000 14:50:25 -0700 > From: Kelsey Cummings <kgc(a)sonic.net> > X-Accept-Language: en > MIME-Version: 1.0 > To: toasters(a)mathworks.com > Subject: Migrating from NetApp to new NetApp > Content-Transfer-Encoding: 7bit > > I've got a f230 with 4 shelves of 4GB disks and its replacement, an > f740. I talked to netapp support and they recommended that the best > method to move the data from the f230 to the f740 would be to tapes with > dump and restore. I can't believe that there isn't a more efficient way > to do this. We are an ISP and all mail/ftp/http is served off of the > netapp, any downtime will be painfull so we'd like to minimize it as > best we can. > > What choices to migrate the data do we have? We've considered tar/cpio > over nfs but that's going to take some time even if we migrate one > service at a time. dump/restore seems clumsy. and plain ole 'cp' would > take forever. Apparently there are issues with volcopy going from SCSI > to FCAL, is that true? > > -- > Kelsey Cummings - kgc(a)sonic.net sonic.net > System Administrator 300 B Street, Ste 101 > 707.522.1000 (Voice) Santa Rosa, CA 95404 > 707.547.2199 (Fax) http://www.sonic.net/ > Fingerprint = 7F 59 43 1B 44 8A 0D 57 91 08 73 73 7A 48 90 C5

2 1

Re: software distribution with NDMPcopy/SnapMirror over WANs?
by Tor Lillqvist 25 May '00

25 May '00

> I believe "rsync" utility can help you out.... Definitely. FYI: Do not even consider rdist. In the common case of very small daily changes, rsync is one magnitude faster than rdist for replicating from one filer to another. (If lots of files change every day, the actual data transfer time will probably dominate, and the difference will not be that great.) Of course, SnapMirror is probably one magnitude faster than any replication using intermediate NFS clients such as rsync, as has other advantages as well... --tml

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