toasters

toasters@lists.teaparty.net

13514 discussions

RE: F85 series
by john＠takedapharm.com 14 Oct '01

14 Oct '01

>[0] I know there are a lot of "configurations" (1 shelf, 2 shelves, >etc.) but what I mean is if you buy one shelf, most people will, and >NetApp recommends, keeping 1 disk as a parity drive and 1 as a hot >spare. Sure, one could create a RAID group with 7 data drives and no >parity and hot spare, but I doubt that is "common." Is it possible with ONTAP to create a volume without a parity disk? I've got a bunch o' data that would function fine on a RAID-0 type volume... (SAS Tempfiles, holding tank for data transfers, etc...) I didn't think it was possible... If it is, I've got a use for it. -john John Witham Senior Data Networking Engineer Takeda Pharmaceuticals North America, Inc. V://847.383.3304 F://847.383.3205 mailto://jwitham@takedapharm.com -----Original Message----- From: Todd C. Merrill [mailto:tmerrill@mathworks.com] Sent: Wednesday, February 21, 2001 2:44 PM To: listsarch-toasters(a)enteract.com Cc: 'toasters(a)mathworks.com' Subject: RE: F85 series On Tue, 20 Feb 2001, White, Lance wrote: > performance...so, I ask again (hypothetically, that is), realistically, how > SHOULD a vendor quote storage capacity?!? ...with the most common configuration [0], accepting the default numbers and vendor's recommended operating configurations. In NetApp's case, filers with shelves should be quoted retaining a parity and hot spare drive with the default WAFL overheads and 20% snapshot reserve. Think of it this way: when a typical customer orders a filer he opens it up, plugs it in, gives it a name and a few network numbers, and <poof> how much space does he see? *That* should be the number in the quoted literature. Specifically, if we were considering the case of the self-contained F85, this would be (6 drives minus 1 parity minus 1 hot spare) 4 x 36 GB drives, minus ~10% filesystem minus ~20% snapshot reserve, for a total usable space of roughly 100 GB. In this way, there is no suprise to the customer; management isn't upset that the "216 GB" file server (36x6) they paid for is only giving them half of that to use; etc. Vendors can say also there is a "maximum usable" configuration available; "however, some important features may not be available in this configuration. Your SE can help you decide what is right for your installation." For instance, you could quote a "maximum usable" capacity of 162 GB, which is 5 drives (sacrificing the hot spare) and no snapshot reserve (5x36x0.9). All IMHO of course. I've got a small spreadsheet which takes the disk capacity and number of drives and calculates this for me, 'cause I know the marketing capacities are useless. [0] I know there are a lot of "configurations" (1 shelf, 2 shelves, etc.) but what I mean is if you buy one shelf, most people will, and NetApp recommends, keeping 1 disk as a parity drive and 1 as a hot spare. Sure, one could create a RAID group with 7 data drives and no parity and hot spare, but I doubt that is "common." Until next time... The Mathworks, Inc. 508-647-7000 x7792 3 Apple Hill Drive, Natick, MA 01760-2098 508-647-7001 FAX tmerrill(a)mathworks.com http://www.mathworks.com ---

1 0

RE: cifs file creation date issue
by Muhlestein, Mark 13 Oct '01

13 Oct '01

ONTAP currently maintains 4 times: * atime, updated when the inode is accessed (unless you have disabled that on the volume), * mtime, updated when the file is modified, * ctime, updated when the inode is changed, and * crtime, which is set when the inode is created. Probably what is happening is that the Unix client is displaying the "mtime", while the Windows client is displaying the "crtime". The CIFS protocol has calls to retrieve the ctime, but I don't know of a way to get the ctime using the Win32 APIs. Also, the crtime is not available to NFS clients until NFSv4. So it looks like you're ok if mtime works for you; just use dir/tw from NT. Mark > -----Original Message----- > From: neil lehrer [mailto:nlehrer@ibb.gov] > Sent: Friday, October 12, 2001 7:40 AM > To: toasters > Cc: Chris Kern; Curt Huyser > Subject: cifs file creation date issue > > > 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

RE: Is there a way to tell who is mapping specific filer cifs sha res?
by White, Lance 13 Oct '01

13 Oct '01

Do this via rsh command to a Filer, or on the Filer itself. Displaying CIFS session information BM_1288165 CIFS session information you can display BM_1263345You can display information about connected users and the number of shares and open files for each user. You can also display information about a specific connected user. BM_1263347 Displaying information with the cifs sessions command BM_1263348The cifs sessions command syntax is as follows: BM_1263349cifs sessions <username> BM_1263351 Displaying information about all connected users BM_1263352To display information about all connected users, use the following command syntax: BM_1263354cifs sessions BM_1263355Sample output is BM_1263356Server Registers as 'TOASTER` in group WNT-DOMAIN BM_1263357WINS Server: 272.320.0.4 BM_1263358PC style Access Control is being used BM_1263359Using domain controller WNT-DOMAIN-PDC for authentication BM_1263360======================================== BM_1263361PC (user) #shares #files BM_1263362SMITHPC (qsmith) 1 1 BM_1263363PETERSPC (zpeters) 2 3 BM_1263364 Displaying information about one user BM_1263365To display the information for a particular user, specify the user name in the command; for example: BM_1263366cifs sessions ghopper BM_1263367users BM_1263368 shares/files opened BM_1263369BM_1263370 HALEY-HOME1 (ghopper) BM_1263371 ENG-USERS BM_1263372 Read-denyW - \GHOPPER\SRC\PROD\COMMON\HTTPD\httpd_fast.c BM_1263373BM_1263374BM_1263375 HALEY-PC (ghopper) BM_1263376 ENG-USERS BM_1263377 Displaying connected user security information BM_1263378To display security information for each connected user, use cifs sessions with the -s option. After the first two lines, detailed information for each connected user is displayed. The following example lists only one user. BM_1263379cifs sessions -s BM_1263380users BM_1263381 Security Information BM_1263382 BM_1263383HOLARD-PC (root) BM_1263384 *************** BM_1263385 UNIX uid = 0 BM_1263386 user is a member of group daemon (1) BM_1263387 user is a member of group www (204) BM_1263388 user is a member of group well (0) BM_1263389 user is a member of group http (500) BM_1263390 BM_1263391 NT membership BM_1263392 WNT-DOMAIN\root BM_1263393 WNT-DOMAIN\Domain Users BM_1263394 WNT-DOMAIN\Domain Admins BM_1263395 WNT-DOMAIN\SU Users BM_1263396 WNT-DOMAIN\Installers BM_1263397 BUILTIN\Users BM_1263398 BUILTIN\Administrators BM_1263399 User is also a member of Everyone, Network Users, BM_1263400 Authenticated Users BM_1263401 *************** -----Original Message----- From: Monica Lam [mailto:Monica.Lam@cosinecom.com] Sent: Tuesday, March 06, 2001 10:29 AM To: 'toasters(a)mathworks.com' Subject: Is there a way to tell who is mapping specific filer cifs shares? Hi, We want to intermittantly capture data on which users are mapping which cifs shares off of our filers. Any one familiar with a command line way of doing this, either from NT or solaris or the Network Appliance itself? (The information shows up in the NT server manager, but it is not very useful in terms of capturing trends...) Thanks!

2 1

RE: diskfirmware and sofwtare upgrade
by Mohler, Jeff 12 Oct '01

12 Oct '01

Yes, the disk firmware process will automagically happen when the filer is first booted into ONTAP 6.1. It requires no interraction and will have informational output on the process at the console as well for you. -----Original Message----- From: Zekeriya Eskiocak [mailto:zeskiocak@pro-link.net] Sent: Friday, October 12, 2001 1:55 PM To: toasters(a)mathworks.com Subject: diskfirmware and sofwtare upgrade Has anyone upgraded from 5.3.x to 6.1.x.Is diskfirmware upgrade a requirement before software upgrade? Any experience shared is welcome. thanks Zekeriya Eskiocak System Engineer Prolink Services Istanbul-TURKEY Work:+90 216 573 73 00 Mobile:+90 532 761 80 69

1 0

diskfirmware and sofwtare upgrade
by Zekeriya Eskiocak 12 Oct '01

12 Oct '01

Has anyone upgraded from 5.3.x to 6.1.x.Is diskfirmware upgrade a requirement before software upgrade? Any experience shared is welcome. thanks Zekeriya Eskiocak System Engineer Prolink Services Istanbul-TURKEY Work:+90 216 573 73 00 Mobile:+90 532 761 80 69

1 0

RE: vol copy from 5.3.6R2 to 6.0.1R1
by Fox, Adam 12 Oct '01

12 Oct '01

Let me be the first to say, I could be wrong here, but since 6.0 allows you to offline a volume without rebooting the filer should be able to revert it back without affecting any other volumes. I believe that's what the error message is telling you... > Filesystem version mismatch for destination volume vol1, reverting the > version and aborting transfer. A console message will be > displayed when > this revert is complete. Therefore, look for a revert complete message on the console (and probably /etc/messages) and it should work. SnapMirror would have the same issue for the initial transfer. Basically the filesystems have to match. But since 6.x can revert, it works. Obviously 5.x can't upgrade the filesystem to 6.x. -- Adam Fox NetApp Professional Services, NC adamfox(a)netapp.com > -----Original Message----- > From: Brian L. Brush [mailto:brian@paradyne.com] > Sent: Tuesday, February 20, 2001 2:55 PM > To: Fox, Adam > Cc: toasters(a)mathworks.com > Subject: Re: vol copy from 5.3.6R2 to 6.0.1R1 > > > "Fox, Adam" wrote: > > > > You can still do the transfer. It just has to revert > > the target (F760) to the 5.3 filesystems first. After > > that revert is complete, you can do the vol copy. > > My understanding is, in that case, I would have to revert ALL of the > 760's volumes before the migration from the 230. Although I'm > in a test > environment at this point--well, half of a test > environment--at the time > of the actual migration the 760 will have several hundred gigabytes' > worth of other volumes already online. > > Is there a way to perform the vol copy without affecting the target > filer's other volumes? > > I would try SnapMirror, but I don't have licenses for it on > both boxes. > > I'm really trying to avoid the old Unix box intermediary, both because > down-time is inversely proportional to speed and because my level of > uneasiness is proportional to the intricacy of the migration plan. > > --Brian L. Brush > Senior Systems Administrator > Paradyne Corporation >

4 3

List fun
by fubar＠pir.net 12 Oct '01

12 Oct '01

The following is from ryanb regarding the list fun today. I'm forwarding it due to the fact that the toasters list is currently blocking all mail from his domain until I'm sure that things have cleared up. Unfortunately, I don't have access to the mail queues at Mathworks, so I can't clean stuff out... Wheee. That was a total fuxup when moving some stuff around/redelivering locally. I forgot to strip CCs and multiple recipients when modifying the headers -- again, I totally apologize for the goof-up. I'm thinking that somewhere between 30-50 messages got out, but I'm not so sure. Sorry! (Please don't kill me!) K.

1 0

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

12 Oct '01

Sorry about this folks. I realized too late that the message I was responding to was dated back in March. I seem to be getting a lot of fairly old messages suddenly coming through. Is this happening to anyone else? -- Mike Sphar - Sr Systems Administrator - Engineering Support Peregrine Systems, Inc. -----Original Message----- From: Mike Sphar Sent: Friday, October 12, 2001 12:07 PM To: toasters(a)mathworks.com Subject: RE: ontap 6.x 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.

4 3

Yikes... list regurgitation!
by Brian Tao 12 Oct '01

12 Oct '01

Oops... ryanb(a)enteract.com is spewing old messages back to the list? | ---------- Forwarded message ---------- | Received: from smtp2.mathworks.com (smtp.mathworks.com [144.212.95.12]) | by mail1.nbc.attcanada.ca (8.9.1/8.9.1) with ESMTP id OAA26064 | for <taob(a)risc.org>; Fri, 12 Oct 2001 14:53:48 -0400 (EDT) | Received: from mail.mathworks.com (turing.mathworks.com [144.212.95.101]) | by smtp2.mathworks.com (8.11.6/8.11.6) with ESMTP id f9CIMPO27245; | Fri, 12 Oct 2001 14:22:25 -0400 (EDT) | Received: (from majordom@localhost) | by mail.mathworks.com (8.11.2/8.11.2) id f9CIBkP12812; | Fri, 12 Oct 2001 14:11:46 -0400 (EDT) | Received: from smtp2.mathworks.com (smtp.mathworks.com [144.212.95.12]) | by mail.mathworks.com (8.11.2/8.11.2) with ESMTP id f9CIBkw12807 | for <toasters(a)mathworks.com>; Fri, 12 Oct 2001 14:11:46 -0400 (EDT) | Received: from smtp.mathworks.com (scanner.mathworks.com [144.212.95.161]) | by smtp2.mathworks.com (8.11.6/8.11.6) with ESMTP id f9CIBhO25225 | for <toasters(a)mathworks.com>; Fri, 12 Oct 2001 14:11:43 -0400 (EDT) | Received: from smtp-1.enteract.com (smtp-1.enteract.com [207.229.143.33]) | by smtp.mathworks.com (8.11.6/8.11.6) with ESMTP id f9CIBh225214 | for <toasters(a)mathworks.com>; Fri, 12 Oct 2001 14:11:43 -0400 (EDT) | Received: from marcus.enteract.com (marcus.enteract.com [207.229.143.25]) | by smtp-1.enteract.com (Postfix) with ESMTP | id 90C3B71FF; Fri, 12 Oct 2001 13:11:42 -0500 (CDT) | Received: (from ryanb@localhost) | by marcus.enteract.com (8.11.6/8.11.1) id f9CIBgs58636; | Fri, 12 Oct 2001 13:11:42 -0500 (CDT) | (envelope-from ryanb) | Delivered-To: ryanb(a)enteract.com | Received: (qmail 35712 invoked from network); 13 Feb 2001 20:37:23 -0000 | Received: from smtp.mathworks.com (144.212.95.12) | by pop3-3.enteract.com with SMTP; 13 Feb 2001 20:37:23 -0000 | Received: from mail.mathworks.com (turing.mathworks.com [144.212.95.101]) | by smtp.mathworks.com (8.11.2/8.11.2) with ESMTP id f1DKaZc19094; | Tue, 13 Feb 2001 15:36:36 -0500 (EST) | Received: (from majordom@localhost) | by mail.mathworks.com (8.11.2/8.11.2) id f1DKVuR03737; | Tue, 13 Feb 2001 15:31:56 -0500 (EST) | Received: from smtp.mathworks.com (smtp.mathworks.com [144.212.95.12]) | by mail.mathworks.com (8.11.2/8.11.2) with ESMTP id f1DKVtS03717 | for <toasters(a)mathworks.com>; Tue, 13 Feb 2001 15:31:55 -0500 (EST) | Received: from ibb22.IBB.GOV ([152.75.72.10]) | by smtp.mathworks.com (8.11.2/8.11.2) with ESMTP id f1DKVtc18665 | for <toasters(a)mathworks.com>; Tue, 13 Feb 2001 15:31:55 -0500 (EST) | Received: from ibb.gov (ws4314-090 [152.75.137.245]) | by ibb22.IBB.GOV (8.9.3+Sun/8.9.3) with ESMTP id PAA02219; | Tue, 13 Feb 2001 15:30:33 -0500 (EST) | Message-ID: <3A899968.4E55285A(a)ibb.gov> | Date: Tue, 13 Feb 2001 15:30:32 -0500 | From: neil lehrer <nlehrer(a)ibb.gov> | Organization: US IBB | X-Mailer: Mozilla 4.7 [en] (WinNT; U) | X-Accept-Language: en | MIME-Version: 1.0 | To: listsarch-toasters(a)enteract.com | Cc: "'Traitel, Eyal'" <eyal(a)netapp.com>, | "'Chris Thompson'" <cet1(a)cus.cam.ac.uk>, | toasters <toasters(a)mathworks.com> | Subject: Re: File deletion problem | References: | <A143246963DAD311AD5000508B8BC9A1022535(a)svr-gbn-exc-01.gbr.mentorg.com> | Content-Type: text/plain; charset=us-ascii | Content-Transfer-Encoding: 7bit | Sender: owner-toasters(a)mathworks.com | Precedence: bulk -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

1 0

RE: ontap 6.x
by Mohler, Anissa 12 Oct '01

12 Oct '01

Chris, Actually your information is slightly out of date. The current GA release is 6.0.1R3. Not 5.3.6R2. There are other 6.x releases available as well with different features added. Click here to see what our current available releases are for an F740: http://now.netapp.com/NOW/cgi-bin/software?product=Data+ONTAP&platform=F740 And here to see what the terms "General Availability" and "First Customer Ship" mean: http://now.netapp.com/NOW/download/defs/ontap.shtml When you go to the software download page you get to choose the platform you're using and then you can see the current releases available and some statistics on the number of systems/customers running each release and how long they've been running it. Enjoy! -----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.

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