toasters

toasters@lists.teaparty.net

13531 discussions

Strange folders cropping up
by Jay Newton (Email) 28 Mar '03

28 Mar '03

I keep getting these folders on one of my CIFS volumes. I don't think the Filer is responsible but I'm having trouble finding the cause. Below is an example of a folder name. There is sometimes a symbols folder underneath the main folder but not in every case. There are no files under the folder at all. 69fe9e1137e5bed8e0a0ba9782268d5e Does anyone else recognize this or know what causes it? Jay Newton Systems Engineer Chesapeake Energy Corporation Natural Gas - Natural Advantages Building 6112, Room 114 (405)848-8000 ext. 683 jnewton(a)chkenergy.com

2 1

rescan of a scsi dlt?
by Toal, Dave 28 Mar '03

28 Mar '03

A while ago, someone posted a command to rescan an FC bus, I believe. I've got a dlt 7000 on an F740; the dlt is inside a storagetek 9710 which was recently ipl'd. The dlt stops working when this happens, I'm not sure why (veritas netbackup shows it as 'down'). Rebooting the netapp fixes it; is there a way to reset the adapter on the dlt without doing that? statler*> fcadmin rescan 1 fcadmin rescan: Channel 1 is not a FC loop channel. statler*> sysconfig -v NetApp Release 6.1.3R2: Mon Jun 17 01:40:16 PDT 2002 slot 1: SCSI Host Adapter 1 (Qlogic ISP 1040B) Fast/Wide, Differential Firmware Version 4.66.00 Clock Rate 60MHz. 0: Tape: Quantum DLT7000 276A -- this is not a .sig

2 1

Anyone using f700 and f800 series filers with Cisco 6509's?
by kyle 28 Mar '03

28 Mar '03

I recently just ran into an issue where I see "Out-Discard" errors on my switch on some of my gigabit ports the filers are on(sh port mac mod/port). Has anyone else run into this problem? On the netapps which are plugged into ports which show no issue, I can not find any difference in configuration - either on the netapp or switch. So, I want to know two things: 1. If you are using a f700 and/or a f800 filer on a Cisco Cat6509 switch with gigabit ports(WS-X6416-GBIC) and you are not showing any In or Out-Discard errors, do you mind sending me your config on the port to compare with my own? 2. I know there is an issue due to the buffer size on the port on cat6500 series, but since this problem doesnt exist on all of my switches, has anyone experienced this problem, and if so, what did you do to correct it? Thanks, K.

2 1

RE: Security on Win2k
by Nail, Larry 28 Mar '03

28 Mar '03

Bill, Not sure where you're going here? File shares are controlled by the ACL's of the Share & the File ACL's. This is the excact same way an NT/W2K file server controls access. If the Share is set to read only, the access to the share & the files in it are limited to read only. Even if the file level ACL's are set to full control, the access is still read only. Think "most restrictive". Regards, Larry -----Original Message----- From: Bill Bello [mailto:Bill.Bello@hds.com] Sent: Thursday, March 27, 2003 6:46 PM To: toasters(a)mathworks.com All, A question has come up in our lab on the subject. If 'read only' is set on the filer for a CIFS share, a user can still have full rights to that share IF security is NOT set in Win2k as well. Has anyone figured a way to make the share secure from the filer only? Thanks in advance. Regards, Bill Bello ATC PreSales Open Systems Support Westchester Office (914) 773-9131 New York Office (212) 827-1314

1 0

RE: Security on Win2k
by Mike Sphar 28 Mar '03

28 Mar '03

This doesn't sound correct to me. Have you actually tested it? In windows network permissions, share permissions are applied first, then individual file or directory ACLs are applied, and the most restrictive permissions always apply. So if a share is read-only to a user, then even if all the files in that share are writeable by everyone, then that user should not be able to update those files or create any new files or directories in that share. I would be very surprised to find that Netapp was not emulating the standard windows file server behavior in this case. -- Mike Sphar - Sr Systems Administrator - Remedy, a BMC Software Company -----Original Message----- From: Bill Bello [mailto:Bill.Bello@hds.com] Sent: Thursday, March 27, 2003 6:46 PM To: toasters(a)mathworks.com Subject: Security on Win2k All, A question has come up in our lab on the subject. If 'read only' is set on the filer for a CIFS share, a user can still have full rights to that share IF security is NOT set in Win2k as well. Has anyone figured a way to make the share secure from the filer only? Thanks in advance. Regards, Bill Bello ATC PreSales Open Systems Support Westchester Office (914) 773-9131 New York Office (212) 827-1314

1 0

Security on Win2k
by Bill Bello 28 Mar '03

28 Mar '03

All, A question has come up in our lab on the subject. If 'read only' is set on the filer for a CIFS share, a user can still have full rights to that share IF security is NOT set in Win2k as well. Has anyone figured a way to make the share secure from the filer only? Thanks in advance. Regards, Bill Bello ATC PreSales Open Systems Support Westchester Office (914) 773-9131 New York Office (212) 827-1314

1 0

snapshots
by George Kahler 27 Mar '03

27 Mar '03

HI, I was wondering if there is a performance issue of letting the snapshot reserve (the size of the current snapshot area) roll into the regular data area of the volume, ie. snapshot capacity be at > 100 % ? All things aside, does the filer perform any less under this condition ? Thanks. George ------------------------------------------------------------------------------- George Kahler e-mail: george(a)yorku.ca Sr. Systems Administrator humans: (416) 736-2100 x.22699 Computing and Network Services machines: (416) 736-5830 Ontario, Canada, M3J-1P3

2 1

RE: maxdir size on ontap 6.2 and higher
by Sam Schorr 27 Mar '03

27 Mar '03

I have found this bug at the NOW site: 69823 Here is the text. There is a workaround documented and it is fixed in 6.3 and up: Before OnTAP release 6.2, wafl.maxdirsize was a filer-wide option that could legally take on values larger than 64 MB (65,536 x 1,024 bytes). OnTAP 6.2 changes wafl.maxdirsize in two important ways. First, it obsoletes the single, filer-wide option and replaces it individual maxdirsize settings for each volume. Second, it allows maxdirsize to be set no higher than 64 MB. In filers that had set wafl.maxdirsize to a value greater than 65,536 (64 MB), an upgrade to OnTAP 6.2 sets the new per-volume maxdirsize value to its default, 10,240 (10 MB). The upgrade output does not highlight this change to the system administrator. Given that wafl.maxdirsize had been previously set to a much larger value, there is a good probability that the upgrade will produce a nontrivial number of directories that are now larger than the volume's new (relatively small) maxdirsize setting. Although all such directories can still be loaded into memory and handle lookups, they have been rendered "ungrowable". Workaround Formatted Before upgrading any filer whose wafl.maxdirsize is larger than 64 MB, examine its volumes to locate all "large" (over 10 MB) directories. If any such large directories exist, please reset wafl.maxdirsize on the filer to an appropriate value (that is still smaller than the new 64 MB limit) BEFORE the upgrade. This way, the upgrade to OnTAP 6.2 will propagate this more reasonable value to each volume. If any existing directories are LARGER than 64 MB, try to reduce their size below 64 MB. Since directories never shrink in OnTAP, you may be able to recreate these very large ones and thus get rid of a significant amount of wasted space. If, despite these efforts, you still have directories that are larger than 64 MB, then they will be "ungrowable" after the upgrade. If you have already upgraded one or more filers to OnTAP 6.2 whose wafl.maxdir option had been set to more than 64 MB, you should check them for any large directories that are now past the new 10 MB default per-volume maxdirsize setting. Use the "vol options" command to raise maxdirsize to a value large enough to make those directories growable again (as long as they are still below the new 64 MB maximum). Notes Formatted Network Appliance is working on a change to the maxdirsize portion of the OnTAP 6.2 upgrade that sets a more reasonable value in these circumstances. In cases where the filer-wide wafl.maxdirsize setting is found to be larger than 64 MB, the upgrade will choose a maxdirsize of 64 MB (instead of 10 MB). This guarantees that all existing directories that are still smaller than the new 64 MB limit are still growable, and minimizes user "surprise". The upgrade code will also print out a message describing the change in maxdirsize (and its implications) to administrators. Related Solutions Version Found Data ONTAP: 6.1.3R1 Likely Exists Data ONTAP: 6.1.3R1 through 6.2.2 Fixed-In Version Data ONTAP 6.3 (First Fixed) - Fixed Data ONTAP 6.3.1R1 (GA) - Fixed Data ONTAP 6.3.2(FCS) - Fixed Data ONTAP 6.4R1(FCS) - Fixed -----Original Message----- From: Reinoud Reynders [mailto:Reinoud.Reynders@uz.kuleuven.ac.be] Sent: Wednesday, March 26, 2003 12:41 AM To: kyle; toasters(a)mathworks.com Subject: Re: maxdir size on ontap 6.2 and higher Hi Kyle, This is indeed a problem, and on this moment, there is no workaround. I have the same problem. We have done some migration from 1 directory to multi directories. Netapp is working on this issue, but for the details, you must contact your local netapp guys. Best regards, Reinoud ----- Original Message ----- From: "kyle" <kyle(a)sportsline.com> To: <toasters(a)mathworks.com> Sent: Tuesday, March 25, 2003 8:14 PM Subject: maxdir size on ontap 6.2 and higher > Seems there is a limit of 64k. This is keeping me from upgrading. I > currently use 6.1R1 and just tried upgrading one of my lab netapps and > see I cant go higher than 64k for maxdir size. Is there some workaround? > >

1 0

Re: Virus Scanning
by Seth Moskowitz 26 Mar '03

26 Mar '03

In my environment there are thousands of windows machines and although they have virus software there are always some cracks so I take the position that if you afford to do it and there is enough windows data to merit it then you should have virus protection on the Filers. My company already has Symantec NAV internally throughout the oganization as well as Mcaffee products on all the firewalls and e-mail servers. Given that Norton was here and they were the first to come out with a working product for the Filers I looked at it. It worked ok and has gotten better in time. 2 years ago I fully deployed Carrier Scan 2.0 which is now SAVSE 4.x. There have been some issues but during migrations from older Novell/NT servers to the Filers I have caught and cleaned 100's of viruses, especially from Novell servers. In the case of one migration from a merging companies server we caught 1400 viruses in one migration. Granted that isn't the norm but it happens. The set up I have built is basically that each filer has a dedicated 1GB network connection for Admin. Admin in this case includes snap mirror and virus scanning. Each Filer also has 2 virus scanning serves dedicated to it each with a 1GB network connection. Moving forward with the newer symantec version I will be pooling all of these scanning servers to basically create a scanning farm. I should mention this solution might be overkill for some but on our home server filers we have 3000+ clients each. We do not have scanning on our NFS only Filers but have over 50TB of data that is being scanned. Lastly since we already have a Symantec platform I leveraged that environment using the LiveUpdate features of Symantec so my virus definitions are automatically updated as our virus people stress test new definitions and roll them out to our LiveUpdate server(s). >From: Geoff Hardin <geoff.hardin(a)dalsemi.com> >To: toasters(a)mathworks.com >Subject: Virus Scanning >Date: Tue, 25 Mar 2003 11:44:53 -0600 > > I was wondering what other admins were using for virus scanning. And as >an aside, I really want to know whether it is worth the time and money. >Basically, I've been asked to evaluate the virus scanning software out >there for the filers, but I'm not really sure it's even necessary. > I am a UNIX admin, so I typically don't see the viruses that plague my >NT compatriots, but I don't believe we've really had a problem on our >filers with CIFS shares. But maybe I'm just biased, so that's why I'm >asking for your input. > >1. Which A/V software do you use > a) McAfee NetShield for Netapp > b) Symantec Antivirus for Netapp > c) Trend Micro Server Protect > d) other (are there any others?) > >2. Is it really necessary? Please explain your answer. > > >Thanks for any and all input. > >Geoff Hardin >UNIX System Administrator >geoff.hardin(a)dalsemi.com >This space is for rent in order to increase company revenue. > _________________________________________________________________ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail

1 0

maxdir size on ontap 6.2 and higher
by kyle 26 Mar '03

26 Mar '03

Seems there is a limit of 64k. This is keeping me from upgrading. I currently use 6.1R1 and just tried upgrading one of my lab netapps and see I cant go higher than 64k for maxdir size. Is there some workaround?

2 1

Jump to page:

2026

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