toasters

toasters@lists.teaparty.net

1 participants
13523 discussions

questions on quotas and drive mapping
by neil lehrer 12 Oct '01

12 Oct '01

hi, using ontap 6.01r3d3, nfs, cifs, nt4 domain and nis. 1. our qtrees are now unix style. my quotas file looks like: /vol/vol0/users tree - - /vol/vol0/shared tree - - * user@/vol/vol0/users - - * user@/vol/vol0/shared - - * group@/vol/vol0/shared - - my question is when we convert from unix to ntfs qtree what will be affected? will quotas still work, will we still have to maintain dual entries in nt and nis? any other gotchas? 2. if i do this(file1 is the dns name for the filer, users is a share): C:\WINNT>net use * \\file1\users Drive J: is now connected to \\file1\users. it works fine i do this: C:\WINNT>net use * \\file1\c$ password /user:domain\nlehrer and get System error 53 has occurred. i am substituting in the pw and domain name. will the net use command work when mapping the hidden admin share? thanks. -- regards

1 0

RE: ontap 6.x
by Fox, Adam 12 Oct '01

12 Oct '01

Just checked on toasters and for an F740, the "Recommened Release" or "General Availability Release" as it is not called has been 6.0.1R3 for quite a while. The "First Customer Shipped" (previously called "Early Access") releases are 6.0.3, 6.1R1, and 6.1.1R2. Just FYI -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Chris Thompson [mailto:cet1@cus.cam.ac.uk] > Sent: Tuesday, March 06, 2001 5:30 PM > To: listsarch-toasters(a)enteract.com > Cc: toasters(a)mathworks.com > Subject: Re: ontap 6.x > > > nlehrer(a)ibb.gov (neil lehrer) writes > > > > is it time to adopt 6.x? > > Of couse, that's an impossible question to answer in vacuo. > > My feeling is that for those who usually run Early Access releases, > 6.0 is increasingly looking like the place to be. We are planning to > upgrade the F740 we use as the primary filestore for our (somewhat > grandiloquently named) Central Unix Service from 5.3.7R1 to 6.0.1R3 > at the end of next week, when the university term ends. I want the > fast snapshots, but apart from that I want to be on the track where > bugs are fixed fastest, and that's clearly 6.0 now. > > On the other hand, the two F740's used by our mail systems have much > more stereotyped usage patterns. They are currently at 5.3.6R2 (which > is, after all, still the "Recommended Release") and it seems unlikely > they will be upgraded before the summer, at the earliest. If > you aren't > pushing the edge of the envelope, in one way or another, there's no > enormously compelling reason to move yet. > > Chris Thompson University of Cambridge > Computing Service, > Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, > Phone: +44 1223 334715 United Kingdom. >

1 0

RE: ontap 6.x
by Mike Sphar 12 Oct '01

12 Oct '01

Where is it stated that 5.3.6R2 is the "Recommended Release"? The NOW site lists "Data ONTAP 6.0.1R3" as the "General Availability Release" for me. -- Mike Sphar - Sr Systems Administrator - Engineering Support Peregrine Systems, Inc. -----Original Message----- From: Chris Thompson [mailto:cet1@cus.cam.ac.uk] Sent: Tuesday, March 06, 2001 2:30 PM To: listsarch-toasters(a)enteract.com Cc: toasters(a)mathworks.com Subject: Re: ontap 6.x nlehrer(a)ibb.gov (neil lehrer) writes > > is it time to adopt 6.x? Of couse, that's an impossible question to answer in vacuo. My feeling is that for those who usually run Early Access releases, 6.0 is increasingly looking like the place to be. We are planning to upgrade the F740 we use as the primary filestore for our (somewhat grandiloquently named) Central Unix Service from 5.3.7R1 to 6.0.1R3 at the end of next week, when the university term ends. I want the fast snapshots, but apart from that I want to be on the track where bugs are fixed fastest, and that's clearly 6.0 now. On the other hand, the two F740's used by our mail systems have much more stereotyped usage patterns. They are currently at 5.3.6R2 (which is, after all, still the "Recommended Release") and it seems unlikely they will be upgraded before the summer, at the earliest. If you aren't pushing the edge of the envelope, in one way or another, there's no enormously compelling reason to move yet. Chris Thompson University of Cambridge Computing Service, Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QG, Phone: +44 1223 334715 United Kingdom.

1 0

bah - apologies for old msgs getting popped back to the list
by ryan beasley 12 Oct '01

12 Oct '01

I goofed while piping an existing archive through a local mail2news gw and it appears that some of my header modifications didn't take effect. More specifically, it looks like I forgot to take care of the Cc: fields. :P I'm totally sorry for passing old stuff back to the list. - ryan

1 0

cifs file creation date issue
by neil lehrer 12 Oct '01

12 Oct '01

hi, i used find . -depth -print | cpio -pdm /target-directory to copy files from sun box to filer. if i look at the the file creation dates on the filer from an nfs mount they look okay, the same as on the source. but if i look at the creation dates from a cifs connection using dir /tc ~~~~~~~~~~~ C:\WINNT>dir /?|more Displays a list of files and subdirectories in a directory. DIR [drive:][path][filename] [/P] [/W] [/D] [/A[[:]attributes]] [/O[[:]sortorder]] [/T[[:]timefield]] [/S] [/B] [/L] [/N] [/X] [/C] /T Controls which time field displayed or used for sorting timefield C Creation A Last Access W Last Written ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ and some other utils the creation date on the files is the date i cp'd the files over. the files are in a unix style qtree and i am running ontap 6.01r3d3. any ideas? i would really like the creation dates to be correct for all access methods. -- regards +++++++++++++++++++++++++++++++++++++++++++++++++ + Neil Lehrer + + United States International Broadcasting Bureau + System Development Division + + voice 202 619-2524 + fax 202 619-3576 + nlehrer(a)ibb.gov + + " is this crisis an opportunity or just + another grab the fire extinguisher moment?" + +++++++++++++++++++++++++++++++++++++++++++++++++

1 0

"quota report" for tree quotas only?
by Brian Tao 11 Oct '01

11 Oct '01

Any plans to include a switch to "quota report" to display only tree-type quotas? I don't see anything obvious in the manual to do this. I have a couple of filers that take can take half an hour to do a complete "quota report" when they're busy, 99.9% of the time looking up and displaying derived user quotas. I have a script that generates HTML quota reports which runs from a central admin host. I'd prefer to run it without requiring a config file listing quota trees, or kludge together some way to see which quota trees are defined (maybe use rdfile? ick...), send multiple rsh commands, collate the results, etc. I've got the data massaging working with the output of a single "quota report ; df ; df -i". It would be nice to keep that. :) -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

4 9

RE: Disconnect serial console
by Fox, Adam 11 Oct '01

11 Oct '01

I've never seen any problems with pulling and re-attchting console ports. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Walsh, Warren (MN65) [mailto:warren.walsh@honeywell.com] > Sent: Wednesday, October 10, 2001 10:41 AM > To: toasters(a)mathworks.com > Subject: Disconnect serial console > > > Hi all - > > I need to move the serial console on my 530 and 740 filers. > Basically, the > console ports on the filers go to a pair of Wyse terminals. > We need to move > the Wyse terminals few feet, and that will require disconnecting and > rerouting the serial cables. I've never disconnected the > console while the > filer is up and running. Will this crash the filer, or cause > any problems? > I know that some Sun servers crash when the console is > disconnected, and I'd > like to avoid that if at all possible. > > Thanks in advance for your help, > > -warren >

2 1

RE: F85
by Hubbard, Dan 10 Oct '01

10 Oct '01

We have an F85 and is has worked well for us. We just had an new SCSI card installed because of a recall and a tech. showed up on-site and made things painless. We use mostly NFS, but some CIFS. My only complaint would be that performance suffers when performing backups and restores with the single CPU. EMC touts that the processors run seperate processes for Management and processing. The F85 was 1/2 the price of the IP4700 and we had it setup in less than a 1/2 day. -----Original Message----- From: Barry Lustig [mailto:barry@lustig.com] Sent: Monday, April 30, 2001 10:44 AM To: Toasters Subject: F85 Has anybody had any experience with the F85? I'm most interested in the hardware. As a continuation of my last message, EMC is pushing hard with an IP4700 against an F85. They've been touting the reliability of their box and that it has no single point of failure (2 processors, etc). I'd like to know if anyone on the list has deployed the F85 and can give a reference on them. Also, does anyone know what type of failover the IP4700 is actually providing between their 2 storage processors. It doesn't look at first glance that the surviving processor takes over the MAC address of the dead processor. It just starts arping for the IP address of its partner. barry

1 0

RE: Disconnect serial console
by Mike Sphar 10 Oct '01

10 Oct '01

I've never had a problem with this on my F230 or F740s. I don't believe NetApp uses the break signal as a trigger to drop to Prom mode (which is the problem the Suns have). I used to have one ASCII terminal between my three filers that I freely swapped around as needed. For the record, the Suns don't crash, they just drop to the prom mode (ok prompt). I don't think I've ever encountered a case where simply entering "go" didn't successfully return the sun machine to service. -- Mike Sphar - Sr Systems Administrator - Engineering Support Peregrine Systems, Inc. -----Original Message----- From: Walsh, Warren (MN65) [mailto:warren.walsh@honeywell.com] Sent: Wednesday, October 10, 2001 7:41 AM To: toasters(a)mathworks.com Subject: Disconnect serial console Hi all - I need to move the serial console on my 530 and 740 filers. Basically, the console ports on the filers go to a pair of Wyse terminals. We need to move the Wyse terminals few feet, and that will require disconnecting and rerouting the serial cables. I've never disconnected the console while the filer is up and running. Will this crash the filer, or cause any problems? I know that some Sun servers crash when the console is disconnected, and I'd like to avoid that if at all possible. Thanks in advance for your help, -warren

2 1

Disconnect serial console
by Walsh, Warren (MN65) 10 Oct '01

10 Oct '01

Hi all - I need to move the serial console on my 530 and 740 filers. Basically, the console ports on the filers go to a pair of Wyse terminals. We need to move the Wyse terminals few feet, and that will require disconnecting and rerouting the serial cables. I've never disconnected the console while the filer is up and running. Will this crash the filer, or cause any problems? I know that some Sun servers crash when the console is disconnected, and I'd like to avoid that if at all possible. Thanks in advance for your help, -warren

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