toasters November 1999

toasters@lists.teaparty.net

104 participants
95 discussions

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

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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 November 1999