toasters April 2003

toasters@lists.teaparty.net

95 participants
102 discussions

boot up error
by Bui, Marcus 17 Apr '03

17 Apr '03

Hi Toasters, I have a F820 (6.3.1R1) which get FC error every during boot up. But once the Filer is up, all volumes are available and can see all disks. Do 'sysconfig -c' and no errors. Try swapping the cable around but same error at boot up. Any ideas? Starting Press CTRL-C for floppy boot menu ispfc: Fibre Channel adapter 8b appears to be unattached/disconnected. If adapter is in use, check cabling and seating of LRC cards in disk shelves. Wed Apr 16 22:33:07 GMT [ispfc_init_2:error]: Initialization failed on Fibre Channel adapter 8b. ispfc: Fibre Channel adapter 7b appears to be unattached/disconnected. If adapter is in use, check cabling and seating of LRC cards in disk shelves. Wed Apr 16 22:33:07 GMT [ispfc_init_4:error]: Initialization failed on Fibre Channel adapter 7b. thanks, Marcus Bui

2 1

RE: tmp files
by Bui, Marcus 17 Apr '03

17 Apr '03

Steven, Are you using roaming profile with your MS client and saving the profile on the Filer? If so, check if temporary Internet files created by IE are being uploaded when the profiles are updated when clients logged off. C:\winnt\profiles\username\local settings\temp\........ compare this with profile stored on the Filer. cheers, Marcus -----Original Message----- From: Steven Boyer [mailto:sboyer1@tampabay.rr.com] Sent: Wednesday, April 16, 2003 9:20 AM To: toasters(a)mathworks.com Subject: tmp files I use a SRM product to manage our storage and have noticed an abundant amount of Microsoft temp files which start with ~. I know these are created as a backup 'till the file is saved but we have way to many.... any ideas. Thanks Steve

2 1

RE: Slow NFS filer performance on WAN connection vs Solaris NFS W AN c onnection
by Alan McLachlan 17 Apr '03

17 Apr '03

Mike, This is very interesting, particularly considering that on regular LAN connections NetApp filers blow away Sun boxes (on SpecSFS anyway). I half expect a "filers can't deal with being asked to run that slow" response from NetApp.... :o) Seriously though, OnTap does not use an NFS daemon. I believe NFS is handled in a state-machine fashion within the Ontap RTOS kernel. It's possible that what your seeing is the result of a timing condition that doesn't show up on faster links. Are you running NFS in sync or async mode on the client? regards, Alan McLachlan Senior Systems Engineer Storage Management Solutions ASI Solutions www.asi.com.au Ph +61 2 6230 1566 Fax +61 2 6230 5343 Mobile +61 428 655644 e-mail amclachlan(a)asi.com.au **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

Slow NFS filer performance on WAN connection vs Solaris NFS WAN c onnection
by Mike McBride 17 Apr '03

17 Apr '03

We have several engineers working from home using Solaris boxes and utilizing VPN's to the office. Typical application use is Cadence. What i have noticed is the NFS performance on the Filers are almost 50% slower than the performance of the Solaris machines. I have run several tests including cp, ftp and utilizing ping roundtrip times, traceroute, snoop and tcpdump to monitor activities between home SUN systems and file systems at work. I have also tested NFS using different transport protocols(tcp/udp) modifying rsize/wsize buffers and using NFS2 and NFS3 versions of NFS. The filers and the Solaris systems at cooperate are on the same subnet - there is no differences in the routing. FYI - the VPN's at home are all Linksys VPN cable/dsl routers configured for Site to Site VPN connections to corporate office. The problem is definitely with NFS and it is isolated to the Filers. I am confused why the performance of the NetApp NFS would be so poor compared with NFS on the Solaris systems. Now, I know NFS on a WAN is slow and VPN encryption is going to degrade the performance severely, but I am wondering why NetApp NFS performance is much worse than Solaris NFS performance. Basically, when accessing files on a Solaris system(local disk) at the corporate office from home i'm getting about 915KBits/sec. When accessing the same files on a NetApp(F740) at the corporate office from home i'm getting about 510KBits/sec. The transfer mechanism is NFS. When using FTP i get the same 915KBits/sec on the Solaris(local disk) and Filer. The load on the Filer at the time of testing is minimal. Anyone have any insight on this subject? Any feedback would be appreciated since I put quite a bit of time in this to try and understand the problem here. Thanks, Mike McBride Silicon Wave, Inc. (858) 404-5210 mcbride(a)siliconwave.com http://www.siliconwave.com

1 0

RE: boot up error
by Mohler, Jeff 17 Apr '03

17 Apr '03

Id you dont have anything plugged into the B ports on the FCAL cards in slots 7 and 8, you will see these errors, and they are normal. If there IS something plugged into those ports, and you see this error, you may have a configuration/hardware issue you need to contact support on. -----Original Message----- From: Bui, Marcus [mailto:Marcus.Bui@aiminvestments.com] Sent: Wednesday, April 16, 2003 4:11 PM To: 'toasters(a)mathworks.com' Subject: boot up error Hi Toasters, I have a F820 (6.3.1R1) which get FC error every during boot up. But once the Filer is up, all volumes are available and can see all disks. Do 'sysconfig -c' and no errors. Try swapping the cable around but same error at boot up. Any ideas? Starting Press CTRL-C for floppy boot menu ispfc: Fibre Channel adapter 8b appears to be unattached/disconnected. If adapter is in use, check cabling and seating of LRC cards in disk shelves. Wed Apr 16 22:33:07 GMT [ispfc_init_2:error]: Initialization failed on Fibre Channel adapter 8b. ispfc: Fibre Channel adapter 7b appears to be unattached/disconnected. If adapter is in use, check cabling and seating of LRC cards in disk shelves. Wed Apr 16 22:33:07 GMT [ispfc_init_4:error]: Initialization failed on Fibre Channel adapter 7b. thanks, Marcus Bui

1 0

RE: CIFS in Workgroup mode
by Muhlestein, Mark 17 Apr '03

17 Apr '03

You have to set the qtree security to mixed or ntfs to use ACLs. Yes, the local user approach is limited. I was just trying to clarify the statement that "no real security is available". Mark -----Original Message----- From: Alan McLachlan [mailto:amclachlan@asi.com.au] Sent: Wednesday, April 16, 2003 4:18 PM To: Muhlestein, Mark; Alan McLachlan; Robert Borowicz; toasters(a)mathworks.com Cc: Dane Knudson Subject: RE: CIFS in Workgroup mode Mark Muhlestein wrote: >Alan wrote: >> One problem is that in workgroup mode NTFS security isn't available. >> In fact, no real security is available... > This isn't quite right. If you are running with ONTAP 6.1.1 or later you > can create up to 96 local users in workgroup mode and use NTFS security > with NTLM authentication. Even without local users you can use > UNIX-style security if you are willing to use /etc/passwd accounts > (which unfortunately implies the use of plaintext passwords over the > wire during CIFS login). > However, it is true that for the very best available CIFS security > (which uses Kerberos authentication) you do have to have the filer > installed in a Win2k domain. Hi Mark, I just tried this on a lab filer here running 6.4.1R1 and in workgroup mode on an NT4.0 Workstation client (as still used by many of our government Novell customers - some are even still using Win98...) the mapped drive still shows up as FAT - no ACL's. I'll look into this further but I don't see how you're going to get ACL's on basic Windows peer-to-peer networking. Win2K local user account ACL's may work with WinXP workstations, but most customers using NetApp for home directories have hundreds or thousands of users. For only 96 or less users you're not going to buy a NetApp primarily for home dirs... (unless you have too much money to play with and believe in overkill, or they are VERY I/O intensive users, i.e. graphic artists, CAD etc :o) ) In any case, the issue here isn't whether you can use fun workarounds to implement some security - you could use hidden shares to obscure user's home dirs from each other but that's not the same as real permissions. And yes you can map to Unix accounts on the filer and use Unix security. But the real issue is how can this be administered from Novell eDirectory as a resource with managed security. Local accounts (whether Unix or post-Ontap 6.1.1 Win2K local accounts) on the filer don't help, the Novell eDirectory server somehow needs to be the primary account management server before most Novell admins will accept the solution. Personally, I wish we didn't have to deal with Novell environments but there are still too many around to ignore it. *sigh* Do you know what the status is WRT LDAP authentication in OnTap? Regards, Alan. **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

RE: CIFS in Workgroup mode
by Alan McLachlan 17 Apr '03

17 Apr '03

Mark Muhlestein wrote: >Alan wrote: >> One problem is that in workgroup mode NTFS security isn't available. >> In fact, no real security is available... > This isn't quite right. If you are running with ONTAP 6.1.1 or later you > can create up to 96 local users in workgroup mode and use NTFS security > with NTLM authentication. Even without local users you can use > UNIX-style security if you are willing to use /etc/passwd accounts > (which unfortunately implies the use of plaintext passwords over the > wire during CIFS login). > However, it is true that for the very best available CIFS security > (which uses Kerberos authentication) you do have to have the filer > installed in a Win2k domain. Hi Mark, I just tried this on a lab filer here running 6.4.1R1 and in workgroup mode on an NT4.0 Workstation client (as still used by many of our government Novell customers - some are even still using Win98...) the mapped drive still shows up as FAT - no ACL's. I'll look into this further but I don't see how you're going to get ACL's on basic Windows peer-to-peer networking. Win2K local user account ACL's may work with WinXP workstations, but most customers using NetApp for home directories have hundreds or thousands of users. For only 96 or less users you're not going to buy a NetApp primarily for home dirs... (unless you have too much money to play with and believe in overkill, or they are VERY I/O intensive users, i.e. graphic artists, CAD etc :o) ) In any case, the issue here isn't whether you can use fun workarounds to implement some security - you could use hidden shares to obscure user's home dirs from each other but that's not the same as real permissions. And yes you can map to Unix accounts on the filer and use Unix security. But the real issue is how can this be administered from Novell eDirectory as a resource with managed security. Local accounts (whether Unix or post-Ontap 6.1.1 Win2K local accounts) on the filer don't help, the Novell eDirectory server somehow needs to be the primary account management server before most Novell admins will accept the solution. Personally, I wish we didn't have to deal with Novell environments but there are still too many around to ignore it. *sigh* Do you know what the status is WRT LDAP authentication in OnTap? Regards, Alan. **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

1 0

Maximum capacity of a netapp
by Art Hebert 16 Apr '03

16 Apr '03

I am trying to find out what limits a netapp f760's maximum storage capacity. The f760 series used to have a max capacity of 1.5TB, but now docs state that its max capacity is now 3TB. What has caused this to change? OS improvements, cpu changes, etc. thanks art

3 2

Filer shelfs on Linux x86
by Ben Rockwood 16 Apr '03

16 Apr '03

Hello Toasters. I've done some testing recently with using NetApp shelfs (FC8/FC9) attached directly to a Linux box. It's worked very well, and I'm happy with the setup. There are some rough points, but the implimentation is pretty straight forward. I had started writting an article on how to do things end-to-end, but somehow half way thru just didn't see the point. Anyway, here are some interesting tidbits to wet the lips of anyone with shelfs sitting unused. Single FC8 shelf with 18G disks: [root@nexus /]# df -h Filesystem Size Used Avail Use% Mounted on /dev/evms/fc8_volume 118G 15M 118G 1% /filer_shelf [benr@nexus benr]$ bonnie++ -d /filer_shelf/ Version 1.03 ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP nexus.homeste 1256M 5604 81 19477 18 15546 17 6861 98 59964 37 677.7 5 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 998 7 +++++ +++ 376 2 422 5 +++++ +++ 401 3 And this is 2 FC9 shelfs with 36G disks: Filesystem Size Used Avail Use% Mounted on /dev/evms/fc9_vol 474G 60M 474G 1% /filer_shelf [benr@nexus benr]$ bonnie++ -d /filer_shelf/ Version 1.03 ------Sequential Output------ --Sequential Input- --Random- -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP nexus.homeste 1256M 5636 82 33744 33 23145 28 6306 93 60607 37 712.0 7 ------Sequential Create------ --------Random Create-------- -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 775 5 +++++ +++ 345 2 326 4 +++++ +++ 358 3 In both cases, the volumes that were build were striped across all avalible disks, using a stwidth of 16k. LVM was used under EVMS control to all volumes. As you can see from the benchmarks, the block read performance was excellent. For the tests I used my standard Linux workstation, a very slow Dell PIII 550Mhz with 512M RAM. JFS was used as the filesystem. The following are some notes for anyone who might wanna try this: a) DO NOT USE THE KERNELS QLOGIC DRIVER. It sucks! And don't think that you can just push the dev count to 255 and get past it, that only works for 3-4 devices. If you use a QLA2100 grab the QLA2200 driver from Qlogic.com, hack the makefile to build you a QLA2100.o module, the code is there but they don't advertise it. b) I tests all this with a custom 2.4.20 kernel, works great, added EVMS patches. c) EVMS rox, much more fun than LVM raw, but takes much longer to set things up due to the abstration layers added d) You'll have to wipe out the 2 partitions on the disk, which fdisk can't do. You'll need to dd over the first 1k to manually wipe the partitioning scheme. e) If your not already using DevFS I highly suggest it before piling shelfs on. If anyone wants more information or benchmarks, mail me directly and I can send my notes over. benr.

1 0

RE: Maximum capacity of a netapp
by Clarke, John L. (CIS) 16 Apr '03

16 Apr '03

The OS was changed to support 3TB. I do not recall exactly what rev, although I think it was at 6.0. FYI John -----Original Message----- From: Stefan Funke [mailto:bundy@arcor-ip.de] Sent: Wednesday, April 16, 2003 4:30 PM To: Art Hebert Cc: toasters(a)mathworks.com Subject: Re: Maximum capacity of a netapp Quoting message received from Art Hebert: > I am trying to find out what limits a netapp f760's maximum storage > capacity. The f760 series used to have a max capacity of 1.5TB, but > now docs state that its max capacity is now 3TB. What has caused this > to change? OS improvements, cpu changes, etc. 3TB in clustered mode I guess?!? -- Stefan Funke, eMail : bundy(a)arcor-ip.de TBD / Zentrale phone : ++49-(0)6196 587-775 Arcor AG & Co. fax : ++49-(0)6196 587-705 Otto-Volger-Strasse 19 PGP KeyID : 0x9BDCA694 65843 Sulzbach, Germany Web : http://www.arcor.de/

1 0

← Newer
1
2
3
4
5
6
7
8
...
11
Older →

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 April 2003