toasters

toasters@lists.teaparty.net

13531 discussions

User Quotas in CIFS Environment
by Plawner, Marom 28 Nov '99

28 Nov '99

Hello! We're using the F720 in a pure CIFS environment. We have the: Cifs.home_dir = /users option enabled. Basically, every user automatically gets a home directory on the filer. (Assuming that they have a directory in the /users folder in their username... we have a login script that creates this if they don't, and maps it to a drive letter.) In the quotas, we have a line: * user@/vol/vol0/users 250M # Default users get 250MB home dir Supposedly, each CIFS user who connects is supposed to get 250 MB quota. But what happened is that all users had just a total of 250 MB COMBINED! Why? Because all users were mapped to 1 account name, and that account got 250 MB quota. To work around this problem, we have to import all users from the NT domain to the /etc/passwd file. Not passwords or anything, just use the migrate program. This solves the problem, but creates new problems: * The command line version of the migration tool doesn't work on our domain (of about 4,000 users). I tried in all sorts of configurations, it crashes every time. * The Beta version of the GUI Migration tool works nicely, but I have to run it by hand (no command line parameters as far as I know) * Our company grows about 100 new employees a month, this must be done all the time * If the UID of an account in the /etc/passwd file gets changed, it starts the quota from 0 (even if the directory was full). Therefore, it is very important the whoever runs the program does it right! I don't have the time to do it, but I don't trust anyone else to not screw everything up! Possible solutions: * I thought: maybe an NIS server running on NT reading the SAM database could update the /etc/passwd file automatically. * Some knows of some hidden command line features of the GUI migration tool * Someone at Netapp could provide some sort of support and fix the dos based tool or make something work properly. (Sorry, but I've been sending this question to Netapp and our local suppliers for about 11 months now and I'm fed up with the lack of response I'm getting) * Someone could explain if this wafl.default_nt_user is in any way connected * Maybe someone knows something more (reason for writing). Help would be much appreciated. Thanks! Marom Plawner ITI Systems Group Manager Comverse Network Systems

1 0

rdate
by Priebe, Jason 26 Nov '99

26 Nov '99

Anybody else had trouble getting rdate to work properly on a filer? I'm trying to get rdate on my F720 to contact a Linux server to get the time, and it comes back with the message "rdate: no response from <myhostnamehere>" The Linux box is definitely listening for connections on port 37, and it seems to be responding fine when other boxes make requests to it. I'm pretty sure it's not related to the F720's network configuration. I wish I could test it against other time servers, but it lives on a private network. Jason Priebe WRAL OnLine http://www.wral-tv.com/

4 3

Misc equipment
by Crve＠aol.com 25 Nov '99

25 Nov '99

Anyone out there looking for the following Extreme Network Summit1 Seagate ST 19171FC Fiber Channel Drives (102 available) Xyplex 9000 Cisco Cards AS5300 As5200 AS5800 Newbridge router and Switches Sun ATL Libaries 1800 3500 new us4d only for evauation by sun! Craig Crve(a)aol.com

1 0

disk/canisters needed desperately!!!
by George Kahler 25 Nov '99

25 Nov '99

I am in a desperate need of 7 x 9GB SCSI disks and canisters for the Eurologic black shelf for my F520. If there is anyone out there that can help please let me know. George ------------------------------------------------------------------------------- George Kahler e-mail: george(a)yorku.ca Sr. Systems Administrator humans: (416) 736-5257 x.22699 Computing Services, York University machines: (416) 736-5830 Ontario, Canada, M3J-1P3

2 1

RE: Problems with file dates
by Garrett Burke 25 Nov '99

25 Nov '99

Hi Dave, Is the data in these files ok or is it corrupt? If it's corrupt then I'd have a look at what version of Win95 is running and has it been patched. What you might be seeing is file corruption due to caching on the client and this might be resulting in the incorrect dates. Another thing to look for is virus scanners on the Win95 clients which are being run against the filer. Some of these do funny things - like changing the archive bit so all your files now end up in an incremental backup. Good luck, GB > -----Original Message----- > From: Dave Atkin [SMTP:dla1@york.ac.uk] > Sent: 25 November 1999 09:07 > To: toasters(a)mathworks.com > Subject: Problems with file dates > > We are finding an increasing number of user files (several thousand files > at present) with bizarre dates, eg > > -rwx--x--x 1 rfx3 ug93 49 Dec 27 1931 > /usr/fsa/ug93/rfx3/letter-home > -rwx--x--x 1 socx12 socs 460 Jul 22 1948 > /usr/fsa/extn/socx12/nov2nd > > The dates display mainly in the 1930s although there are a few around the > year 2009! These files seem to have been created over CIFS from PCs > running Windows 95. > ------------------------------------------------------ ******************************************************************* This email and any files transmitted with it are confidential and are solely for the use of the individual or organisation to whom they are addressed. If you have received this mail in error please notify the system administrator at +353 1 6399700 or by email to hostmaster(a)msc.ie This email message has been swept for computer viruses. Managed Solutions Corporation, Enterprise Customer Relationship Management, Workflow and Contract Administration. Tel: 353 1 639 9700 Fax: 353 1 639 9701 Don't forget to visit our website at http://www.msc.ie ********************************************************************

1 0

RE: Cisco pings NetApp
by Plawner, Marom 25 Nov '99

25 Nov '99

Yes, we have that, too. If you use *nix and do a 'ping -f' to the filer, it responds with about 87% packet loss. I asked our local supplier about this and they told me this is an intended design, and does not affect the performance of the machine. -----Original Message----- From: Krzysztof Miller [mailto:tytus@lucent.com] Sent: Thursday, November 25, 1999 9:54 AM To: toasters(a)mathworks.com Subject: Cisco pings NetApp Hi, I ahve two filers F740 and F520. It happens for both of them. Cisco router pings filer and sucess rate is about 90%. We have switched network and it doesn't matter if filer has 100Mb halfduplex or full duplex. If Cisco pings SUN machine (the same network) success rate is 100 %. Does anybody seen something similiar ? best regards -- _____________________________________________________________ Krzysztof M. Miller, CIO Poland email : tytus(a)lucent.com phone : +48 52 3491845 fax : +48 52 3463033 mobile: +48 601 358032 _____________________________________________________________

1 0

Wincenter Pro, excel 97 and netapp problem
by Krzysztof Miller 25 Nov '99

25 Nov '99

Hi, I am new on this list. Let me introduce myself - my name is Krzysztof Miller, I work for Lucent Technologies CIO dept, in Poland. We have F520 running 5.1.2 . Did anybody had problems with Wincenter Pro (or Cytrix Winframe) and NetApp ? We have following problem - when excel 97 session is open when you log off from wincenter, it deletes file, which is opened. NCD support suggest to upgrade system to 4.3.4D9, but I have 5.1.2 regards -- _____________________________________________________________ Krzysztof M. Miller, CIO Poland email : tytus(a)lucent.com phone : +48 52 3491845 fax : +48 52 3463033 mobile: +48 601 358032 _____________________________________________________________

3 2

reading tar format tapes
by Artur Shnayder 23 Nov '99

23 Nov '99

Hello, I wonder if anybody had experience with reading tar format tapes from device, that connected to Network Appliance. I tried from Solaris machine "tar xvf netapp:nrst0a" ... and got "netapp:nrst0a: No such file or directory". ufsdump utility works fine. Thanks. -- ~*-,._.,-*~`^`~*-,._.,-*~`^`~*-,._.,-*~`^`~*-,._.,-*~`^`~*-,._.,-*~`^ Artur Shnayder Voice: (609)655-5105 x12 System Manager Fax: (609)655-5114 Email: artur(a)cgen.com Compugen Inc URL: http://www.cgen.com ~*-,._.,-*~`^`~*-,._.,-*~`^`~*-,._.,-*~`^`~*-,._.,-*~`^`~*-,._.,-*~`^

3 4

RE: reading tar format tapes
by Bond, Andrew 23 Nov '99

23 Nov '99

It's documented as bug # 16390: %%% TITLE: Filer responds to rmt status inquiry with an error code %%% DESCRIPTION: Filers support the rmt protocol and thus a tape drive attached to a filer can act as a target rmt tape drive. The rmt driver on the filer will respond to a status inquiry (S option) with an error code. This behavior breaks ufsdump on Solaris 7 since it requests the status of the target rmt drive and receives an error back if the rmt device is attached to a filer. %%% WORKAROUND: Do not select rmt devices on Netapp's filers as target output devices for ufsdump on Solaris 7. The fix is currently scheduled for 5.3.5. Andrew > -----Original Message----- > From: owner-dl-toasters(a)netapp.com > [mailto:owner-dl-toasters@netapp.com]On Behalf Of Dave Atkin > Sent: 23 November 1999 08:31 > To: Artur Shnayder > Cc: toasters(a)mathworks.com > Subject: Re: reading tar format tapes > > > On Mon, 22 Nov 1999, Artur Shnayder wrote: > > > Hello, > > I wonder if anybody had experience with reading tar format > tapes from > > device, > > that connected to Network Appliance. > > I tried from Solaris machine "tar xvf netapp:nrst0a" ... and got > > "netapp:nrst0a: No such file or directory". > > ufsdump utility works fine. > > > > > > Netapp's implementation of the rmt protocol is at best > "minimalist" and > at worst wrong. Earlier this year I spent a few happy hours with a > protocol analyser and found that filers don't respond properly to tape > drive status requests and hence some clients won't talk to > them. That may > be the problem in this case. > > I reported this to Netapp some time ago but I don't know if anything > happened. It's probably fixed in a future major release of their > no-upgrades-needed OS! > > ------------------------------------------------------ > Dave Atkin, Head of Technical Services > Computing Service, University of York, YORK YO10 5DD > Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 > Email: D.Atkin(a)york.ac.uk > ------------------------------------------------------ > >

1 0

searching for 230 ethernet card...
by Linda Walton 22 Nov '99

22 Nov '99

I realize the 230 is in the "end of life" cycle at Network Appliance and that new parts are not available. Does anybody have an unused ethernet card for a 230 that I can buy or trade for? Happy Thanksgiving to all, Linda Walton

1 0

Re: more disks in certain raidgroup
by Aaron M. Sims 22 Nov '99

22 Nov '99

On Nov 21, tomi.rautio(a)nokia.com wrote: > > Hello there, > > is it possible to add mode disks in certain raidgroup. > > I already have raidgroup 0 and 1, all disks in same/one vol0. > > Raid group0: 14 disks and group1:28 disks and I want to add more disks in > group0, How? Sorry you can't. To the best of my knowledge, you can only add disks to the raid group most recently created. And by the way, 28 disks in one raid group??? IMHO, that's a lot. What kind of reconstruct times are you seeing for that? I have always used 7 max. It gives pretty good reconstruct times. -- Aaron M. Sims | "The reason why bad things happen to you is | because you're a dumbass!" ams(a)gtf.org | - Red Foreman, That 70s Show |

5 5

more disks in certain raidgroup
by tomi.rautio＠nokia.com 20 Nov '99

20 Nov '99

Hello there, is it possible to add mode disks in certain raidgroup. I already have raidgroup 0 and 1, all disks in same/one vol0. Raid group0: 14 disks and group1:28 disks and I want to add more disks in group0, How? Thanks, Tomi.Rautio

1 0

Re: NetApp CEO
by Mohan Movva 20 Nov '99

20 Nov '99

Ontap requires Upgrade but much less than most of the other OS available. In could be a generalised statement in comparison to Microsoft Products. Mohan. ----- Original Message ----- From: John Tatar <tatar(a)dis.anl.gov> To: <toasters(a)mathworks.com> Sent: Thursday, November 18, 1999 1:47 PM Subject: NetApp CEO > Yesterday, I was at my health club working out and watching CNBC. Here > is the CEO of Netapp talking about their last quarter and their product > line. What struck me was his statement about the product (This is not > an exact quote - but a good approximation. > > Interviewer: So you don't have do things like upgrade the OS > > NetApp CEO: No, our products are like a refrigerator, how often do you > have to upgrade your refrigerator. > > Could someone at NetApp sign up the CEO for NetApp 101: Data ONTAP > System Administration - Multiprotocol. ;-) > > > JT > > -- > > =================================================================== > > John J. Tatar > > Systems & Network Engineering Section > > Advanced Computer Applications Group > > Decision & Information Sciences Division > > Argonne National Laboratory > > > > mailto:tatar@dis.anl.gov or john(a)tatar.com > > Office: 630-252-3242 > > Fax: 630-252-5128 > > Pager: 630-266-1063 > > =================================================================== > > >

1 0

RE: options cift.home_dir question
by Jones, Bill 20 Nov '99

20 Nov '99

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 This worked great. Thanks. Bill - -------------------------------------- Bill Jones System Support Analyst Network Associates, Inc. bjones(a)nai.com Business PGP Fingerprint F95E 2D96 37E8 01D0 E9AA CBD2 FA68 15D8 63C2 1BE3 Personal PGP Fingerprint 8713 EB44 EE05 8915 B470 D57D D9DB 5A46 1B1D 0BA2 > -----Original Message----- > From: Uren, Jim [mailto:jim.uren@netapp.com] > Sent: Friday, November 19, 1999 5:52 PM > To: 'Jones, Bill'; 'toasters(a)mathworks.com' > Subject: RE: options cift.home_dir question > > > Hi Bill, > From your filer console type > options cifs.home_dir "" > to clear the homedir path, > Jim Uren > > -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.1 iQA/AwUBODbF2fpoFdhjwhvjEQI1GgCfVw1pieDuKgCxMEaU6ufe6UIIgcgAoLsr SC2V7Yddecr9A53G1CFhvljS =T8At -----END PGP SIGNATURE-----

1 0

RE: options cifs.home_dir question
by Jones, Bill 20 Nov '99

20 Nov '99

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I understand the way in which homedirs are working on the filer, and I am confident that the permissions are set correctly. There are really two issues at hand. #1. Users see their homedir when the list available shares when the connect to the server (Start -> Run -> \\filer or using Windows Explorer through Network Neighborhood). The user then looks in the share with their user name, and sees all the files stored in their homedir. They panic thinking that somehow their data is being shared out on the network for everyone to see. They run to me and say, "HELP! There's a share on FILER with my name on it!!!!" and I get to explain this to them amid the many other projects going on. Even the more savvy users come by and ask, "What's up with this?" and I get to explain it once again.. And yes, we'll ignore that this was all explained in an email a week or so ago. #2. Our local domain will soon be migrated to a resource domain. Users will then log in to the corporate-master-globular-user domain. The filer will stay a memeber of the resource domain, because it _is_ a local resource. and cifs.home_dir does not work across domains. So, spending the time to educate the user community is a wasted effort. :} I want cifs.home_dir off. I cannot set it to null because that is not a valid pathname. I am almost to the point of creating a volume, pointing cifs.home_dir at it, and then killing the volume. I have concidered killing the CIFS.HOMEDIR share under server manager, but I have this horrible fear that in doing either one I will cause my filer to panic or crash. Bill > -----Original Message----- > From: Uren, Jim [mailto:jim.uren@netapp.com] > Sent: Friday, November 19, 1999 6:13 PM > To: 'Jones, Bill' > Subject: RE: options cift.home_dir question > > > Hi Bill, > I replied to this question via toasters. But I have > a further question. If you have time to answer (sounds > like you are harrassed and busy) :) > I'd like to know a little more about the problem. > > When the cifs.home_dir option is set to some legal path, > users can have home directories. But each homedir is > individual. Suppose your homedir path is /vol/vol0/home. > Underneath home there are directories bill and susie. > > When bill accesses the filer he will see all the filer's shares > and also a share called "bill" that is at /vol/vol0/home/bill. > If susie looks at the share list, it will also have all the > "real" shares and also a share called susie which is at > /vol/vol0/home/susie. But bill doesn't see a share called > "susie", and susie doesn't see "bill". > > Also, the sysadmin can set the permissions/ACLs on each > user's homedir to give them ownership privileges. Then, > the user can the security to restrict access to files > from others. > > So I wonder if your users browse the filer with Explorer > or do "net view \\filer" from a DOS prompt and see a share > with their name and think everyone else sees it too? > Jim Uren > > > -----Original Message----- > > From: Jones, Bill [mailto:Bill_Jones@NAI.com] > > Sent: Friday, November 19, 1999 5:21 PM > > To: 'toasters(a)mathworks.com' > > Subject: options cift.home_dir question > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > How do I turn it off??? > > > > It seemed like a good idea at the time, but now users are > > concerned that their homedirs are a share for everyone to see. > > The question load is getting very repetitive and annoying!!!! > > > > Thanks in advance. > > > > Bill > > > > -----BEGIN PGP SIGNATURE----- > > Version: PGP Personal Privacy 6.5.1 > > > > iQA/AwUBODX4t/poFdhjwhvjEQL8pgCfZx9qsvekgCGtS11y79pLADYCvRMAnijQ > > V88oVOycQszl87SJ2zFwC7F5 > > =kZjI > > -----END PGP SIGNATURE----- > > > -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.1 iQA/AwUBODauYPpoFdhjwhvjEQLXbACeP9dFHMoyGuF4Ft5yxL1S2r9n7wwAoOPE GS/LeyV7AEttM0FW4UtNS+sc =PO1A -----END PGP SIGNATURE-----

1 0

RE: options cift.home_dir question
by Uren, Jim 20 Nov '99

20 Nov '99

Hi Bill, From your filer console type options cifs.home_dir "" to clear the homedir path, Jim Uren > -----Original Message----- > From: Jones, Bill [mailto:Bill_Jones@NAI.com] > Sent: Friday, November 19, 1999 5:21 PM > To: 'toasters(a)mathworks.com' > Subject: options cift.home_dir question > > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > How do I turn it off??? > > It seemed like a good idea at the time, but now users are concerned > that their homedirs are a share for everyone to see. The question > load is getting very repetitive and annoying!!!! > > Thanks in advance. > > Bill > > -----BEGIN PGP SIGNATURE----- > Version: PGP Personal Privacy 6.5.1 > > iQA/AwUBODX4t/poFdhjwhvjEQL8pgCfZx9qsvekgCGtS11y79pLADYCvRMAnijQ > V88oVOycQszl87SJ2zFwC7F5 > =kZjI > -----END PGP SIGNATURE----- >

1 0

options cift.home_dir question
by Jones, Bill 20 Nov '99

20 Nov '99

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 How do I turn it off??? It seemed like a good idea at the time, but now users are concerned that their homedirs are a share for everyone to see. The question load is getting very repetitive and annoying!!!! Thanks in advance. Bill -----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.1 iQA/AwUBODX4t/poFdhjwhvjEQL8pgCfZx9qsvekgCGtS11y79pLADYCvRMAnijQ V88oVOycQszl87SJ2zFwC7F5 =kZjI -----END PGP SIGNATURE-----

1 0

Mailing list
by dennism＠dtn.com 19 Nov '99

19 Nov '99

Can I be added to the toasters mailing list? Thank you, dennis

1 0

SCSI bus timeout
by Dave Toal 19 Nov '99

19 Nov '99

Folks, Ignorance question here, if you don't mind. We're seeing this timeout error -- "relog syslog SCSI drive 6.0 max timeout count exceeded" followed by "Resetting SCSI bus 6 (ha #3)". However, sysconfig -r doesn't show drive 6.0 on ha id 3 anywhere. Could someone please explain what's going on here? Thanks much. Dave Stephen Lasseter wrote: > Fri Nov 19 00:00:01 GMT [smith: statd]: 12:00am up 25 days, 2:48 169239880 NFS ops, 0 CIFS ops, 63 HTTP ops > Fri Nov 19 01:00:01 GMT [smith: statd]: 1:00am up 25 days, 3:48 169345577 NFS ops, 0 CIFS ops, 63 HTTP ops > Fri Nov 19 02:00:01 GMT [smith: statd]: 2:00am up 25 days, 4:48 169451567 NFS ops, 0 CIFS ops, 63 HTTP ops > Fri Nov 19 02:20:08 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84180): command timeout, retrying request > Fri Nov 19 02:20:08 GMT [smith: isp_timeout]: Resetting SCSI bus 6 (ha #3) > Fri Nov 19 02:25:34 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84660): command timeout, retrying request > Fri Nov 19 02:25:34 GMT [smith: isp_timeout]: Resetting SCSI bus 6 (ha #3) > Fri Nov 19 02:32:05 GMT [smith: rc]: de_main: e0 : Link up. > Fri Nov 19 02:32:05 GMT [smith: rc]: relog syslog Fri Nov 19 02:30:53 GMT [smith: isp_timeout]: 6.0(0xfffffc0000e84b40): command timeout, retrying request > > Fri Nov 19 02:32:05 GMT [smith: rc]: relog syslog SCSI drive 6.0 max timeout count exceeded - system resetting to recover! > > Fri Nov 19 02:32:05 GMT [smith: rc]: NetApp Release 5.2.1P2 boot complete. Last disk update written at Fri Nov 19 02:30:22 GMT 1999 > > smith> sysconfig -r > Volume brs1 > > RAID group 0 > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) > --------- ----- ------------ ---- -------------- -------------- > parity 0a.8 0a 1 0 FC:A 17000/34816000 17366/35566480 > data 0a.1 0a 0 1 FC:A 17000/34816000 17366/35566480 > data 0a.4 0a 0 4 FC:A 17000/34816000 17366/35566480 > data 0a.0 0a 0 0 FC:A 17000/34816000 17366/35566480 > data 0a.5 0a 0 5 FC:A 17000/34816000 17366/35566480 > data 0a.13 0a 1 5 FC:A 17000/34816000 17366/35566480 > data 0a.10 0a 1 2 FC:A 17000/34816000 17366/35566480 > data 0a.3 0a 0 3 FC:A 17000/34816000 17366/35566480 > data 0a.11 0a 1 3 FC:A 17000/34816000 17366/35566480 > data 0a.9 0a 1 1 FC:A 17000/34816000 17366/35566480 > data 0a.2 0a 0 2 FC:A 17000/34816000 17366/35566480 > data 0a.28 0a 3 4 FC:A 17000/34816000 17366/35566480 > data 0a.29 0a 3 5 FC:A 17000/34816000 17366/35566480 > data 0a.30 0a 3 6 FC:A 17000/34816000 17366/35566480 > > Volume spool (root) > > RAID group 0 > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) > --------- ----- ------------ ---- -------------- -------------- > parity 0a.12 0a 1 4 FC:A 17000/34816000 17366/35566480 > data 0a.14 0a 1 6 FC:A 17000/34816000 17366/35566480 > data 0a.6 0a 0 6 FC:A 17000/34816000 17366/35566480 > > Volume inbox > > RAID group 0 > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) > --------- ----- ------------ ---- -------------- -------------- > parity 0a.17 0a 2 1 FC:A 17000/34816000 17366/35566480 > data 0a.16 0a 2 0 FC:A 17000/34816000 17366/35566480 > data 0a.18 0a 2 2 FC:A 17000/34816000 17366/35566480 > data 0a.21 0a 2 5 FC:A 17000/34816000 17366/35566480 > data 0a.22 0a 2 6 FC:A 17000/34816000 17366/35566480 > data 0a.24 0a 3 0 FC:A 17000/34816000 17366/35566480 > data 0a.25 0a 3 1 FC:A 17000/34816000 17366/35566480 > > Volume hostapp > > 0a 1 4 FC:A 17000/34816000 17366/35566480 > data 0a.14 0a 1 6 FC:A 17000/34816000 17366/35566480 > data 0a.6 0a 0 6 FC:A 17000/34816000 17366/35566480 > > Volume inbox > > RAID group 0 > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) > --------- ----- ------------ ---- -------------- -------------- > parity 0a.17 0a 2 1 FC:A 17000/34816000 17366/35566480 > data 0a.16 0a 2 0 FC:A 17000/34816000 17366/35566480 > data 0a.18 0a 2 2 FC:A 17000/34816000 17366/35566480 > data 0a.21 0a 2 5 FC:A 17000/34816000 17366/35566480 > data 0a.22 0a 2 6 FC:A 17000/34816000 17366/35566480 > data 0a.24 0a 3 0 FC:A 17000/34816000 17366/35566480 > data 0a.25 0a 3 1 FC:A 17000/34816000 17366/35566480 > > Volume hostapp > > RAID group 0 > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) > --------- ----- ------------ ---- -------------- -------------- > parity 0a.20 0a 2 4 FC:A 17000/34816000 17366/35566480 > data 0a.19 0a 2 3 FC:A 17000/34816000 17366/35566480 > > Spare disks > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) > --------- ----- ------------ ---- -------------- -------------- > spare 0a.27 0a 3 3 FC:A 0 17366/35566480 > spare 0a.26 0a 3 2 FC:A 0 17366/35566480 > > Partner disks > > RAID Disk HA.ID HA SHELF BAY CHAN Used (MB/blks) Phys (MB/blks) > --------- ----- ------------ ---- -------------- -------------- > partner 1.0 1 0 0 FC:B 0 17366/35566480 > partner 1.1 1 0 1 FC:B 0 17366/35566480 > partner 1.2 1 0 2 FC:B 0 17366/35566480 > partner 1.3 1 0 3 FC:B 0 17366/35566480 > partner 1.4 1 0 4 FC:B 0 17366/35566480 > partner 1.5 1 0 5 FC:B 0 17366/35566480 > partner 1.6 1 0 6 FC:B 0 17366/35566480 > partner 1.8 1 1 0 FC:B 0 17366/35566480 > partner 1.9 1 1 1 FC:B 0 17366/35566480 > partner 1.10 1 1 2 FC:B 0 17366/35566480 > partner 1.11 1 1 3 FC:B 0 17366/35566480 > partner 1.12 1 1 4 FC:B 0 17366/35566480 > partner 1.13 1 1 5 FC:B 0 17366/35566480 > partner 1.18 1 2 2 FC:B 0 17366/35566480 > partner 1.19 1 2 3 FC:B 0 17366/35566480 > partner 1.20 1 2 4 FC:B 0 17366/35566480 > partner 1.14 1 1 6 FC:B 0 17366/35566480 > partner 1.16 1 2 0 FC:B 0 17366/35566480 > partner 1.17 1 2 1 FC:B 0 17366/35566480 > partner 1.22 1 2 6 FC:B 0 17366/35566480 > partner 1.21 1 2 5 FC:B 0 17366/35566480 > partner 1.32 1 4 0 FC:B 0 17366/35566480 > partner 1.33 1 4 1 FC:B 0 17366/35566480 > partner 1.34 1 4 2 FC:B 0 17366/35566480 > partner 1.35 1 4 3 FC:B 0 17366/35566480 > partner 1.36 1 4 4 FC:B 0 17366/35566480 > partner 1.37 1 4 5 FC:B 0 17366/35566480 > partner 1.38 1 4 6 FC:B 0 17366/35566480 > smith> > -Steve

3 2

64-bit protocol ops counters?
by Brian Tao 19 Nov '99

19 Nov '99

Easy question... did anything change since 5.2.1 to give us 64-bit ops counters? A couple of our F740's are busy enough to roll 2^32 NFS ops every two weeks, and I get bogus stuff like: # rsh nfs3 nfsstat -l 10.35.10.2 tor-adm1-nfs NFSOPS = 759822365 (4294967087%) 10.35.10.3 tor-dev1-nfs NFSOPS = 79004302 (4294967275%) 10.35.10.17 tor-vs1-nfs NFSOPS = 2388554097 (528%) 10.35.10.18 tor-vs2-nfs NFSOPS = 3999698242 (82%) 10.35.10.19 tor-vs3-nfs NFSOPS = 1563148406 (4294966864%) 10.35.10.20 tor-vs4-nfs NFSOPS = 576153104 (4294967138%) 10.35.10.21 tor-vs5-nfs NFSOPS = 2690811725 (444%) 10.35.10.26 tor-fp1-nfs NFSOPS = 466426683 (4294967168%) Tue Nov 16 23:00:01 EST [nfs3: statd]: 11:00pm up 116 days, 2:53 4281632236 NFS ops, 0 CIFS ops, 0 HTTP ops Wed Nov 17 00:00:02 EST [nfs3: statd]: 12:00am up 116 days, 3:53 4291222987 NFS ops, 0 CIFS ops, 0 HTTP ops Wed Nov 17 01:00:01 EST [nfs3: statd]: 1:00am up 116 days, 4:53 4730533 NFS ops, 0 CIFS ops, 0 HTTP ops Wed Nov 17 02:00:01 EST [nfs3: statd]: 2:00am up 116 days, 5:53 12718144 NFS ops, 0 CIFS ops, 0 HTTP ops -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

1 0

Re: NetApp CEO
by Graydon Dodson 19 Nov '99

19 Nov '99

FYI. I know from personal experience that Dan Warmenhoven (Netapp's CEO) is a regular reader of this list..... Graydon Dodson grdodson(a)lexmark.com Lexmark International Inc.

1 0

where can I get F330 parts?
by Jay Orr 18 Nov '99

18 Nov '99

I was wondering with the EOL on the F330's, we had been thinking of adding more space, but to do so we'd need : 1) Another SCSI card. 2) More memory to handle it. 3) Another Tray. Anyone know where I can find this stuff? New or used... Anyone out there scrapping theirs? ----------- Jay Orr Systems Administrator Fujitsu Nexion Inc. St. Louis, MO

1 0

No more 4GB drives available??
by Dane Jasper 17 Nov '99

17 Nov '99

I've got an F230 that I need disks for, but Netapp is telling me that they don't have any to sell. I need the space, and would like to buy disks. Does anyone have a source for these, or some to sell? I'm looking for like four to six drives. -- Dane Jasper Sonic.net, Inc. (707)522-1000 mailto:dane@sonic.net http://www.sonic.net/ Key fingerprint = A5 D6 6E 16 D8 81 BA E9 CB BD A9 77 B3 AF 45 53

3 2

case #79131, Very Poor Backup performances: 1Gb/H with Veritas Netbackup through NFS
by Pierre Maubert 16 Nov '99

16 Nov '99

Hi, We have several F330 in TIF, 2 of them have an enourmous number of small files: over 3.5M for one single volume. We have increase the maxfiles value to 4328504. We have currently a significative degradation of backup performances on these 2 servers: backup are done at 1.5Gb, on both server, wheras we reach 5Gb/h for the 3 others. Servers are all running Dataontap5.2.3, and are all identical. F330, 128Mb Ram, 24*4Gb disks, I wonder what kind of fine tuning can be done to speed up the backup. -- Regards, Pierre . +------------------------------------------------------+ | Pierre Maubert, Sys_Admin Texas Instruments France | | email:p-maubert@ti.com Tel: +33 49322.2681 | | Fax: +33 49202.4669 Pager: 0606498982 | +------------------------------------------------------+

11 22

RE: FC-AL: Onboard vs. PCI Adapter Card
by Norman, Paul 16 Nov '99

16 Nov '99

> -----Original Message----- > From: Shaun T. Erickson [mailto:ste@research.bell-labs.com] > Sent: Monday, November 15, 1999 8:27 PM > To: Norman, Paul > Cc: toasters(a)mathworks.com > Subject: Re: FC-AL: Onboard vs. PCI Adapter Card > > > "Norman, Paul" wrote: > > > > Over the last couple days, there has been some discussion > about on-board FC-AL > > in our filers. This summer, NetApp started shipping > filers with an FC-AL > > adapter card rather than the on-board FC-AL to improve > reliability and > > performance. We did this because we found errors which, > though recoverable, > > potentially effect performance and loop stability. The > problem effected a very > > small fraction, just a few percent, of the installed base. > > Thank you for your reply. However, you didn't address the main > concern/perception of many folks here: that NetApp apparently shipped > many F700 series systems with onboard FC-AL controllers that had hard > failures shortly after being put into production, after which NetApp Perhaps I missed some e-mails, but I didn't see anyone suggesting that there were "many F700" filers that had "hard failures shortly after being put into production". As I said the number of filers with instability problems was quite small. We've shipped on the order of 5,000 F700 series filers, the vast majority of which run fine on on-board FC-AL. About one percent of these exhibited instability on the on-board FC-AL and not all of those the instant they were put into production. All that being said, as I look back on how we handled this problem I think NetApp should have been more aggressive in alerting the installed base. You can't be a chicken little crying the sky is falling every time you have a hiccup in the production line, but you also have to recognize when an issue is not just temporary problem. > apparently started sending out new filers with the PCI card > pre-installed, to be used in place of the onboard controller. That's > quite different from what you just described. > > Can you elaborate on and clarify this issue for us, please? I think I've been pretty clear, but please feel free to call me tomorrow if you want to discuss further. 408 822 6288 is my direct line. > > TIA, > -ste >

1 0

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