toasters

toasters@lists.teaparty.net

13514 discussions

RE: TCP v UDP performance
by Peter Bryant 14 Jun '02

14 Jun '02

*** Before acting on this e-mail or opening any attachment you are advised to read the disclaimer at the end of this e-mail *** Solaris 6, and we used Sun's own PCI Gigabit 2.0 card (as it's described on the invoice) Thanks for the tip though. I suspect the drivers are probably OK, install was only done a couple of months back and up to date versions used - unless you know a previous driver is better.... <g> Peter -----Original Message----- From: Jason S. Cash [mailto:cash@UDel.Edu] Sent: 12 June 2002 19:02 To: Peter Bryant Cc: 'toasters(a)mathworks.com' Subject: Re: TCP v UDP performance On Tue, 11 Jun 2002, Peter Bryant wrote: > Sometime ago I posted some performance tweaks for TCP performance, > which (when the filer was switched to TCP) worked a treat. I was > hoping to get the same for UDP. However... > > It seems that UDP on Sun over 1GB Ethernet and above is problematic. > Some details below (words and details have been changed to protect the > guilty!). As a result we're sticking to TCP for now. What version of solaris and what gig-e card? I would look for a new driver for the gigaswift adaptor that helps immensly w/ UDP NFS perf. Jason > > Peter > > ===================================================== > > I've done a bit of research and found out that testing of a very > similar setup to yours, by another customer, showed that there is a > performance bug in the NFS UDP implementation of Solaris. > > We all know that NFS over UDP is about 20% faster than NFS over TCP > however, the Solaris implementation of UDP breaks this rule when > gigabit Ethernet is involved..! It seems to be that when NFS is used > with UDP for internet, 10Mb and 100Mb connectivity then the rule > applies and also when you have a gigabit Ethernet connection under low > load then again all is fine. > > The performance problem appears when you try to load the gig > connection heavily - Solaris's UDP simply cannot perform at the > required rate. Now, thankfully, the TCP implementation in Solaris is > very good and is up to the job - hence, the situation you find whereby > NFS over TCP is much better than NFS over UDP. This matches exactly > with your findings where under normal database usage your Gig + > NFS/UDP connection is fine - but when you try to backup over the Gig > Ethernet link the load on the network goes up and UDP can't perform. > You switched from UDP to TCP and the problem went away. > > My recommendation to you is to keep using NFS over TCP - the other > customer has decided to stay with TCP as it works well and they can't > see any benefit in moving back to UDP. > > > ******************************* Disclaimer > ***************************** > Confidentiality: This e-mail and any attachments are intended for the > addressee(s) only and may be confidential. If they have come to you in > error you must take no action based on them, nor must you copy or show > them to anyone; please reply to this e-mail and highlight the error. > > Viruses: Although we have taken steps to ensure that this e-mail and > attachments are free from any virus, we advise that in keeping with > good practice the recipient should ensure they are actually virus > free. > ********************** http://www.burallplastec.com ******************** > /* Jason S. Cash - Systems Programmer IT/Network and Systems Services University of Delaware, Newark Delaware e:cash@udel.edu v: 302-831-0461 */

2 1

Native LDAP authentication , when ?
by Frank Bonnet 13 Jun '02

13 Jun '02

Hi Few monthes ago I posted a request to know WHEN Ontap will support LDAP as an authetication method ( instead of NIS/YP ) ? I haven't received any infos from Netapp folks about this subject ... I mean LDAP and certainly NOT M$ Active Directory ! ( openldap prefered ! ) Any infos about this welcome ! Frank Bonnet

1 0

nfs.tcp.enable
by Geoff Hardin 12 Jun '02

12 Jun '02

Based on discussion generated by a post yesterday regarding Sun GbE performance and NetApp filers, I had a question about the nfs.tcp.enable option. I have heard that once you enable this, it is impossible to switch back to UDP; is this true? I don't really have any filers I can test this on, and I'd rather not find out that switching to TCP doesn't fix my problem but I can't go back to UDP. Thanks, Geoff Hardin geoff.hardin(a)dalsemi.com This space is for rent in order to increase company revenue.

2 1

TCP v UDP performance
by Peter Bryant 12 Jun '02

12 Jun '02

*** Before acting on this e-mail or opening any attachment you are advised to read the disclaimer at the end of this e-mail *** Sometime ago I posted some performance tweaks for TCP performance, which (when the filer was switched to TCP) worked a treat. I was hoping to get the same for UDP. However... It seems that UDP on Sun over 1GB Ethernet and above is problematic. Some details below (words and details have been changed to protect the guilty!). As a result we're sticking to TCP for now. Peter ===================================================== I've done a bit of research and found out that testing of a very similar setup to yours, by another customer, showed that there is a performance bug in the NFS UDP implementation of Solaris. We all know that NFS over UDP is about 20% faster than NFS over TCP however, the Solaris implementation of UDP breaks this rule when gigabit Ethernet is involved..! It seems to be that when NFS is used with UDP for internet, 10Mb and 100Mb connectivity then the rule applies and also when you have a gigabit Ethernet connection under low load then again all is fine. The performance problem appears when you try to load the gig connection heavily - Solaris's UDP simply cannot perform at the required rate. Now, thankfully, the TCP implementation in Solaris is very good and is up to the job - hence, the situation you find whereby NFS over TCP is much better than NFS over UDP. This matches exactly with your findings where under normal database usage your Gig + NFS/UDP connection is fine - but when you try to backup over the Gig Ethernet link the load on the network goes up and UDP can't perform. You switched from UDP to TCP and the problem went away. My recommendation to you is to keep using NFS over TCP - the other customer has decided to stay with TCP as it works well and they can't see any benefit in moving back to UDP. ******************************* Disclaimer ***************************** Confidentiality: This e-mail and any attachments are intended for the addressee(s) only and may be confidential. If they have come to you in error you must take no action based on them, nor must you copy or show them to anyone; please reply to this e-mail and highlight the error. Viruses: Although we have taken steps to ensure that this e-mail and attachments are free from any virus, we advise that in keeping with good practice the recipient should ensure they are actually virus free. ********************** http://www.burallplastec.com ********************

2 1

RE: Cannot delete .snapshot folder
by Maglinger, Paul 10 Jun '02

10 Jun '02

That seems to have done it. Thanks Kevin... -----Original Message----- From: kevin graham [mailto:kgraham@dotnetdotcom.org] Sent: Monday, June 10, 2002 15:52 To: Maglinger, Paul Cc: 'NetApps list server' Subject: Re: Cannot delete .snapshot folder > We have a .snapshot folder on one of our volumes that we cannot delete. We > used to run snapshots on this volume, but turned them off and deleted > snapshots contained within. vol options vol0 nosnapdir on ..kg..

1 0

Cannot delete .snapshot folder
by Maglinger, Paul 10 Jun '02

10 Jun '02

We have a .snapshot folder on one of our volumes that we cannot delete. We used to run snapshots on this volume, but turned them off and deleted snapshots contained within. Whenever we try to delete the folder from NT, we get a message, "Access is denied, the source file may be in use". We tried deleting it from a Unix host and get the same problem. What sparked this is that we have 3 directories that we are trying to mount to on the filer. 2 of them have no problem, but the third one gives us an "Access is denied". The only difference that I can see between the 2 that work and the 1 that doesn't is this .snapshot directory that I can't get rid of. Some insight, please? Remember, you are unique... just like everyone else! Paul Maglinger, A+, CA, CET, MCSE Systems Administrator Shoe Carnival Inc. (812)867-4674 pmaglinger(a)scvl.com

2 1

Backup Exec and incremental backup
by Uros Lampret 07 Jun '02

07 Jun '02

Hi! Does anybody know if it's possible to make incremental backups of snapshot dir. Every night there's nightly.0 snapshot created. I'd like to back it up to tape. I'd like to make weekly full backup and daily incrementals. But snapshot dir is read only. Is it possible to create incremental bacups in this way? Uros _____________________________

1 0

RE: Using Active Directory to set user home folder fails.
by Pero, Eric P (ETSD, IT) 06 Jun '02

06 Jun '02

I'm experiencing a problem accessing homedirs under Windows XP. I used to (about 3 days ago) access my homedir from the filer (ONTAP 6.1.3R1) using the CIFS OPTIONS HOMEDIR DOMAIN feature...I can access my homedir fine from Windows NT4/2K as \\filer\username, but not with Windows XP anymore. Has anyone experienced this problem? Thanks, Eric Pero _______________________________________ Technical Team Leader ETSD Intel Server Support The Hartford Eric.Pero(a)thehartford.com _______________________________________ -----Original Message----- From: Benny Wiström [mailto:benny.wistrom@proact.se] Sent: Thursday, June 06, 2002 3:39 AM To: 'toasters(a)mathworks.com' Subject: Using Active Directory to set user home folder fails. I have a customer who has upgraded to OnTap 6.2R2 and he has run into bug 42100 which is described as follows: Using Active Directory to set a user profile's home folder to map the user's CIFS home directory on a filer fails. When attempting to set the user home directory to \\filer\%username% AD puts up a MsgBox with the error message: The home folder could not be created because: The network name cannot be found. The reason AD does this is because it tries to verify that the home folder path exists. However, the CIFS home directory for a given user is only visible to that user. With the User Manager tool in NT4, setting the user's home folder path to a filer's CIFS home directory would cause a warning but User Manager did not prevent the operation as Active Directory does. The workaround described below doesn't work under version 6.2R2 of OnTap. It does work under version 6.1.2R1. Well the first workaround would work but that is not an option for my customer. He is about to migrate about 500 users so that would definately be to much work. Use this workaround: a) Create a share on the filer with the user's name. b) Set the user profile's home folder to the filer CIFS home directory. c) Delete the share with the user's name. Or use this 2 step procedure for Ontap 6.0 and above: a) Create the homedir folder of the user which is creating the user profiles. For example, if the filer homedir path is /home and AD is being run by Administrator then "mkdir \\filer\home\Administrator" b) When creating a user profile, instead of setting the home folder to \\filer\%username%, set the home folder path to \\filer\CIFS.HOMEDIR or to \\filer\~ Has anyone else come across this problem? If so, how did you fix it. _________________ Regards Benny This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return email and delete this communication and destroy all copies.

1 0

Using Active Directory to set user home folder fails.
by Benny Wiström 06 Jun '02

06 Jun '02

I have a customer who has upgraded to OnTap 6.2R2 and he has run into bug 42100 which is described as follows: Using Active Directory to set a user profile's home folder to map the user's CIFS home directory on a filer fails. When attempting to set the user home directory to \\filer\%username% AD puts up a MsgBox with the error message: The home folder could not be created because: The network name cannot be found. The reason AD does this is because it tries to verify that the home folder path exists. However, the CIFS home directory for a given user is only visible to that user. With the User Manager tool in NT4, setting the user's home folder path to a filer's CIFS home directory would cause a warning but User Manager did not prevent the operation as Active Directory does. The workaround described below doesn't work under version 6.2R2 of OnTap. It does work under version 6.1.2R1. Well the first workaround would work but that is not an option for my customer. He is about to migrate about 500 users so that would definately be to much work. Use this workaround: a) Create a share on the filer with the user's name. b) Set the user profile's home folder to the filer CIFS home directory. c) Delete the share with the user's name. Or use this 2 step procedure for Ontap 6.0 and above: a) Create the homedir folder of the user which is creating the user profiles. For example, if the filer homedir path is /home and AD is being run by Administrator then "mkdir \\filer\home\Administrator" b) When creating a user profile, instead of setting the home folder to \\filer\%username%, set the home folder path to \\filer\CIFS.HOMEDIR or to \\filer\~ Has anyone else come across this problem? If so, how did you fix it. _________________ Regards Benny

1 0

Anyone have a raw (Unix mailbox) copy of the List Archive?
by David L Kindred (Dave) 05 Jun '02

05 Jun '02

Does anyone have a copy of the List Archive in a raw (preferably Unix mailbox) format? I'd like to have a local copy to facilitate searching by myself and co-workers, and to keep the search burden off our gracious host's desktop. The HTML version is nice for browsing, but harder to manipulate with other tools. Thanks. -- David L. Kindred <mailto:d.kindred@telesciences.com> Unix Systems & Network Administrator Telesciences, Inc. <http://www.telesciences.com> Support: <http://support.telesciences.com> 2000 Midlantic Drive, Suite 410, Mt. Laurel, NJ 08054 Tel: +1.856.866.1000 ext. 4184 Fax: +1.856.866.0185 Cel: +1.609.413.6205 Pgr: +1.800.689.5182 SMS: <mailto:davidlkindred@vtext.com> ---

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