toasters

toasters@lists.teaparty.net

13515 discussions

RE: Good experience with Netapp & exchange
by Jay Newton 19 Oct '01

19 Oct '01

I just finished migrating a 43 gig InfoStore to our 840 Filer. I created a new Exchange server and added it to the site. I then moved the new databases to the Filer and set up all the Snapshot stuff with SnapManager for Exchange. I then migrated all 679 mailboxes to the new server on the Filer and voila! 99% of the user population did not notice the difference. Address books and calendars pop up a little quicker as well. I then back up the Snapshot once a day to our tape library using CommVault Galaxy which has incredible Exchange support. There are a couple of really important things to remember when doing this. First, you really need a private network of 100 megabit or better for the Exchange server to talk to the Filer. You don't want to share traffic with everyone else. Use a crossover cable and use the IP in the path just to be 100% certain traffic is on the private network. Next, buy a copy of SnapManager for Exchange. It makes the whole thing work more smoothly. Finally, make sure you have another server attached to that private network to run Snap verifies. Snap verifies make sure the Snapshot you just took is consistent and restorable. You can Snap an Exchange database and defer verification until later and on another machine. That gives you about a 15 second window where performance marginally degrades every time you do a Snapshot. Our experience is 1 gig per minute doing a verify. Ours were taking 45 minutes and was slowing down the server pretty drastically. By moving to another server on the private network, we only incur the 15 second penalty instead of the 45 minute one. Not only does this run great, but test restores I have done to another server are incredibly fast. It takes longer to install the OS and Exchange than it does to restore the database! There was no data loss and logs rolled forward. -----Original Message----- From: netapp netappliance [mailto:netapp@mail.be] Sent: Friday, October 19, 2001 8:43 AM To: toasters(a)mathworks.com Subject: Good experience with Netapp & exchange I'm looking for good experience of migrating exchange to netapp ? ----------------------------------------------------- Mail.be, Free WebMail and Virtual Office http://www.mail.be

1 0

Good experience with Netapp & exchange
by netapp netappliance 19 Oct '01

19 Oct '01

I'm looking for good experience of migrating exchange to netapp ? ----------------------------------------------------- Mail.be, Free WebMail and Virtual Office http://www.mail.be

1 0

"unrecognized error 0xb" -- correct slot for tape scsi?
by Toal, Dave 19 Oct '01

19 Oct '01

Folks, I've been trying to get an F740 filer to recognize a dlt for several weeks. The error it returns is below. This same error also happens on another filer, also a 740. DLT checks out ok, according to the StorageTek tech's dignostics box. Have tried swapping cables, and using different dlt's -- _always_ this "unrecognized error". The filer has been rebooted many times during this process. mt fsf, bsf, weof, &c all work ok, according to mt status, but all tape writes fail. -- Dave Toal unix person T&T, nq, MA statler> dump u0f nrst0a /vol/spool DUMP: Dumping tape file 1 on nrst0a DUMP: creating "/vol/spool/../snapshot_for_backup.0" snapshot. DUMP: Using Full Volume Dump DUMP: Date of this level 0 dump: Fri Oct 19 02:02:52 2001. DUMP: Date of last level 0 dump: the epoch. DUMP: Dumping /vol/spool/ to nrst0a DUMP: mapping (Pass I)[regular files] DUMP: mapping (Pass II)[directories] Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0.0):cmdblk 0xfffffc0000e020f8 op 0xa block 64512 aborted command (b 47, 0) DUMP: Tape write failed. Fri Oct 19 02:03:10 GMT [isp_main]: Tape (1.0) unrecognized error 0xbunrecognized error 0xb. DUMP: DUMP IS ABORTED DUMP: Deleting "/vol/spool/../snapshot_for_backup.0" snapshot. statler>

1 0

RE: which disk
by Mike Sphar 18 Oct '01

18 Oct '01

Well, at the very least you can just run in degraded mode while you get the correct disk. I would expect you could simply plug the other disk in. If it's the wrong one, the netapp should just ignore it, I would think. Then you just go about ordering a correct one. Or, the whole filer might go up in a big puff of smoke. Try it and let us know! (This is one reason why I prefer to always keep at least one spare available on all my filers. I prefer to let it grab a spare on its own, then I just have to show up at my convenience to swap in the replacement for the bad one.) -- Mike Sphar - Sr Systems Administrator - Engineering Support Peregrine Systems, Inc. -----Original Message----- From: Jim Harm [mailto:jharm@llnl.gov] Sent: Thursday, October 18, 2001 3:12 PM To: toasters(a)mathworks.com Subject: Re: which disk I did not make myself clear. the disks are in the shelves and I am going to fail one that is noisy with errors and remaps of sectors. I know which disk it is. I don't know if my spare, in my hand(SHZHB-ZZ), can replace the one in the shelf(ST15230N). I'd like to know before I fail the disk. Can I plug in a SHZHB-ZZ to replace a failed ST15230N? I can't event tell if a SHZHB-ZZ is a scsi or a 4 GB disk! We haven't had to replace a disk on this unit for over three years! All my production systems that I work on now are 760s and 840s. At 2:33 PM -0700 10/18/01, Chris Lamb wrote: > > >> How do I correlate the identification of the disk on the >> weekly report with the label on the disk? > > The report says 4 GB disk ST15230N and one of my disks says SHZHB-ZZ. >> Nowhere on the disk is there a designation of size, scsi or ultra, >> or even if it is scsi. > >Yow! That is old. :-) An F330, perhaps? What version of ONTAP are you >running? > >From the part number, that drive is a Seagate fast/narrow SCSI drive. >Have you looked at the front of the machine? Even on the old StorageWorks >SCSI shelves the red LED should light to indicate a failed drive... but >it's been a long, long time since I ran one of those. > >Good luck, > >-- Chris > -- }}}===============>> LLNL James E. Harm (Jim); jharm(a)llnl.gov System Administrator Compaq Clusters (925) 422-4018 Page: 423-7705x57152

2 1

Re: which disk
by Jim Harm 18 Oct '01

18 Oct '01

I did not make myself clear. the disks are in the shelves and I am going to fail one that is noisy with errors and remaps of sectors. I know which disk it is. I don't know if my spare, in my hand(SHZHB-ZZ), can replace the one in the shelf(ST15230N). I'd like to know before I fail the disk. Can I plug in a SHZHB-ZZ to replace a failed ST15230N? I can't event tell if a SHZHB-ZZ is a scsi or a 4 GB disk! We haven't had to replace a disk on this unit for over three years! All my production systems that I work on now are 760s and 840s. At 2:33 PM -0700 10/18/01, Chris Lamb wrote: > > >> How do I correlate the identification of the disk on the >> weekly report with the label on the disk? > > The report says 4 GB disk ST15230N and one of my disks says SHZHB-ZZ. >> Nowhere on the disk is there a designation of size, scsi or ultra, >> or even if it is scsi. > >Yow! That is old. :-) An F330, perhaps? What version of ONTAP are you >running? > >From the part number, that drive is a Seagate fast/narrow SCSI drive. >Have you looked at the front of the machine? Even on the old StorageWorks >SCSI shelves the red LED should light to indicate a failed drive... but >it's been a long, long time since I ran one of those. > >Good luck, > >-- Chris > -- }}}===============>> LLNL James E. Harm (Jim); jharm(a)llnl.gov System Administrator Compaq Clusters (925) 422-4018 Page: 423-7705x57152

1 0

which disk
by Jim Harm 18 Oct '01

18 Oct '01

I have a filer that is old and still used for testbeds. The disk failed and we have spares, but; How do I correlate the identification of the disk on the weekly report with the label on the disk? The report says 4 GB disk ST15230N and one of my disks says SHZHB-ZZ. Nowhere on the disk is there a designation of size, scsi or ultra, or even if it is scsi. It is from NetApp, but the only label from netapp on it is the test sticker. -- }}}===============>> LLNL James E. Harm (Jim); jharm(a)llnl.gov System Administrator Compaq Clusters (925) 422-4018 Page: 423-7705x57152

1 0

Re: ONTAP with RedHat linux
by Jered Heeschen 18 Oct '01

18 Oct '01

It's nice to hear I'm not the only one who's run into the hang with the 2.4 kernel, though it sounds like we get it more consistently. I've seen the same issue on a RedHat 6.2 box that's updated to the 2.4 kernel, which is why I'd point to something in the kernel rather than something RedHat-specfic. The best workaround seems to be using TCP to mount the NFS shares - that should allow for better performance than limiting readand write sizes to 1023. To do that, add "tcp" to the mount options, either in /etc/fstab or using the -o flag for "mount". You'd also need to turn on the nfs.tcp.enable option on the filer. Jered Steve Losen <scl(a)sasha.acc.virginia.edu>@mathworks.com on 10/18/2001 10:25:54 AM Sent by: owner-toasters(a)mathworks.com To: toasters(a)mathworks.com cc: Subject: Re: ONTAP with RedHat linux I am running RedHat 7.1 and NFS mounting a netapp F820 running 6.0.1R3. Things work pretty smoothly, but I have experienced the same problem as another poster (sorry, lost the message) where NFS writes occasionally delay and a "NFS server not responding" error is logged. I have not tried the rsize=1023,wsize=1023 work around. I have experienced the same problem with NFS servers other than Netapp, including a IBM RS6000 running AIX. Non Linux NFS clients are having no delay problems with the Netapp filers, so I'm pretty sure it is on the Linux end. For awhile I thought the NIC on my Linux box had botched the speed/duplex negotiation with the ethernet switch. Our network folks can tell me what speed the switch port has negotiated, but I don't know how to check my NIC from Linux. The network folks tell me they see no errors on my switch port when I experience NFS delays. I don't seem to have any other network problems, so I doubt this is the problem. I have been able to duplicate the problem on a second Linux box. However, on a third box, essentially identical to mine and also running RH 7.1, I could not duplicate it. A couple of things to be aware of with RedHat Linux and NFS. Prior to RedHat 7.0, only NFS v2 was supported. Furthermore, Linux only supported 16 bit uids and gids. We have a lot of files on our Netapp filers with uids greater than 65535. RedHat 7.1 supports NFS v3 and 32 bit uids and gids. 32 bit uids are critical in our environment. I administer our filers and when I was running RH 6.2, I could not get accurate file owner information with "ls" and I could not "chown" files to uids over 65535, so I had to use another unix box for filer administration. Now I can do it all from my Linux box. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

1 0

RE: disk_fw_update
by Geoff Hardin 18 Oct '01

18 Oct '01

Thanks for the responses everyone! Jeff Sloan wrote: Yes there is definitely spin up issues with some of the old firmware on the 18G FCAL disks. Upgrading the firmware to the newest releases is the right move. Doing it individually is a very safe method up updating them, and definitely desirable, as you've had a few disk fail on you. I would like to note this is just on the older firmware revisions on the 18G drives. (hence once you finish upgrading you won't have to worry about this repeating itself). In regard to your current situation, The solution is to reboot the node that is reporting the mailbox disk error. We have a workaround that allows you to avoid rebooting, but it's only for ONTAP 6.1X and above. Did you halt the second system when upgrading the firmware? There's a specific process to upgrading the disk firmware on a cluster pair. You can review that process here: http://now.netapp.com/NOW/knowledge/docs/ontap/rel601r3/html/sag/fw_up5.htm… Cheers! :-) Jeff > -----Original Message----- > From: Geoff Hardin [mailto:geoff.hardin@dalsemi.com] > Sent: Thursday, October 18, 2001 1:40 PM > To: Sloan, Jeff > Subject: Re: disk_fw_update > > > Jeff, > The cluster is running DOT NetApp Release 5.3.4R2. We > are updating the firmware in anticipation of upgrading to > DOT 6.1.1R1. We have had problems with some of our filers > with the old 18GB disks during the upgrade; during the last > upgrade, we lost 3 disks, fortunately in 3 separate RAID > groups. Needless to say, it made for a very long, very > tense night as the disks rebuilt. We were hoping to update > the firmware of each disk separately so that we could avoid > this problem. > > Geoff Hardin > geoff.hardin(a)dalsemi.com > Politicians and diapers need changing often for similar reasons.

1 0

disk_fw_update
by Geoff Hardin 18 Oct '01

18 Oct '01

filer1> cf status filer1 has detected a mailbox disk error, takeover of filer2 disabled I have just finished upgrading the disk firmware on filer2. I had turned off clustering per the disk_fw_upgrade instructions prior to upgrading the disks. Once I had finished, I tried to turn clustering back on on filer1 and received the error message above. Any idea what's going on? filer2 does not report any errors on cf status. Thanks for the help! Geoff Hardin Dallas Semiconductor MIS UNIX geoff.hardin(a)dalsemi.com Politicians and diapers need changing often for similar reasons.

2 1

RE: quotas file
by Honeycutt, Michael 18 Oct '01

18 Oct '01

Thats how I do it also. For instance, if you want to use a scheduled task to do a quota off/on instead of resize, you could say: This would be first cmd file- rsh filername -l username:password -n quota off volumename call c:\foldername\filename.cmd This would be second cmd file- rsh filername -l username:password -n quota on volumename -----Original Message----- From: Jordan Share [mailto:iso9@phantasticant.com] Sent: Thursday, October 18, 2001 2:23 PM To: Grey, Michael; toasters(a)mathworks.com Subject: RE: quotas file Well, I can't help you with most of your questions, but I can tell you how I rsh from win2k to my filer. In my hosts.equiv file, I have a line like this: w.x.y.z Administrator Where w.x.y.z is the IP of the machine I am rsh'ing from. Then I use commands like this: rsh FILERNAME -l root:ROOTPASSWORD command_for_filer This works for me. Jordan -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com]On Behalf Of Grey, Michael Sent: Wednesday, October 17, 2001 8:12 PM To: 'toasters(a)mathworks.com' Subject: quotas file Well I have figured out how to set quotas based on global groups in Windows NT, but I'm having a little problem with the quotas file once completed. My script checks to see if a user is a member of a global group for a quota alocation (200MB, 350MB, and 500MB) via the "Global" command. This script runs automatically when a change is made to a quota global group. If the user ID is not in any global group then they would receive the default quota. The users who are members of a global group for quotas are written to a scratch file in the format of the quotas file. Once the script is complete the quotas file is deleted and then this scratch file is renamed to the quotas file. Everything works excellent but quota changes are not applied until I perform a "quota resize" command. I need to know if the filer automatically recalculates the quotas based on this file and if so, under what conditions? or, is there any way to have the filer recalculate quotas based on the quota file other then via the "quota resize" command. I'm trying to do this from a batch script under NT. I'm not sure how to RSH to the box via a script from NT if at all possible. Any help would be appreciated. Thanks.

1 0

RE: quotas file
by Berry, Grant 18 Oct '01

18 Oct '01

Hi Michael. Sounds like you have quotas set up well. RSH from an NT client is pretty easy to set up and then make a batch file for. This is what I do... 1) Just type in "rsh filername command" eg: rsh toronto1 df from a dos prompt of the machine that you wish to schedule this from. At the filer console you'll get an rsh error similar to: toronto1> Thu Oct 18 07:34:26 EDT [rshd_0]: Permission denied to rsh request fro m gberry at 99.118.225.53 2) Using that info for an example go and edit your <filerroot>/etc/host.equiv file with wordpad and add a line that contains "99.118.225.53 gberry" and make sure you hit <enter> at the end of the line, save the file. Then try "rsh toronto1 df" again to test and it should work just fine. A .bat file to do this would simply contain the command(s) you wish to execute. You can also use the "-l <username>" option on the rsh command if that's handy. Just type rsh at a dos prompt and it'll give you the syntax. I hope this helps. Regards, Grant -----Original Message----- From: Grey, Michael [mailto:Michael.Grey@ttc.ca] Sent: Wednesday, October 17, 2001 11:12 PM To: 'toasters(a)mathworks.com' Subject: quotas file Well I have figured out how to set quotas based on global groups in Windows NT, but I'm having a little problem with the quotas file once completed. My script checks to see if a user is a member of a global group for a quota alocation (200MB, 350MB, and 500MB) via the "Global" command. This script runs automatically when a change is made to a quota global group. If the user ID is not in any global group then they would receive the default quota. The users who are members of a global group for quotas are written to a scratch file in the format of the quotas file. Once the script is complete the quotas file is deleted and then this scratch file is renamed to the quotas file. Everything works excellent but quota changes are not applied until I perform a "quota resize" command. I need to know if the filer automatically recalculates the quotas based on this file and if so, under what conditions? or, is there any way to have the filer recalculate quotas based on the quota file other then via the "quota resize" command. I'm trying to do this from a batch script under NT. I'm not sure how to RSH to the box via a script from NT if at all possible. Any help would be appreciated. Thanks.

2 1

quotas file
by Grey, Michael 18 Oct '01

18 Oct '01

Well I have figured out how to set quotas based on global groups in Windows NT, but I'm having a little problem with the quotas file once completed. My script checks to see if a user is a member of a global group for a quota alocation (200MB, 350MB, and 500MB) via the "Global" command. This script runs automatically when a change is made to a quota global group. If the user ID is not in any global group then they would receive the default quota. The users who are members of a global group for quotas are written to a scratch file in the format of the quotas file. Once the script is complete the quotas file is deleted and then this scratch file is renamed to the quotas file. Everything works excellent but quota changes are not applied until I perform a "quota resize" command. I need to know if the filer automatically recalculates the quotas based on this file and if so, under what conditions? or, is there any way to have the filer recalculate quotas based on the quota file other then via the "quota resize" command. I'm trying to do this from a batch script under NT. I'm not sure how to RSH to the box via a script from NT if at all possible. Any help would be appreciated. Thanks.

2 1

Ndmpcopy or vol copy (data migration)?
by Dawn Lovell 18 Oct '01

18 Oct '01

I know this very issue has been discussed previously, but I'm seeking some clarification. We have a 210 running 5.3.6R2 that we're replacing with an 820 running 6.1.1R1. The filers both have 100mb/full-duplex connections on the same subnet. Our initial plan was to vol copy the single 36GB volume on the 210 to a new volume on the 820. We've used vol copy to move roughly the same amount of data from a 210 to a 740 in the past, although both were running the same DOT version. After reading the archived discussion on the filesystem reversion necessary when migrating between 5.3.6R2 and 6.0.1R1, I opened a case with NetApp to ask about the time involved for reversion and if the filesystem would be upgraded after the vol copy completed. The support engineer pointed out that there are possible data safety issues with doing a vol copy from the older hardware/OS to the newer and strongly suggested avoiding vol copy and using ndmpcopy instead. I guess I'm just seeking some additional opinions, as vol copy has worked so well for us in the past. We can certainly use ndmpcopy with some variation of level0/incremental (or rsync), but I'm concerned the move will end up taking longer that way than if we just schedule several hours of downtime and vol copy once. I don't want to do something unsupported, but my impression (from the archived discussion) was that vol copy should work after the target filesystem was reverted. Is vol copy actually unsupported by NetApp in this scenario? Has anyone done this and had problems? Thanks very much for your time! Dawn Lovell dlovell(a)centurytel.net

1 0

RE: root volume
by Lane, Debbie 18 Oct '01

18 Oct '01

This list is great. I wanted to thank everyone for their replies. I was also impressed with NetApp Tech Support. They saw my question on the list server and gave me a call. Best Regards, --Debbie

1 0

RE: NetApp and EMC Comparisons
by Joe Luchtenberg 18 Oct '01

18 Oct '01

1. The article, while making some valid points about the industry in general with regards to FC SAN and TCP/IP NAS, misses a lot of significant points about Network Appliance. Furthermore, in making generalized statements about the NAS market (most platforms of which are tuned Win2K Advanced Server devices or some-flavor-of-Linux), these would mis-characterize filers if applied to them. When comparing NetApp filers to competing SANs the important comparisons to make are between WAFL and NTFS/xFS. For instance, when addressing the scalability requirements for large enterprises, The Clipper Group states, "[NAS] will likely require, over the long run, much more IT staff involvement than [SAN]," the argument being that it takes more resources to manage many small (their characterization) filers than fewer behemoth SANs. I think most on this list would refute that point for many reasons. 2. Without understanding the requirement you seek to address, it's hard to make pertinent comparisons between EMC's IP4700 and NetApp filers (I assume this is the comparison you're making, not Celerra vs NetApp). However, some general points to consider: - if you're doing anything other than home directories and general purpose file sharing, you should consider the level of application support for the two platforms (I believe you will find NetApp is more likely to have certified support on their filers, although in researching this I was surprised to find EMC had certified Oracle on IP4700; nonetheless, from my point of view EMC will want you to do anything other than home directories and file sharing on a Sym). - IP4700 RAID5 / NetApp RAID4 -- inherent dynamic RAID set expansion advantages to NetApp - IP4700 RAID set sizes are restricted to 5- or 10-disk multiples -- less user configurable - no competing offering to NetApp's SnapMirror from EMC for the IP4700 platform 3. Getting back to your specific question about admin... Generally speaking, EMC supports their own products. This support is surely world-class, but it also carries a world-class price tag. As an administrator you won't be adding storage capacity, loading patches or performing other typical tasks -- they will (unless you get and maintain expensive certification training). In today's bloody market (EMC lost over $1B last quarter) vendors are doing everything they can to move product. Getting demos should be easy from both (now that manufacturing has had time to catch up with the response to Sept 11 -- for a while all demos and stock from a number of h/w vendors were redirected to NYC and DC for disaster response). Get 'em both in your lab and try 'em out for yourself. Let us know what you find. Just my $.02. Joe > -----Original Message----- > From: Mark Johnson-Barbier [mailto:mjb@mj3.org] > Sent: Wednesday, October 17, 2001 1:02 PM > To: Toasters (E-mail) > Subject: Re: NetApp and EMC Comparisons > > > This is a good write-up about NAS vs. SAN in general. I got > the link from > EMC, but the recommendations seems to favor NetApp for the needs of my > company. > > http://www.clipper.com/bulletins/sanvnasfinal.pdf > > > > ----- Original Message ----- > From: "Killion, Brent (ZB7217)" <Brent.Killion(a)pinnaclewest.com> > To: "Toasters (E-mail)" <toasters(a)mathworks.com> > Sent: Wednesday, October 17, 2001 8:12 AM > Subject: NetApp and EMC Comparisons > > > > Fellow Filer Admins- > > > > Can anyone point me to any white papers comparing the EMC > NAS products > with > > Network Appliance NAS solutions? Specifically, I'm looking > for comparisons > > of ease of use and ease of administration. > > > > Thanks. > > > > >

1 0

RE: remove
by Braunschweiger, Udo 18 Oct '01

18 Oct '01

please send a mail to majordomo(a)mathworks.com <mailto:majordomo@mathworks.com> with the only word in the message body unsubscribe toasters that's all! -----Original Message----- From: Morgan, Joshua [mailto:JMorgan@Trivergent.com] Sent: Donnerstag, 18. Oktober 2001 17:02 To: toasters(a)mathworks.com Subject: remove remove Joshua Morgan PH: (864) 331-7939 jmorgan(a)trivergent.com

1 0

Write permissions on CIFS share
by Ian F. Jarvis 18 Oct '01

18 Oct '01

NetApp gurus, I have a scenario where I am unable to gain write access to a CIFS share on our Filer for a local Filer account. I can map a drive, read and execute with no problems but cannot write to the share. Due to our security policy, our Windows NT boxes and Filer are in workgroup and not in a domain. The Filer is being used as a store of log data from servers and not for any 'user' data. PlainTextPasswords is enabled on the Windows NT machines. The user account in question has been added locally to the Filer and the share has a mixed security style. The share has 'everyone' access with full control. I have attempted to map the user account to pcuser and even root in usermap.cfg with no luck. I am able to write when mapping the drive as root. Although the user account shows up with the useradmin userlist command, it is not showing in /etc/passwd. I'm not sure if this is an issue or not. Hopefully there is something simple I am missing here. Data OnTap version: 6.0.1R3 Licenses: CIFS, NFS Thanks in advance!! Ian Jarvis NOC Systems Engineer Aether Systems Inc. 443-394-5029 <<...OLE_Obj...>>

1 0

remove
by Morgan, Joshua 18 Oct '01

18 Oct '01

remove Joshua Morgan PH: (864) 331-7939 jmorgan(a)trivergent.com

1 0

Re: ONTAP with RedHat linux
by Steve Losen 18 Oct '01

18 Oct '01

I am running RedHat 7.1 and NFS mounting a netapp F820 running 6.0.1R3. Things work pretty smoothly, but I have experienced the same problem as another poster (sorry, lost the message) where NFS writes occasionally delay and a "NFS server not responding" error is logged. I have not tried the rsize=1023,wsize=1023 work around. I have experienced the same problem with NFS servers other than Netapp, including a IBM RS6000 running AIX. Non Linux NFS clients are having no delay problems with the Netapp filers, so I'm pretty sure it is on the Linux end. For awhile I thought the NIC on my Linux box had botched the speed/duplex negotiation with the ethernet switch. Our network folks can tell me what speed the switch port has negotiated, but I don't know how to check my NIC from Linux. The network folks tell me they see no errors on my switch port when I experience NFS delays. I don't seem to have any other network problems, so I doubt this is the problem. I have been able to duplicate the problem on a second Linux box. However, on a third box, essentially identical to mine and also running RH 7.1, I could not duplicate it. A couple of things to be aware of with RedHat Linux and NFS. Prior to RedHat 7.0, only NFS v2 was supported. Furthermore, Linux only supported 16 bit uids and gids. We have a lot of files on our Netapp filers with uids greater than 65535. RedHat 7.1 supports NFS v3 and 32 bit uids and gids. 32 bit uids are critical in our environment. I administer our filers and when I was running RH 6.2, I could not get accurate file owner information with "ls" and I could not "chown" files to uids over 65535, so I had to use another unix box for filer administration. Now I can do it all from my Linux box. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

1 0

ONTAP with RedHat linux
by Kunihiko Motoyoshi 18 Oct '01

18 Oct '01

Hello, Dose anyone had experience about filer with RedHat 7.1 or later ? I know RedHad 6.x working with ONTAP. Please let me know, If you had experience, What ONTAP version you use ? Thank you, -Motoyoshi -- Kunihiko Motoyoshi Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 Storage Group / Product Support Dept. CTC Technology

5 5

NIS groups not showing up
by Roman.Ustoyev＠chase.com 17 Oct '01

17 Oct '01

Hi Lance, Did you find a solution to this problem? We are running 6.1R1 and have the same issue. As of today there is no fix for this, the only workaround is to have the groups locally on the filer, but that defeats the whole purpose for NIS. The problem has to do with the way YP stores its maps using dbm format (I think NIS+ in yp compatibility mode emulates dbm for yp clients). As far as I know there is a limitation on a single entry in dbm file which can not exceed 1024. It would be nice if filers could read NIS+, but I don't think this will happen. Can anyone else comment on that? Roman. >Thanks to all for your help. As it turns out the problem is if a group line >on your NIS+ server exceeds 1024 chars the filer will stop processing the NIS >entry once it sees that line. So all groups after that are non-existant! > >I understand this is fixed in 6.0 but don't know for sure. If not there should >atleast be a warning in the log file that says you may have exceeded the 1024 >char limit in a particular NIS map. > >Hi Lance, > > When the group cache is created, if there are duplicate entries, a message will >be logged. Are there any such messages logged? > >Thanks, >-Devi > > > >-----Original Message----- >From: Lance R. Mehle [mailto:mehlel001@hawaii.rr.com] >Sent: Saturday, October 14, 2000 3:13 PM >To: Toasters (E-mail) >Subject: NIS groups not showing up > > >Hi all, > >I have a problem that I was wondering if any of you have seen. > >We have a little over 2000 groups in our NIS+ environment. When I check the >nis_cache file on the filer about 399 are missing. A ypgroup also shows the >group(s) missing from the filer although a ypmatch can find the group(s). >It also appears that the same groups are effected all the time. > >The groups are fine on the UNIX side. > >Help! > >Lance

1 0

Re: ONTAP with RedHat linux
by Jered Heeschen 17 Oct '01

17 Oct '01

Ugh, my bad - That should have read less than a kilobyte. Sorry about that. That would be mount options like rsize=1023,wsize=1023. Jered Frank Smith <fsmith(a)hoovers.com> on 10/17/2001 03:40:57 PM To: Jered Heeschen/Raleigh/Contr/IBM@IBMUS cc: "toasters(a)mathworks.com" <toasters(a)mathworks.com> Subject: Re: ONTAP with RedHat linux How do you read/write less than a byte? Frank --On Wednesday, October 17, 2001 15:14:58 -0400 Jered Heeschen <heeschen(a)us.ibm.com> wrote: > I've had users with RedHat 6.2 through 7.1 connecting to our filers, > running various versions of ONTAP 6.x. The only strangeness we've run into > seems more related to our network - machines running the Linux kernel 2.4.x > tend to hang on NFS writes when using UDP and a packet size greater than a > byte. It started around the time CodeRed starting making the rounds, and > since I haven't been able to talk to whoever's in charge of the larger > network here, we've just worked around it - I assume they're filtering some > types of UDP traffic, since around that time we had trouble serving NFS > from some Linux boxes that hadn't given us trouble previously. > > I'm not sure what kernel 2.4 does differently from 2.2 when making NFS > connections, but the workaround has been either to use TCP instead of the > default UDP when mounting NFS shares, or to set the rsize and wsize to less > than a byte. > > Jered > > > > Kunihiko Motoyoshi <k_moto(a)ctc-g.co.jp>@mathworks.com on 10/17/2001 > 09:06:16 AM > > Sent by: owner-toasters(a)mathworks.com > > > To: "toasters(a)mathworks.com" <toasters(a)mathworks.com> > cc: chinatsu(a)ctc-g.co.jp, ue(a)ctc-g.co.jp, "Syouichi.Nakayama" > <syou(a)ctc-g.co.jp> > Subject: ONTAP with RedHat linux > > > > Hello, > > Dose anyone had experience about filer with RedHat 7.1 or later ? > I know RedHad 6.x working with ONTAP. > > Please let me know, > If you had experience, What ONTAP version you use ? > > Thank you, > -Motoyoshi > -- > Kunihiko Motoyoshi > Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 > Storage Group / Product Support Dept. > CTC Technology > -- Frank Smith fsmith(a)hoovers.com Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501

1 0

Re: ONTAP with RedHat linux
by Jered Heeschen 17 Oct '01

17 Oct '01

I've had users with RedHat 6.2 through 7.1 connecting to our filers, running various versions of ONTAP 6.x. The only strangeness we've run into seems more related to our network - machines running the Linux kernel 2.4.x tend to hang on NFS writes when using UDP and a packet size greater than a byte. It started around the time CodeRed starting making the rounds, and since I haven't been able to talk to whoever's in charge of the larger network here, we've just worked around it - I assume they're filtering some types of UDP traffic, since around that time we had trouble serving NFS from some Linux boxes that hadn't given us trouble previously. I'm not sure what kernel 2.4 does differently from 2.2 when making NFS connections, but the workaround has been either to use TCP instead of the default UDP when mounting NFS shares, or to set the rsize and wsize to less than a byte. Jered Kunihiko Motoyoshi <k_moto(a)ctc-g.co.jp>@mathworks.com on 10/17/2001 09:06:16 AM Sent by: owner-toasters(a)mathworks.com To: "toasters(a)mathworks.com" <toasters(a)mathworks.com> cc: chinatsu(a)ctc-g.co.jp, ue(a)ctc-g.co.jp, "Syouichi.Nakayama" <syou(a)ctc-g.co.jp> Subject: ONTAP with RedHat linux Hello, Dose anyone had experience about filer with RedHat 7.1 or later ? I know RedHad 6.x working with ONTAP. Please let me know, If you had experience, What ONTAP version you use ? Thank you, -Motoyoshi -- Kunihiko Motoyoshi Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 Storage Group / Product Support Dept. CTC Technology

2 1

ontap 6.1x
by neil lehrer 17 Oct '01

17 Oct '01

hi, my management is very interested in doing quotas for our nt users. that requires 6.1x. does anyone have any comments on the 6.1x releases? we are nfs,cifs,nis,nt 4,atm,clustered 760's. thanks. --

5 6

RE: root volume
by White, Lance 17 Oct '01

17 Oct '01

Good point...then don't use vol copy, but instead just the /etc dir across the mount. I returned with a "create a new volume" because Debbie wanted to REDUCE her existing volume (something that we know we can't do, so creation of a new one is the best way). If an existing 2 disk volume was already in your system, then go for that instead, as Michael explains. Lance -----Original Message----- From: Honeycutt, Michael [mailto:MichaelHoneycutt@NC.SLR.com] Sent: Wednesday, October 17, 2001 8:46 AM To: 'White, Lance'; 'Lane, Debbie'; toasters(a)mathworks.com Subject: RE: root volume You dont need spares to do it. You can copy the /etc directory to another volume and set it as root. Thats what I did to remove 2 drives from vol0. -----Original Message----- From: White, Lance [mailto:Lance.White@netapp.com] Sent: Wednesday, October 17, 2001 11:12 AM To: 'Lane, Debbie'; toasters(a)mathworks.com Subject: RE: root volume Assuming you still have a couple of spares... 1. Create your new root volume on the new drives (let's call it vol1 for this article) 2. Issue the offline command on vol1 3. If running OnTap 5.3.6R2 or lower, reboot the Filer. If running OnTap 6.0 or greater, carry on... 4. Delete the data that you no longer want on vol0 5. Initiate the vol copy command (vol copy start vol0 vol1) 6. Now, make vol1 the root volume (vol options vol1 root) 7. Reboot the Filer to boot from vol1 8. Rename vol0 to mydata (vol rename vol0 mydata) 9. Rename vol1 to vol0 (vol rename vol1 vol0) 10. Reboot 1 last time so all shares & exports get mounted/exported properly 11. Offline mydata, and if running OnTap 6.0 or higher, destroy mydata to put mydata disks back to spare state -----Original Message----- From: Lane, Debbie [mailto:Debbie.Lane@intermec.com] Sent: Wednesday, October 17, 2001 7:59 AM To: toasters(a)mathworks.com Subject: root volume Our filers vol0 contains user data. We are going to be getting rid of about 80GB of this data. We then want to take some of the disk out of vol0 and put them in another volume. What is the best way to go about this? I have limited filer experience. Thanks for your help. --Debbie

2 1

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