toasters

toasters@lists.teaparty.net

13520 discussions

Re: Difference in resources?
by Tuc 01 Oct '00

01 Oct '00

> > On Tue, 26 Sep 2000, TTSG wrote: > > > Maybe a CPU % of 8-12, NFSops of 400-600. (I haven't gotten > > That's nothing. I don't think the filer is to blame for the > load. Cache ages? > Varies. I've seen >60, 7, etc. > > > I tried it on Sif. Sif went nuts with file locking. CGI's that need > > to do file lock seem to take FOREVER (7-10 seconds). If I change the CGI to > > point to a local filestore, the load goes from maybe 2.X to 6-7.X . The > > CPU goes 100% with an increased user and kernel. > > I don't know how much time you have to spend on this, but you > might try mounting a set of disk from one of your U1's to the other, to > see if the problem is with NFS in general or with the filer's > implementation of NFS. > Don't I just introduce another unknown, the 2nd U1s ability to serve the content? I don't have time to futz, since this is a production system, but I need to do whats necessary. I'm afraid also that making the 2nd U1 a NFS server will impact ITS performance. I'm already getting a 15-20% I/O wait outta it, which is why we are looking towards the Filer. > > > Thats what I figured. I need to throw 2 of them, serving 7-8Mb/s > > content out the front end. > > Hmmm...I don't know how much cache a F720 has, but maybe you > need something with more cache to serve out that much data. > I've got 4 BSDI's, each pushing 7-8Mb/s out the front, to another F720 with no hassles. If it wasn't for the fact that the BSDI dropped in and went well, I wouldn't even CONSIDER this as a solution. > > > > What network pieces are between Thor and the F720? > > > > > Thor -> 4 ft network cable -> Cisco 2924 switch -> 8 ft network > > cable -> Cisco 5505 -> 6 inch network cable -> RJ45/Punchdown block -> > > 200ft network cable -> RJ45/Punchdown block -> 6 inch network cable -> > > RJ45/Punchdown block -> 24 ft network cable -> RJ45/Punchdown block -> > > 8 ft network -> Cisco 2924 -> 8 ft network cable -> F720 > > 200 ft of network cable? Is that legit, i.e., within the CAT5 > specification? > Yea, and there aren't any collisions or symptoms of problems between the Cat5505 and remote 2924. > > Also, are all the speed negotiations fixed? Many people post of > bad performance which is due to either the filer or the switches being > set to auto-negoatiate. Force both to be fixed. > I don't let ANYTHING in our network auto-negotiate. To me, thats a non-truth. ESPECIALLY with Sun equipment around. 8-) > > > > NFS v2 or v3? If v3, over TCP or UDP? > > You say NFS v3 over UDP. You might also try to force this to be > NFS v2, just to see what happens with the locking, which seems to be the > source of the bottleneck. > Maybe on the Sol 7, not 5.5.1 . I'll try V2 at some point. > > You can disable v3 complete on the filer with > the nfs.v3.enable option, or force a vers=2 mount with the mount > command. > > Until next time... > Thanks, Tuc/TTSG

1 0

Re: Presenting Netapp as a location disk
by mds＠gbnet.net 30 Sep '00

30 Sep '00

On Sat 30 Sep, 2000, James R Grinter <jrg(a)acm.org> wrote: > On Fri, Sep 29, 2000 at 08:38:43AM -0700, Eyal Traitel wrote: > > Anyway, isn't faster-access what DAFS is going to provide? I'd be happy if it just had mount options to allow you to specify non-buffer-cache'd access on Solaris to reduce memory footprints for advanced apps like Oracle, speaking for myself. >-- End of excerpt from James R Grinter -- -Mark ... an Englishman in Derby ...

1 0

Re: Presenting Netapp as a location disk
by Eyal Traitel 30 Sep '00

30 Sep '00

Guys, Isn't it the exact purpose of Unix' vnodes, and NT's redirectors ? The network file system inventors tried to attack this issue, so if applications aren't written correctly, this is not on the file server to solve, this is on the app. writer side... Eyal. --- Mark D Simmons <mds(a)ns.gbnet.net> wrote: > On Wed, Sep 20, 2000 at 01:35:13PM +0100, Richard wrote: > > I know this is not really, a question that applies just to Netapp's > but at the moment > > I am looking at a SAN that allows the shared remote disk array to > be seen by a NT > > system as if it is a local disk drive (this helps make frontpage > happy). And I am trying > > to find a way to do this with a Netapp as a remote filestore, surly > someone has written > > a NTFS filesystem driver for NT that reads from a network drive, > but presents itself as > > a local drive? If a SAN can offer this it must be possible? > > I've informally mentioned that the same thing would be very nice on > Unix too, both > in the distant, and recent past. > > Currently I manage no filers so I cannot really RFE this. > > As a concept it's in serious conflict with the appliance philosphy. > However, I think the > benefits to some users might even justify their stumping up cash > separately to buy it.. > > -- > -Mark ... an Englishman in Derby ... ===== Yours, Eyal Traitel eTraitel(a)yahoo.com, Home: 972-3-5290415 (Tel Aviv) *** eTraitel - it's the new eBuzzword ! *** __________________________________________________ Do You Yahoo!? Yahoo! Photos - 35mm Quality Prints, Now Get 15 Free! http://photos.yahoo.com/

2 1

Re: Multiple cifs.homedir paths (Was: RE: Optimal volume size)
by Darrell Fuhriman 29 Sep '00

29 Sep '00

All this cifs homedir talk has got me thinking. I recall that there was a Microsoft made product which was essentially an automounter for NT. Does anyone know the name of the product in question, and have any experience with it? I would love to be able to point users at one location, and have them find the right toaster. Darrell

1 0

RE: Multiple cifs.homedir paths (Was: RE: Optimal volume size)
by Benn, Paul 29 Sep '00

29 Sep '00

Hi Gang, As it turns out, tilde "~' support does not exist in Data ONTAP 6.0. Sorry for the misinformation. Regards, Paul Benn -----Original Message----- From: Benn, Paul Sent: Friday, September 29, 2000 9:24 AM To: 'Todd C. Merrill'; Brookes, Matt Cc: 'Chris Lamb'; toasters(a)mathworks.com Subject: RE: Multiple cifs.homedir paths (Was: RE: Optimal volume size) We have a two more new features related to CIFS shares that you might find useful: 1) Data ONTAP now provides tilde "~" support, so you can specify: \\<filer's net BIOS name>\~<your login name> to access or map to your home directory or.... \\<filer's net BIOS name>\~<someone else's login name> to access or map to someone else's home directory. 2) There's a new option called "cifs.home_dir_namestyle" and it has three parameters: ntname, domain or mapped. This option allows you to specify the style of user name which is used to determine the home directory. ntname: Uses the NT user name to look up the home directory (same as 5.3.x) domain: Picks up the user's user AND domain name and maps to appropriate subdirectory. For this, the directories beneath the root home directory would be named the same as your NT domains. The user directories would then reside under the appropriate domain directory. mapped: This is used to map to home directories that are named the same as the users' UNIX login names. Regards, Paul Benn Network Appliance -----Original Message----- From: Todd C. Merrill [mailto:tmerrill@mathworks.com] Sent: Friday, September 29, 2000 7:42 AM To: Brookes, Matt Cc: 'Chris Lamb'; toasters(a)mathworks.com Subject: Re: Multiple cifs.homedir paths (Was: RE: Optimal volume size) On Fri, 29 Sep 2000, Brookes, Matt wrote: > No, you weren't dreaming! :) 6.0 supports multiple cifs home directory paths: > > http://now.netapp.com/NOW/knowledge/docs/ontap/rel60/html/sag/cifs19.htm > > And a few other neat tricks worth checking out if you use this feature. That is fan-fscking-tastic! Thanks very much for a feature I never even though to ask for, but we will certainly use now that we know about it. Is it coincidence or deliberate that NetApp now recommends that volume sizes do not exceed ~500 GB? ;) And, Chris, I hope you got some sleep last night. You were bobbing and weaving all over the place. 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: Multiple cifs.homedir paths (Was: RE: Optimal volume size)
by Benn, Paul 29 Sep '00

29 Sep '00

We have a two more new features related to CIFS shares that you might find useful: 1) Data ONTAP now provides tilde "~" support, so you can specify: \\<filer's net BIOS name>\~<your login name> to access or map to your home directory or.... \\<filer's net BIOS name>\~<someone else's login name> to access or map to someone else's home directory. 2) There's a new option called "cifs.home_dir_namestyle" and it has three parameters: ntname, domain or mapped. This option allows you to specify the style of user name which is used to determine the home directory. ntname: Uses the NT user name to look up the home directory (same as 5.3.x) domain: Picks up the user's user AND domain name and maps to appropriate subdirectory. For this, the directories beneath the root home directory would be named the same as your NT domains. The user directories would then reside under the appropriate domain directory. mapped: This is used to map to home directories that are named the same as the users' UNIX login names. Regards, Paul Benn Network Appliance -----Original Message----- From: Todd C. Merrill [mailto:tmerrill@mathworks.com] Sent: Friday, September 29, 2000 7:42 AM To: Brookes, Matt Cc: 'Chris Lamb'; toasters(a)mathworks.com Subject: Re: Multiple cifs.homedir paths (Was: RE: Optimal volume size) On Fri, 29 Sep 2000, Brookes, Matt wrote: > No, you weren't dreaming! :) 6.0 supports multiple cifs home directory paths: > > http://now.netapp.com/NOW/knowledge/docs/ontap/rel60/html/sag/cifs19.htm > > And a few other neat tricks worth checking out if you use this feature. That is fan-fscking-tastic! Thanks very much for a feature I never even though to ask for, but we will certainly use now that we know about it. Is it coincidence or deliberate that NetApp now recommends that volume sizes do not exceed ~500 GB? ;) And, Chris, I hope you got some sleep last night. You were bobbing and weaving all over the place. 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: help
by Cormier, Darleen 29 Sep '00

29 Sep '00

Hi Steve, Just curious. What sort of help are you looking for? Have you been kidnapped by terrorists, lost your car keys, need to know the meaning of life, looking to borrow money, find a cure for the common cold, etc? This is a great group, but if you would be a little more specific we might be able to come up with an idea or two. ;-) -----Original Message----- From: Barr, Stephen [mailto:stephen.barr@kingsburgh.co.uk] Sent: Friday, September 29, 2000 3:49 AM To: 'toasters(a)mathworks.com' Subject: help

1 0

Multiple cifs.homedir paths (Was: RE: Optimal volume size)
by Brookes, Matt 29 Sep '00

29 Sep '00

Hi Chris, No, you weren't dreaming! :) 6.0 supports multiple cifs home directory paths: http://now.netapp.com/NOW/knowledge/docs/ontap/rel60/html/sag/cifs19.htm And a few other neat tricks worth checking out if you use this feature. Matt. ________________________________________________________________ Matthew Brookes mailto:mbrookes@netapp.com Systems Engineer http://www.netapp.com Network Appliance Tel: +353 1 4064600 Unit 36, Rathfarnham Gate Fax: +353 1 4064601 Dublin 14, IRELAND Mob: +353 86 8575127 > -----Original Message----- > From: Chris Lamb [mailto:skeezics@measurecast.com] > Sent: 29 September 2000 08:05 > To: toasters(a)mathworks.com > Subject: Re: Optimal volume size > > > > On Thu, 28 Sep 2000, Todd C. Merrill wrote: > > On Tue, 26 Sep 2000, Moshe Linzer wrote: > > > Jeffrey Krueger wrote: > > > > On Wed, Sep 20, 2000 at 09:23:04AM +0200, Eli Lopez wrote: > > Aieee! EATTRIB2DEEP! > > > > > > BTW, you can create a soft link on the filer called > QTREE1 pointing to > > > > > /vol/vol1/QTREE1 and mount using the link name. > > > > > > > > Cool! I didn't know the NetApp could internally > resolve symlinks for > > > > NFS/CIFS exports/shares and still give us the "right > stuff" from rquotad > > > > and what not. > > > > > > Yeah, the same trick allows us to share our CIFS homedirs > under a single > > > root, without actually moving the user's home directory. > > > > Whoa. What's this? I knew symlinks if resolved on the same > > filesystem on a filer work correctly under CIFS, but this seems > > different. You can symlink across *volumes* on the same > filer and it is > > transparent to NFS and CIFS clients??? > > <Scratches chin, tries to think back, way back, to the late 1900's...> > > Y'know, I can't recall exactly now, but I thought we tried > that trick on a > filer running an early 5.x release... when we went from a > pure, pristine > NFS-only shop to the bag of rabid weasels that is a mixed CIFS/NFS > environment, we had to figure out how to map a flat /home/users/* > namespace into CIFS shares. Only our /home/users was really populated > with symlinks to about a dozen separate subdirectories of a > users qtree, > which segregated them according to groups, so that NFS > exports of those > groups could be divided into netgroups of machines that were > owned by said > groups. (Phew! Say that five times fast.) I.e., we could restrict > exports to some machines so that they could only "see" home > directories > for users in that group, but on shared central servers we > could mount the > parent of the users tree and see everything. Given the (political) > circumstances that necessitated this somehwat bizarre > arrangement, this > was Very clean. Nee, even elegant in its own way. > > And, of course, Windows choked on it like month-old leftovers. > > Because cifs.home_dir only accepted one directory argument to do its > magic, we were stuck. We had a bunch of separate roots, not > just one, so > now typing "cifs shares" on said filer produces something > resembling the > Portland Metro Area phone book. My, how we scroll! (I'm > sure the folks > that read the autosupport mail have probably seen worse, though. :-) > > > So I put in an RFE a couple of years ago to expand the cifs.home_dir > option to accept multiple paths, rather than just a single > directory. > Like setting $PATH to a colon-separated list in any Unix shell: > > /vol/vol0/users/dirA:/vol/vol0/users/dirB:/vol/vol1/users/dirC > > I think someone else had already submitted that one too, > around the same > time. > > "So, how is any of this relevant to the discussion at hand?" > I hear you > cry. > > In glancing over the 6.0 release notes, I *thought* I read > that this very > RFE has finally been included in the release. So, rather > than worry about > directories of symlinks or the vagaries of resolving them > across volumes > in a mixed NFS/CIFS environment, you can simply set cifs.home_dir to a > collection of paths and be done with it. Hooray! Of course, > I'm far too > tired to log into NOW and look for it and see if this is, indeed, the > case, so don't take my word for it. I've had enough caffeine today to > incapacitate a large barnyard animal. > > > OKAY, so sleep is overrated. I went and looked. Bug ID > 13856 is the RFE > that caught my eye, but it doesn't quite describe the thing I > requested, > although it does appear to add some interesting > functionality, although > it's full of Windows goop and not what I was describing with the path > idea. Bzzzt. Sorry to get your hopes up. Please play again soon. > > > It's funny is that I really can't remember if we tried setting > cifs.home_dir to the directory full of symlinks or not. We > must have. > Really. I've probably blocked out the whole sordid affair. > If that had > worked in 5.2.x and we could have avoided defining and maintaining all > those separate shares, by hand, for every bloomin' user... but heck, > that's what we have NT admins for. :-) > > Nowadays I'm unencumbered by such restraints and I have one nice flat > /home, and cifs.home_dir works famously. Still, even though > I don't have > a need for it anymore, I think having cifs.home_dir take a $PATH-style > argument would be a spiffy feature. Don't you agree, > Toastadminarians? > > Cheers! > > -- Chris > > -- > Chris Lamb, Unix Guy > MeasureCast, Inc. > 503-241-1469 x247 > <skeezics(a)measurecast.com> >

2 1

Re: Optimal volume size
by Marcus Smiley 29 Sep '00

29 Sep '00

seems like they ought to fix this... On Fri, 29 Sep 2000, Moshe Linzer wrote: ! symlinks inside a CIFS share will only work if they point to other directories in the same share. What I meant ! was that we make a symlink on the filer (with NFS), and then we share that symlink, instead of sharing the actual ! directory. For example, if my homedir sits under /users1/moshel, I can make a symlink like this: ! ! /pchomes/moshel -> /users1/moshel ! ! and then say options cifs.home_dir /pchomes or share /pchomes/moshel explicitly, and the share will work. ! ! Moshe ! ! Marcus Smiley wrote: ! ! > I tried using sym links to other directories (on the same volume) from a directory that is "cifs shared", and ! > cd'ing into these symlinks works just find over nfs from a unix box, but through windoze ! > they show up as files. Am I doing something wrong?

1 0

help
by Barr, Stephen 29 Sep '00

29 Sep '00

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