toasters September 2000

toasters@lists.teaparty.net

122 participants
161 discussions

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

Solaris 2.5.1, stat/read/fcntl random freezes on NFS
by Graydon Dodson 29 Sep '00

29 Sep '00

This is similar to a problem we have been experiencing with increasing frequency. We run large batch jobs that compile our S/W. During these batch jobs we get "file not found" or "make: no rule to create target" type errors where we can prove the files existed on the filler when the Suns reported them missing. We don't have a "hang" just a failure to stat(). The problem has manifested itself on both our Solaris 2.5.1 and Solaris 8 systems. The filler is a F760 (5.3.5R2P2). The load on the filler when this happens is typically 10,000 ops/sec or greater. Netapp has asked for packett traces but we are talking gigabit interfaces here, the trace files are huge and "pktt" is dropping about 80% of the packets anyway. We have already cut "nfs.udp.xfersize" to 8K and are running out of ideas. I am getting hauled in front of management on a regular basis to explain how I am going to make the problem go away. Now all I need is a solution..... What type of filler do you have and what version of code is it running? I know it's obvious, but have you checked for duplex problems? If you find a solution I would really like to hear about it. Graydon Dodson (606) 232-6483 grdodson(a)lexmark.com Lexmark International Inc.

2 1

RE: fastboot
by Rowe, Alan 29 Sep '00

29 Sep '00

6.0 does indeed have a fast reboot option, which skips the memcheck and the load of the OS from the disk. This kicks in for panics and reboots where the OS version is still the same. Other parts of boot are faster too: WAFL replay, disk scan, ... {and, we're have more in mind..) alr -----Original Message----- From: Timothy A. McCarthy [mailto:tmac@netapp.com] Sent: Thursday, September 28, 2000 7:21 PM To: Todd C. Merrill Cc: toasters(a)mathworks.com Subject: Re: fastboot If it is any consequence, when 6.0.1 or later is loaded on your machine, it appears to have a "fastboot" type mechanism. It appears to skip POST & memory, just boots ontap from memory. --tmac "Todd C. Merrill" wrote: > SunOS used to have a `fastboot` command that skipped filesystem checks > (?) on bootup. HP-UX machines have a PROM setting FASTBOOT to skip > memory checks on bootup. > > Anything equivalent on a filer (skipping memory tests, not filesystem > checks, that is!)? > > With 3 GB of memory to check on boot, it takes (min:sec) 1:11 of a > total boot time of 2:15. Downtime can be reduced by 50% by just > skipping the memory test! > > It may not be a good thing in production, but during installation and > configuration, it gets to be tiring. > > 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 > --- -- ******All New Numbers!!!****** ************* ************* Timothy A. McCarthy --> System Engineer, Eastern Region Network Appliance http://www.netapp.com 240-268-2034 Office \ / Page Me at: 240-268-2001 Fax \/ 888-971-4468

1 0

fastboot
by Todd C. Merrill 29 Sep '00

29 Sep '00

SunOS used to have a `fastboot` command that skipped filesystem checks (?) on bootup. HP-UX machines have a PROM setting FASTBOOT to skip memory checks on bootup. Anything equivalent on a filer (skipping memory tests, not filesystem checks, that is!)? With 3 GB of memory to check on boot, it takes (min:sec) 1:11 of a total boot time of 2:15. Downtime can be reduced by 50% by just skipping the memory test! It may not be a good thing in production, but during installation and configuration, it gets to be tiring. 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 ---

2 1

Ultra 1 and NFS
by Tuc 29 Sep '00

29 Sep '00

Hi, Would like to hear, OFF LIST, of anyone who's used NFS off a Sun Ultra 1 (170E especially) for a high volume web site. (4-5 Mb/s continuous out the front end). Thanks, Tuc/TTSG

1 0

RE: fastboot
by Knight, Graham 28 Sep '00

28 Sep '00

There's no automatic way to do it, but you can hit ESC on the console and it will skip the test. 6.0 has a warm reboot feature that skips the memory test completely. Graham -----Original Message----- From: Todd C. Merrill [mailto:tmerrill@mathworks.com] Sent: Thursday, September 28, 2000 2:47 PM To: toasters(a)mathworks.com Subject: fastboot SunOS used to have a `fastboot` command that skipped filesystem checks (?) on bootup. HP-UX machines have a PROM setting FASTBOOT to skip memory checks on bootup. Anything equivalent on a filer (skipping memory tests, not filesystem checks, that is!)? With 3 GB of memory to check on boot, it takes (min:sec) 1:11 of a total boot time of 2:15. Downtime can be reduced by 50% by just skipping the memory test! It may not be a good thing in production, but during installation and configuration, it gets to be tiring. 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

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 September 2000