toasters

toasters@lists.teaparty.net

13515 discussions

Busy F740
by Brian Tao 01 Feb '01

01 Feb '01

How many ops/sec is a single F740 officially rated for? :) # rsh nbc-na1 sysstat 1 CPU NFS CIFS HTTP Net kB/s Disk kB/s Tape kB/s Cache in out read write read write age 99% 11785 0 0 3852 8967 5935 3317 0 0 0 95% 11225 0 0 4315 8385 6374 16 0 0 0 100% 10989 0 0 3316 7499 5952 6348 0 0 0 96% 12374 0 0 3630 8735 6596 16 0 0 0 97% 11502 0 0 4079 9386 7211 0 0 0 0 92% 13279 0 0 2141 9466 5503 0 0 0 0 94% 11133 0 0 2793 8861 5290 2472 0 0 0 91% 13849 0 0 2845 6541 3051 0 0 0 0 91% 12882 0 0 2366 7718 5153 16 0 0 0 90% 11270 0 0 3114 10893 5976 16 0 0 0 92% 13656 0 0 2235 8336 5198 15 0 0 0 93% 11616 0 0 3674 9995 5897 0 0 0 0 100% 11045 0 0 3217 7324 6336 6224 0 0 0 100% 12071 0 0 3596 7478 4320 4140 0 0 0 83% 11188 0 0 3147 4314 2042 16 0 0 0 86% 12037 0 0 2996 3768 2204 0 0 0 0 Mon Jan 29 09:00:00 EST [statd]: 9:00am up 91 days, 23:12 3206819678 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 10:00:00 EST [statd]: 10:00am up 92 days, 12 mins, 3242103525 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 11:00:00 EST [statd]: 11:00am up 92 days, 1:12 3280497515 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 12:00:00 EST [statd]: 12:00pm up 92 days, 2:12 3320627495 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 13:00:00 EST [statd]: 1:00pm up 92 days, 3:12 3359963237 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 14:00:00 EST [statd]: 2:00pm up 92 days, 4:12 3401086673 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 15:00:00 EST [statd]: 3:00pm up 92 days, 5:12 3442816074 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 16:00:00 EST [statd]: 4:00pm up 92 days, 6:12 3483761033 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 17:00:00 EST [statd]: 5:00pm up 92 days, 7:12 3522841284 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 18:00:00 EST [statd]: 6:00pm up 92 days, 8:12 3552441745 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 19:00:00 EST [statd]: 7:00pm up 92 days, 9:12 3574376381 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 20:00:00 EST [statd]: 8:00pm up 92 days, 10:12 3592665398 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 21:00:00 EST [statd]: 9:00pm up 92 days, 11:12 3609752095 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 22:00:00 EST [statd]: 10:00pm up 92 days, 12:12 3625268516 NFS ops, 0 CIFS ops, 0 HTTP ops Mon Jan 29 23:00:00 EST [statd]: 11:00pm up 92 days, 13:12 3639419661 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 00:00:00 EST [statd]: 12:00am up 92 days, 14:12 3651946436 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 01:00:00 EST [statd]: 1:00am up 92 days, 15:12 3663387313 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 02:00:00 EST [statd]: 2:00am up 92 days, 16:12 3673728933 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 03:00:00 EST [statd]: 3:00am up 92 days, 17:12 3682329227 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 04:00:00 EST [statd]: 4:00am up 92 days, 18:12 3694782732 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 05:00:00 EST [statd]: 5:00am up 92 days, 19:12 3707095565 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 06:00:00 EST [statd]: 6:00am up 92 days, 20:12 3719706901 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 07:00:00 EST [statd]: 7:00am up 92 days, 21:12 3732211249 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 08:00:00 EST [statd]: 8:00am up 92 days, 22:12 3748531341 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Jan 30 09:00:00 EST [statd]: 9:00am up 92 days, 23:12 3773248114 NFS ops, 0 CIFS ops, 0 HTTP ops Over half a billion NFS ops per day, so we roll the uptime ops counter about once a week... -- Brian Tao (BT300, taob(a)risc.org) "Though this be madness, yet there is method in't"

3 3

A suggestion for the list
by Chris Thompson 31 Jan '01

31 Jan '01

Hmm, first I should apologise for posting the (response to the followup to the unsubscribe request) to the list... I really had not intended to. Secondly: some mailing lists have added headers or footers attached to each message giving directions on how to unsubscribe (or otherwise manage one's list entry). It doesn't totally eliminate unsubscribe messages sent to the list, of course, but it does seem to help. Could something like that be implemented for toasters? It only needs 2 or 3 lines giving a URL and/or an e-mail address. 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.

3 2

FW: Please remove m-casacci@ti.com from the list
by Cortez, Vince 31 Jan '01

31 Jan '01

Why am I getting these messages, Vince Cortez 408-822-3479 vcortez(a)netapp.com Get Answers on NOW (Netapp on the Web)! http://now.netapp.com <http://now.netapp.com/> -----Original Message----- From: Casacci, Mario [mailto:m-casacci@ti.com] Sent: Wednesday, January 31, 2001 8:20 AM To: toasters(a)mathworks.com; owner-toasters(a)mathworks.com Subject: RE: Please remove m-casacci(a)ti.com from the list Please remove m-casacci(a)ti.com <mailto:m-casacci@ti.com> from the list . Tks and regards, Mario

2 1

FW: Please Sign Me Up for NetApp Thread
by Cortez, Vince 31 Jan '01

31 Jan '01

Why am I getting this request? vince Cortez Vince Cortez 408-822-3479 vcortez(a)netapp.com Get Answers on NOW (Netapp on the Web)! http://now.netapp.com -----Original Message----- From: Noble_Russ(a)emc.com [mailto:Noble_Russ@emc.com] Sent: Wednesday, January 31, 2001 7:41 AM To: toasters(a)mathworks.com Subject: Please Sign Me Up for NetApp Thread Thanks Russ Noble

1 0

FW: 2 q's - quotas and tape drives
by Maglinger, Paul 31 Jan '01

31 Jan '01

But if I use User quotas, then I will have to modify my usermap and passwd files to include all of my 250 NT users. I don't want to have to put 250 entries into my usermap file. -----Original Message----- From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] Sent: Tuesday, January 30, 2001 16:37 To: toasters Subject: Re: 2 q's - quotas and tape drives > Along the same lines, we're working on creating home directories for users > here at the corporate office. We're wanting to limit the amount of storage > per user, but from what I've read there is a limitation of 254 qtrees per > volume. We're running NT, so therefore using CIFS, and using Ontap 5.3.7R2. > We are also running NetIQ, but can't install the agent on the filer. We > could limit the disks per volume, but smaller volumes waste more disk space. > To give you an idea, we're considering limits of either 250 or 500MB per > user. Unless I misunderstand you, you do not need a separate qtree for each user. Netapps provide both "tree" quotas and "user" quotas. A "tree" quota limits the total disk space of all files in a directory tree (quota tree), regardless of who owns them. A "user" quota limits the total disk space of files that are owned by a particular user. It sounds like you can do what you want with "user" quotas in one big volume with no qtrees at all. However, you may want to split things up for other reasons. "tree" quotas are typically used to limit the disk space of a project or department consisting of multiple users. And if you really like to micromanage, you can even have user quotas within a qtree. For example, fred user@/vol/vol0 15G - /vol/vol0/qt1 tree 25G - fred user@/vol/vol0/qt1 10G - Here "fred" can use up to 15G in the volume vol0. The qtree qt1 cannot use more than 25G of vol0. And inside qt1, fred can only use 10G. Any disk space that fred uses inside qt1 also counts against his 15G quota for the entire volume. Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

3 2

Re: FW: 2 q's - quotas and tape drives
by kelvin.spaulding＠kodak.com 31 Jan '01

31 Jan '01

From: Kelvin D Spaulding (sorry about lotus notes stuff at end; but...) This may or may not work in your case; but I am using mixed-mode home directories. Each home is the UNIX and WindowsNT home for each user. I put about 50 users in each home directory. The "*" should work if you are using UNIX or Windows NT style security. It should look at the appropriate NIS or domain server to determine the ownership of the files. I am running Ontapp 5.3.6R2, and this is working well. # Users Type Size Files Comment #------- -------------- -------- ------ ---------------------- ----- * user@/vol/vol2/home4 250M 25k # UNIX and NTFS Home Dir * user@/vol/vol2/home5 250M 25k # UNIX and NTFS Home Dir * user@/vol/vol2/home6 250M 25k # UNIX and NTFS Home Dir * user@/vol/vol2/home7 250M 25k # UNIX and NTFS Home Dir bakal user@/vol/vol0/home1 150M 5k # Home quota for Andy B. "Maglinger, Paul" <PMAGLINGER(a)scvl.com> on 01/31/2001 11:09:52 AM To: "'NetApps list server'" <toasters(a)mathworks.com> cc: (bcc: Kelvin D Spaulding/249256/EKC) Subject: FW: 2 q's - quotas and tape drives But if I use User quotas, then I will have to modify my usermap and passwd files to include all of my 250 NT users. I don't want to have to put 250 entries into my usermap file. -----Original Message----- From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] Sent: Tuesday, January 30, 2001 16:37 To: toasters Subject: Re: 2 q's - quotas and tape drives > Along the same lines, we're working on creating home directories for users > here at the corporate office. We're wanting to limit the amount of storage > per user, but from what I've read there is a limitation of 254 qtrees per > volume. We're running NT, so therefore using CIFS, and using Ontap 5.3.7R2. > We are also running NetIQ, but can't install the agent on the filer. We > could limit the disks per volume, but smaller volumes waste more disk space. > To give you an idea, we're considering limits of either 250 or 500MB per > user. Unless I misunderstand you, you do not need a separate qtree for each user. Netapps provide both "tree" quotas and "user" quotas. A "tree" quota limits the total disk space of all files in a directory tree (quota tree), regardless of who owns them. A "user" quota limits the total disk space of files that are owned by a particular user. It sounds like you can do what you want with "user" quotas in one big volume with no qtrees at all. However, you may want to split things up for other reasons. "tree" quotas are typically used to limit the disk space of a project or department consisting of multiple users. And if you really like to micromanage, you can even have user quotas within a qtree. For example, fred user@/vol/vol0 15G - /vol/vol0/qt1 tree 25G - fred user@/vol/vol0/qt1 10G - Here "fred" can use up to 15G in the volume vol0. The qtree qt1 cannot use more than 25G of vol0. And inside qt1, fred can only use 10G. Any disk space that fred uses inside qt1 also counts against his 15G quota for the entire volume. Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

1 0

FS: NetApp 9gb SCSI disks - $450.00@
by ScottUCE＠aol.com 31 Jan '01

31 Jan '01

We have about THIRTY hard-to-find 9gb SCSI drives (for NetApp Storage Shelf 2) available for which we are asking $450.00@. We also have many other NetApp drive types and shelves in stock. Scott Fischmann Union Computer Exchange, Inc. 6233 Idylwood Lane Minneapolis, MN 55436 Phone: 952 935 7282 www.unioncomputer.com

1 0

RE: Physically moving a volume
by Palmer, Jason (London) 31 Jan '01

31 Jan '01

Matt, You may need to refer to the rehoming a foreign volume bit on the NOW site. I have pasted relevent extracts below. ********** Extract 1 ********** Installing a foreign volume BM_1149726You can remove an entire volume from one filer and install it in another, which makes the moved volume a foreign volume to the filer. BM_1178353 Example BM_1178361For example, you might want to move a volume to a different filer to BM_1149727 * replace the volume's disk shelf with one that has a greater storage capacity BM_1149728 * gain access to the files on a dead filer BM_1149729When a filer detects a foreign volume at boot time, it places the foreign volume off-line. You can then bring the foreign volume on-line. For more information about installing and bringing up a foreign volume on-line, refer to "Adding <http://now.netapp.com/NOW/knowledge/docs/ontap/rel523/html/sag/disk5.htm#11 49886> a foreign volume." ********** Extract 2 ********** Adding a foreign volume BM_1149888To add a foreign volume, that is, a volume that was previously installed on another filer, you move the disks that contain the volume from the old filer to the destination filer. BM_1179040Complete the following steps to add a foreign volume. BM_1181660BM_1177101Step BM_1177103Action BM_11771051 BM_1177107Follow the instructions in the hardware guide to remove the disks from the old filer. BM_11771092 BM_1177111 Turn off the destination filer and install the disks in the destination filer's disk shelf. BM_11771133 BM_1177115 Turn on and boot the destination filer. BM_1177116 Results BM_1185503When the destination filer boots, it places the foreign volume off-line. If the foreign volume has the same name as an existing volume on the filer, the filer renames it volume_name(1), where volume_name is the original name of the volume. BM_1185881 _____ Caution: If the foreign volume is incomplete, repeat Steps 1 and 2 to add the missing disks. Do not try to add missing disks while online--doing so will cause them to become hot spare disks. BM_1185905 _____ BM_11855354 BM_1185564 If the filer renamed the foreign volume because of a name conflict, type the following command to rename the volume: BM_1185589vol rename oldname newname BM_1185565 Example BM_1185566The following command renames the volume vol0(1) to vol1: BM_1185567vol rename vol0(1) vol1 BM_11771225 BM_1177124 Type the following command to bring the volume on-line in the new filer, replacing volume_name with the name of the volume: BM_1177133vol online volume_name BM_11791026 BM_1179104 Enter the following command to confirm that the added volume came on-line: BM_1179129vol status BM_1149894 Destroying a volume BM_1149896To destroy a volume, turning its disks back into spare disks, follow these steps. BM_1181656BM_1177162Step BM_1177164Action BM_11771661 BM_1177168To deactivate the volume, enter BM_1177195 vol offline volume BM_11771702 BM_1177172Enter the reboot command to reboot the filer. BM_11771743 BM_1177176To destroy the volume, enter BM_1177211 vol destroy volume BM_1149900 Renaming a volume BM_1149902To rename a volume, follow these steps. BM_1181649BM_1177221Step BM_1177223Action BM_11772251 BM_1177227Enter BM_1177242 vol rename oldvolume newvol BM_11772292 BM_1177231Update the /etc/exports file and run exportfs. BM_11772333 BM_1177235Update any CIFS shares that refer to the volume. BM_1177293 Handling volume failures BM_1177295A volume might fail because of an inconsistent directory or a double-disk failure. If the system does not reboot after a volume failure, take the volume off-line, as follows: BM_1177296 1. Boot the filer from a system boot diskette into maintenance mode. BM_1177297 2. Use the vol command to take the failed volume off-line. BM_1177298If the failed volume was the filer's root volume, you must designate another volume as the new root volume. _____ There may also be issues with moving a root volume between filers ie 760 ----> 840. Just data volumes should be fine. I hope this is of help, Jason -----Original Message----- From: Matt Phelps [ mailto:mphelps@cfa.harvard.edu <mailto:mphelps@cfa.harvard.edu> ] Sent: 31 January 2001 16:44 To: toasters(a)mathworks.com Subject: Physically moving a volume All, We are physically moving a disk volume from a 760 to an 840 tonight. We're resonably confident about bringing up the 840 with the moved disks on it. The volume will come up as a foreign volume (it won't need to be renamed) and we'll just need to do a "vol online" command for it. It's not a root volume. However, the book says to check "your hardware guide" for instructions on removing the disks from the 760. We can't find this anywhere. Our current plan is to remove references to the volume in the various /vol0/etc files; shut down the 760, power it and it's shelves off. Remove the disks and just power everything back on again. Is it that simple? -- Matt Phelps System Administrator, Computation Facility Harvard - Smithsonian Center for Astrophysics mphelps(a)cfa.harvard.edu, http://cfa-www.harvard.edu/~mphelps <http://cfa-www.harvard.edu/~mphelps> -- This communication contains information which is confidential and may also be privileged. It is for the exclusive use of the intended recipient(s). If you are not the intended recipient(s), please note that any distribution, copying or use of this communication or the information in it is strictly prohibited. If you have received this communication in error, please notify the sender immediately and then destroy any copies of it.

1 0

RE: FW: 2 q's - quotas and tape drives
by Ellett, Peter 31 Jan '01

31 Jan '01

Hi, There is a utility up on the NOW site call SecureShare Account Migrator and helps with the following: SecureShare Account Migrator converts users/groups from an NT domain into the format necessary to populate the /etc/passwd and etc/group files on a NetApp Filer. It creates the commands necessary to build CIFS shares for each user and applies appropriate rights to said shares. It also allows for syncing of an NT domain with /etc files, so you can run the program daily to keep your /etc files current. SecureShare Account Migrator is currently a beta release. Similar to SecureShare Account Migrator but in a command-line version, cvtusers can only be run from NT and requires access to NT kernel exports. It is the original incarnation of this tool. Here is a link to where you can find the SecureShare Account Migrator: http://now.netapp.com/NOW/download/tools/secureshaream/ Hope that this helps. Pete Ellett -----Original Message----- From: Jeffrey Krueger [mailto:jkrueger@qualcomm.com] Sent: Wednesday, January 31, 2001 10:53 AM To: Maglinger, Paul Cc: 'NetApps list server' Subject: Re: FW: 2 q's - quotas and tape drives If the UNIX usernames and NT usernames are the same, you can either enable NIS on the filer, or just copy the passwd file from a host with all the UNIX accounts on to the filer. Both ways the filer will automatically map UNIX user "fud" to NT user "NT_DOMAIN\fud". -- Jeff On Wed, Jan 31, 2001 at 10:09:52AM -0600, Maglinger, Paul wrote: > But if I use User quotas, then I will have to modify my usermap and passwd > files to include all of my 250 NT users. I don't want to have to put 250 > entries into my usermap file. > > -----Original Message----- > From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] > Sent: Tuesday, January 30, 2001 16:37 > To: toasters > Subject: Re: 2 q's - quotas and tape drives > > > > Along the same lines, we're working on creating home directories for users > > here at the corporate office. We're wanting to limit the amount of > storage > > per user, but from what I've read there is a limitation of 254 qtrees per > > volume. We're running NT, so therefore using CIFS, and using Ontap > 5.3.7R2. > > We are also running NetIQ, but can't install the agent on the filer. We > > could limit the disks per volume, but smaller volumes waste more disk > space. > > To give you an idea, we're considering limits of either 250 or 500MB per > > user. > > Unless I misunderstand you, you do not need a separate qtree for > each user. Netapps provide both "tree" quotas and "user" quotas. > > A "tree" quota limits the total disk space of all files in > a directory tree (quota tree), regardless of who owns them. > > A "user" quota limits the total disk space of files that are > owned by a particular user. It sounds like you can do what you > want with "user" quotas in one big volume with no qtrees at all. > However, you may want to split things up for other reasons. > > "tree" quotas are typically used to limit the disk space of a project or > department consisting of multiple users. And if you really like to > micromanage, you can even have user quotas within a qtree. For example, > > fred user@/vol/vol0 15G - > /vol/vol0/qt1 tree 25G - > fred user@/vol/vol0/qt1 10G - > > > Here "fred" can use up to 15G in the volume vol0. The qtree qt1 cannot > use more than 25G of vol0. And inside qt1, fred can only use 10G. Any > disk space that fred uses inside qt1 also counts against his 15G quota for > the entire volume. > > Steve Losen scl(a)virginia.edu phone: 804-924-0640 > > University of Virginia ITC Unix Support >

1 0

RE: 2 q's - quotas and tape drives
by Witham, John 31 Jan '01

31 Jan '01

How does the cifs.homedir option play into this? I'm in the same boat, as I have to migrate 1300 CIFS user directories from an ailing NT box to one of my 760s in the damn-near future. -john -----Original Message----- From: Maglinger, Paul [mailto:PMAGLINGER@scvl.com] Sent: Wednesday, January 31, 2001 10:10 AM To: 'NetApps list server' Subject: FW: 2 q's - quotas and tape drives But if I use User quotas, then I will have to modify my usermap and passwd files to include all of my 250 NT users. I don't want to have to put 250 entries into my usermap file. -----Original Message----- From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] Sent: Tuesday, January 30, 2001 16:37 To: toasters Subject: Re: 2 q's - quotas and tape drives > Along the same lines, we're working on creating home directories for users > here at the corporate office. We're wanting to limit the amount of storage > per user, but from what I've read there is a limitation of 254 qtrees per > volume. We're running NT, so therefore using CIFS, and using Ontap 5.3.7R2. > We are also running NetIQ, but can't install the agent on the filer. We > could limit the disks per volume, but smaller volumes waste more disk space. > To give you an idea, we're considering limits of either 250 or 500MB per > user. Unless I misunderstand you, you do not need a separate qtree for each user. Netapps provide both "tree" quotas and "user" quotas. A "tree" quota limits the total disk space of all files in a directory tree (quota tree), regardless of who owns them. A "user" quota limits the total disk space of files that are owned by a particular user. It sounds like you can do what you want with "user" quotas in one big volume with no qtrees at all. However, you may want to split things up for other reasons. "tree" quotas are typically used to limit the disk space of a project or department consisting of multiple users. And if you really like to micromanage, you can even have user quotas within a qtree. For example, fred user@/vol/vol0 15G - /vol/vol0/qt1 tree 25G - fred user@/vol/vol0/qt1 10G - Here "fred" can use up to 15G in the volume vol0. The qtree qt1 cannot use more than 25G of vol0. And inside qt1, fred can only use 10G. Any disk space that fred uses inside qt1 also counts against his 15G quota for the entire volume. Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

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