toasters

toasters@lists.teaparty.net

13515 discussions

quotas over limit: determination thereof
by David Lee 20 Jul '02

20 Jul '02

If what follows is in the manual or is a FAQ, then just point me in the direction... Executive summary: Is there an easy way (variant of "quota report" perhaps?) to discover which users are over-quota? Detail: We are beginning to migrate our home directories (15K-20K of them) from Solaris to NetApp. Quotas are a vital part of the control of these directories. Under Solaris (trad. UNIX), each user has an explicit quota. While this is possible under NetApp, it seems far more sensible to use default quotas where possible (and the documentation encourages this). We have set up some reasonable default quotas, and are using rsync (thanks, folk!) to get the user files prepared in the future NetApp location: transferred (from 20+ volumes across three Solaris fileservers) and kept in sync. Naturally a few of our users have more data than our NetApp default quotas. What we simply want to do is identify these exceptions so we can apply explicit quotas. We will, if possible, adjust the defaults so that the number of exceptions, from our 20K user-base, is reasonably small. Under Solaris etc., the output from its "repquota" command was easily eyeball-able (I know, no such word!) for such exceptions: "+" and expiry times. Is there a variant of NetApp's "quota report" that either restricts output to over-quota users, or has a field indicating over-quota, or similar? Or is the NetApp convention simply to cobble together a bit of awk/perl to extract those lines (from the total 20K) in which "Used" exceeds "Limit"? Thanks in advance. -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 374 2882 U.K. :

2 1

RE: arp spoof, 840 with 6.2.1
by Toal, Dave 19 Jul '02

19 Jul '02

Brian, Snapmirror and vol copy turned out not to be an option, because the 760 is at 5.3.1; we're getting the 'volume is in transitional state, aborting' error even though the destination is offline. NDMP copy looks like the remaining method, the 760 is being upgraded to 6.2.1 and I want to duplicate the data before starting that. Piotr, Yes, disks and data too. %-{)# What I saw from the first attempt was no response to ping, on either side, even after doing ifconfig down/up of the e9b nic. Maybe the magic arp has leaked out the switch I was using? After connecting the original filer I had to do arp -d and ping again, before it would respond to the unix host mount request. -----Original Message----- From: Brian Long To: Toal, Dave Cc: 'toasters(a)mathworks.com' Sent: 7/19/02 10:37 AM Subject: Re: arp spoof, 840 with 6.2.1 Dave, Are you replicating the data to the F840 or just moving shelves? If you're replicating data with something like Snapmirror, you might consider the Ontap 6.X snapmirror migrate command. This alters the disk labels on the destination so you don't end up with stale NFS filehandles on all the clients (if you're using NFS). For CIFS, you don't need to worry about this. /Brian/ > Good morning. I've got a question about substituting > one netapp for another, by setting the ip addresses the same > and changing the ethernet cable going to the switch from one > to the other. > > The netapp I'm trying to bring online is the 840. The > ether (mac) addresses are showing different from inconfig, and > I'm wondering if there's a way to set that explicitly; I don't > see it from the options listed. > > > > the 840: > > netapp-demo*> ifconfig e9b > e9b: flags=48043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 > inet 206.33.27.85 netmask 0xffffffc0 broadcast 206.33.27.127 > ether 00:20:fc:1e:3a:75 (100tx-fd-down) > netapp-demo*> > > > > > > the other netapp, a 760 running 5.3.6R1: > > wesson> ifconfig e0 > e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500 > inet 206.33.27.85 netmask 0xffffffc0 broadcast 206.33.27.127 > partner inet 206.33.27.86 (not in use) > ether 00:a0:98:00:78:c5 (100tx-fd-up) > wesson> > > > > > > -- > Dave Toal > Thomson & Thomson > North Quincy, MA > > > -- Brian Long | | | Americas IT Hosting Sys Admin | .|||. .|||. Phone: (919) 392-7363 | ..:|||||||:...:|||||||:.. Pager: (888) 651-2015 | C i s c o S y s t e m s

2 1

arp spoof, 840 with 6.2.1
by Toal, Dave 19 Jul '02

19 Jul '02

All, Good morning. I've got a question about substituting one netapp for another, by setting the ip addresses the same and changing the ethernet cable going to the switch from one to the other. The netapp I'm trying to bring online is the 840. The ether (mac) addresses are showing different from inconfig, and I'm wondering if there's a way to set that explicitly; I don't see it from the options listed. the 840: netapp-demo*> ifconfig e9b e9b: flags=48043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 206.33.27.85 netmask 0xffffffc0 broadcast 206.33.27.127 ether 00:20:fc:1e:3a:75 (100tx-fd-down) netapp-demo*> the other netapp, a 760 running 5.3.6R1: wesson> ifconfig e0 e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500 inet 206.33.27.85 netmask 0xffffffc0 broadcast 206.33.27.127 partner inet 206.33.27.86 (not in use) ether 00:a0:98:00:78:c5 (100tx-fd-up) wesson> -- Dave Toal Thomson & Thomson North Quincy, MA

3 2

RE: NT Domain Authentication and Filer Access
by Chuck Tomasi 18 Jul '02

18 Jul '02

It sounds like there is an inconsistency between the UNIX login name and the Windows domain\login name for that user. If they are the same, then odds are that the user and the filer aren't in the same domain. The joys of multi-protocol environments. Some of us learned this the hard way... There are two ways to approach this. The first is to do your best to keep the UNIX login name (e.g. ctomasi) the same as the domain login (TGI\CTomasi). Note, case doesn't matter - most of the time. If, however, the filer is in another domain (assuming full NT trusts are setup between the domains) you'll need to start tweaking the /etc/usermap.cfg file on the filer. This is a handy file. Often times it is used to map "Domain\Administrator" to "root" so you get all your admin priviledges from either world. It can also be used for other things (see the docs and/or the comments in the file.) In our case, we have lots of domains which we will hopefully be consolidating in to fewer with Win2K Active Directory, but that's beside the point. We use an entry *\* == * in the usermap.cfg file to help the filer look in other domains to authenticate the user. In my case, the filer is part of the Win2K domain "NA", but I'm "TGI\CTomasi" and my UNIX account is "ctomasi". That entry starts a search for various PDCs (see CIFS PREFDC for some other helpful info.) Note, this could take a while to authenticate a user if you have to search a bunch of domains. The user may perceive this delay when they open a connection to a CIFS share for the first time on that filer. The filer is just trying to match the Windows name (credentials) with a corresponding UNIX account. You may need to help it along if you're dealing with multiple domains or if the login name doesn't correspond between Windows and UNIX. I hope that helps. --Chuck -----Original Message----- From: Jessica Fernandez To: toasters(a)mathworks.com Sent: 7/18/2002 12:21 PM Subject: NT Domain Authentication and Filer Access I am new to administering a filer via NT. Our filers have always been administered from a UNIX host. We are migrating users from a UNIX environment to an Windows NT/2000 environment. I have a user that has a domain account and needs access to the filer. Without having to create an account on the UNIX, where do I indicate validation via NT domain? I have a people share on my filer with a folder with his employee number as the folder name. After logging into the domain, he can see the filer listed in the domain. When he double clicks it, it prompts him for a username and password. He has tried what he uses to authenticate on the domain and it does not work. For our UNIX users they have accounts on our UNIX server and are authenticated that way. Your help is appreciated. Thanks. JESSICA A. S. FERNANDEZ ESA-FM-ESH E-mail: jessicaf(a)lanl.gov TA-16-661-101, MS-C933 Voice: 505-665-8051 FAX: 505-665-9490 Pager: 104-6707

1 0

NT Domain Authentication and Filer Access
by Jessica Fernandez 18 Jul '02

18 Jul '02

I am new to administering a filer via NT. Our filers have always been administered from a UNIX host. We are migrating users from a UNIX environment to an Windows NT/2000 environment. I have a user that has a domain account and needs access to the filer. Without having to create an account on the UNIX, where do I indicate validation via NT domain? I have a people share on my filer with a folder with his employee number as the folder name. After logging into the domain, he can see the filer listed in the domain. When he double clicks it, it prompts him for a username and password. He has tried what he uses to authenticate on the domain and it does not work. For our UNIX users they have accounts on our UNIX server and are authenticated that way. Your help is appreciated. Thanks. JESSICA A. S. FERNANDEZ ESA-FM-ESH E-mail: jessicaf(a)lanl.gov TA-16-661-101, MS-C933 Voice: 505-665-8051 FAX: 505-665-9490 Pager: 104-6707

1 0

18cent long distance conference calls
by Service Center 16 Jul '02

16 Jul '02

1 0

Re: Upgrade
by Bryan_West＠shamrockfoods.com 16 Jul '02

16 Jul '02

Sounds to me like your problem lies in the fact that your filer is not in a true Windows 2000 Mode. I believe that 6.1 adds full support for Windows 2000 Domains, but don't quote me on that. To solve you problem do the following: In your windows 2000 DNS server add a new alias or CNAME: MESIROWFINANCIA CNAME MESIROWFINANCIAL.NET This is for backwards compatibility for your old clients and servers. After the upgrade of the filer re-run CIFS SETUP Make sure you delete the computer account for the filer in your domain and have it re-created. Once completed you should be able to run CIFS DOMAININFO and get the following: DNS Domain Name: MESIROWFINANCIAL.NET Type: Windows 2000 You are also having a problem because your Domain name is longer than 15 Characters: http://support.microsoft.com/default.aspx?scid=kb;EN-US;q226144 Windows 9x machines and any other Netbios based systems will not be able to access it using the full name. Good luck. Bryan. |---------+-----------------------------> | | "Sayla, Mustafa" | | | <MSAYLA@mesirowfin| | | ancial.com> | | | Sent by: | | | owner-toasters@mat| | | hworks.com | | | | | | | | | 07/16/2002 10:36 | | | AM | | | | |---------+-----------------------------> >---------------------------------------------------------------------------------------------------------------| | | | To: "'toasters(a)mathworks.com'" <toasters(a)mathworks.com> | | cc: | | Subject: Upgrade | >---------------------------------------------------------------------------------------------------------------| Yesterday we tried to upgrade our F760 filer running 6.0.1r3 to 6.1.2r3. After the upgrade our NFS environment worked fine but cifs environment would not work. I can go to filer view and everything looked fine, I can see my shares, qtree and snapshots fine. All configurations as far as domain, DNS server, WINS and other networking is also fine. Yet when I try to access a share it will ask me for a login name and password. Same behavior when I try to access filer through network neighborhood even though I am logged in as administrator. We have a windows 2000 domain and a Windows NT 4.0 domain and there is a two way trust between them. Filer is in Windows 2000 domain and it was there even before the upgrade and been working fine. Talked to NetApp support and they made me try different things but could not be able to solve the issue. According to them they have never seen this kind of problem before. After the upgrade when it did not work I ran the cifs setup it gave me an error: "DNS does not appear to be configured correctly for proper windows 2000 operation in this domain. The filer could not resolve simple domain name 'MESIROWFINANCIA' to DNS form 'MESIROWFINANCIAL.NET' If I use a filer view setup wizard it would give me an error that domain name is illegal. What is confusing here is filer had been working fine for over two years in the same w2k domain with the same name without any problem. Netapp tech support had me run setup quite a few times and I also came across an error CIFS - Domain name not legal in the root volume language. After trying to fix this problem for 5 hours I finally decided to roll back so that filer is up and functioning. Once I rolled back to 6.0.1r3 cifs started to work but now NFS works fine, access from NT 4.0 domain works fine but if you are logged in to windows 2000 domain you cannot access the filer even though filer is also in windows 2000 domain. When you try to access it will give you an error "The account is not authorized to log in from this station". The case is still open with Netapp and we are trying different things but so far no luck. Any suggestion and help from you guys will be highly appreciated. Mustafa Sayla Sr. Network Administrator Mesirow Financial 312-595-6388

1 0

Upgrade
by Sayla, Mustafa 16 Jul '02

16 Jul '02

Yesterday we tried to upgrade our F760 filer running 6.0.1r3 to 6.1.2r3. After the upgrade our NFS environment worked fine but cifs environment would not work. I can go to filer view and everything looked fine, I can see my shares, qtree and snapshots fine. All configurations as far as domain, DNS server, WINS and other networking is also fine. Yet when I try to access a share it will ask me for a login name and password. Same behavior when I try to access filer through network neighborhood even though I am logged in as administrator. We have a windows 2000 domain and a Windows NT 4.0 domain and there is a two way trust between them. Filer is in Windows 2000 domain and it was there even before the upgrade and been working fine. Talked to NetApp support and they made me try different things but could not be able to solve the issue. According to them they have never seen this kind of problem before. After the upgrade when it did not work I ran the cifs setup it gave me an error: "DNS does not appear to be configured correctly for proper windows 2000 operation in this domain. The filer could not resolve simple domain name 'MESIROWFINANCIA' to DNS form 'MESIROWFINANCIAL.NET' If I use a filer view setup wizard it would give me an error that domain name is illegal. What is confusing here is filer had been working fine for over two years in the same w2k domain with the same name without any problem. Netapp tech support had me run setup quite a few times and I also came across an error CIFS - Domain name not legal in the root volume language. After trying to fix this problem for 5 hours I finally decided to roll back so that filer is up and functioning. Once I rolled back to 6.0.1r3 cifs started to work but now NFS works fine, access from NT 4.0 domain works fine but if you are logged in to windows 2000 domain you cannot access the filer even though filer is also in windows 2000 domain. When you try to access it will give you an error "The account is not authorized to log in from this station". The case is still open with Netapp and we are trying different things but so far no luck. Any suggestion and help from you guys will be highly appreciated. Mustafa Sayla Sr. Network Administrator Mesirow Financial 312-595-6388

1 0

rename across qtrees?
by David Lee 16 Jul '02

16 Jul '02

Executive summary of question: Is there a fast, efficient way to move a directory tree from one qtree to another? (Can a rename/mv simply relink across qtrees?) Detail: (We are new to NetApp, so this might be a FAQ: if so, just point me in the right direction.) We soon need to move the home directories of a few thousand users from a couple of Sun/Solaris NFS/Samba fileservers onto a NetApp. On the old Sun fileservers, these users are subgrouped using one scheme (into about 100 subgroups); on the new NetApp they'll be redistributed into about five qtrees. Ideally, we would simply pull them across the network (a long evening's work!) dumping them into one qtree on the NetApp. The second step would be to redistribute them into their new qtrees and, for us, conceptually straightforward because the homedirectory names can be pattern-matched into corresponding qtrees. In UNIX-speak, the equivalent of: mv qtree_tmp/<...>/dir_pattern_1 qtree_a mv qtree_tmp/<...>/dir_pattern_2 qtree_b (about five commands, one per qtree). In UNIX-land, a "mv" within a volume is a fast operation, simply relinking from one parent directory into another; whereas an "mv" across volumes is (of necessity, of course) a much larger data-copying operation. On the NetApp/WAFL is such a move across qtrees a simple relink or is it a data-copying operation? Is there a NetApp command to move/rename a directory-tree? If so, what? Not having found a NetApp command, I experimented with an "mv" from a UNIX box which had the volume NFS-mounted. But this took a long time so, I presume, was doing a data-copy, rather than relink. (Hope I explained that reasonably clearly!) -- : David Lee I.T. Service : : Systems Programmer Computer Centre : : University of Durham : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham : : Phone: +44 191 374 2882 U.K. :

3 3

filer CPU usage - resolution?
by Ambrose_Earle＠shamrockfoods.com 15 Jul '02

15 Jul '02

That was it. The DOS program was performing "search"es of hundreds of files in one directory. The problem became noticeable because the purge of the filers in that directory has been failing, allowing the files to accumulate. Again, the filers still have an issue handling search and the problem still occurs, but it is much less noticeable now that there are only a few dozen instead of a few hundred files involved.

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