toasters

toasters@lists.teaparty.net

13514 discussions

Write permissions on CIFS share
by Ian F. Jarvis 18 Oct '01

18 Oct '01

NetApp gurus, I have a scenario where I am unable to gain write access to a CIFS share on our Filer for a local Filer account. I can map a drive, read and execute with no problems but cannot write to the share. Due to our security policy, our Windows NT boxes and Filer are in workgroup and not in a domain. The Filer is being used as a store of log data from servers and not for any 'user' data. PlainTextPasswords is enabled on the Windows NT machines. The user account in question has been added locally to the Filer and the share has a mixed security style. The share has 'everyone' access with full control. I have attempted to map the user account to pcuser and even root in usermap.cfg with no luck. I am able to write when mapping the drive as root. Although the user account shows up with the useradmin userlist command, it is not showing in /etc/passwd. I'm not sure if this is an issue or not. Hopefully there is something simple I am missing here. Data OnTap version: 6.0.1R3 Licenses: CIFS, NFS Thanks in advance!! Ian Jarvis NOC Systems Engineer Aether Systems Inc. 443-394-5029 <<...OLE_Obj...>>

1 0

remove
by Morgan, Joshua 18 Oct '01

18 Oct '01

remove Joshua Morgan PH: (864) 331-7939 jmorgan(a)trivergent.com

1 0

Re: ONTAP with RedHat linux
by Steve Losen 18 Oct '01

18 Oct '01

I am running RedHat 7.1 and NFS mounting a netapp F820 running 6.0.1R3. Things work pretty smoothly, but I have experienced the same problem as another poster (sorry, lost the message) where NFS writes occasionally delay and a "NFS server not responding" error is logged. I have not tried the rsize=1023,wsize=1023 work around. I have experienced the same problem with NFS servers other than Netapp, including a IBM RS6000 running AIX. Non Linux NFS clients are having no delay problems with the Netapp filers, so I'm pretty sure it is on the Linux end. For awhile I thought the NIC on my Linux box had botched the speed/duplex negotiation with the ethernet switch. Our network folks can tell me what speed the switch port has negotiated, but I don't know how to check my NIC from Linux. The network folks tell me they see no errors on my switch port when I experience NFS delays. I don't seem to have any other network problems, so I doubt this is the problem. I have been able to duplicate the problem on a second Linux box. However, on a third box, essentially identical to mine and also running RH 7.1, I could not duplicate it. A couple of things to be aware of with RedHat Linux and NFS. Prior to RedHat 7.0, only NFS v2 was supported. Furthermore, Linux only supported 16 bit uids and gids. We have a lot of files on our Netapp filers with uids greater than 65535. RedHat 7.1 supports NFS v3 and 32 bit uids and gids. 32 bit uids are critical in our environment. I administer our filers and when I was running RH 6.2, I could not get accurate file owner information with "ls" and I could not "chown" files to uids over 65535, so I had to use another unix box for filer administration. Now I can do it all from my Linux box. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support

1 0

ONTAP with RedHat linux
by Kunihiko Motoyoshi 18 Oct '01

18 Oct '01

Hello, Dose anyone had experience about filer with RedHat 7.1 or later ? I know RedHad 6.x working with ONTAP. Please let me know, If you had experience, What ONTAP version you use ? Thank you, -Motoyoshi -- Kunihiko Motoyoshi Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 Storage Group / Product Support Dept. CTC Technology

5 5

NIS groups not showing up
by Roman.Ustoyev＠chase.com 17 Oct '01

17 Oct '01

Hi Lance, Did you find a solution to this problem? We are running 6.1R1 and have the same issue. As of today there is no fix for this, the only workaround is to have the groups locally on the filer, but that defeats the whole purpose for NIS. The problem has to do with the way YP stores its maps using dbm format (I think NIS+ in yp compatibility mode emulates dbm for yp clients). As far as I know there is a limitation on a single entry in dbm file which can not exceed 1024. It would be nice if filers could read NIS+, but I don't think this will happen. Can anyone else comment on that? Roman. >Thanks to all for your help. As it turns out the problem is if a group line >on your NIS+ server exceeds 1024 chars the filer will stop processing the NIS >entry once it sees that line. So all groups after that are non-existant! > >I understand this is fixed in 6.0 but don't know for sure. If not there should >atleast be a warning in the log file that says you may have exceeded the 1024 >char limit in a particular NIS map. > >Hi Lance, > > When the group cache is created, if there are duplicate entries, a message will >be logged. Are there any such messages logged? > >Thanks, >-Devi > > > >-----Original Message----- >From: Lance R. Mehle [mailto:mehlel001@hawaii.rr.com] >Sent: Saturday, October 14, 2000 3:13 PM >To: Toasters (E-mail) >Subject: NIS groups not showing up > > >Hi all, > >I have a problem that I was wondering if any of you have seen. > >We have a little over 2000 groups in our NIS+ environment. When I check the >nis_cache file on the filer about 399 are missing. A ypgroup also shows the >group(s) missing from the filer although a ypmatch can find the group(s). >It also appears that the same groups are effected all the time. > >The groups are fine on the UNIX side. > >Help! > >Lance

1 0

Re: ONTAP with RedHat linux
by Jered Heeschen 17 Oct '01

17 Oct '01

Ugh, my bad - That should have read less than a kilobyte. Sorry about that. That would be mount options like rsize=1023,wsize=1023. Jered Frank Smith <fsmith(a)hoovers.com> on 10/17/2001 03:40:57 PM To: Jered Heeschen/Raleigh/Contr/IBM@IBMUS cc: "toasters(a)mathworks.com" <toasters(a)mathworks.com> Subject: Re: ONTAP with RedHat linux How do you read/write less than a byte? Frank --On Wednesday, October 17, 2001 15:14:58 -0400 Jered Heeschen <heeschen(a)us.ibm.com> wrote: > I've had users with RedHat 6.2 through 7.1 connecting to our filers, > running various versions of ONTAP 6.x. The only strangeness we've run into > seems more related to our network - machines running the Linux kernel 2.4.x > tend to hang on NFS writes when using UDP and a packet size greater than a > byte. It started around the time CodeRed starting making the rounds, and > since I haven't been able to talk to whoever's in charge of the larger > network here, we've just worked around it - I assume they're filtering some > types of UDP traffic, since around that time we had trouble serving NFS > from some Linux boxes that hadn't given us trouble previously. > > I'm not sure what kernel 2.4 does differently from 2.2 when making NFS > connections, but the workaround has been either to use TCP instead of the > default UDP when mounting NFS shares, or to set the rsize and wsize to less > than a byte. > > Jered > > > > Kunihiko Motoyoshi <k_moto(a)ctc-g.co.jp>@mathworks.com on 10/17/2001 > 09:06:16 AM > > Sent by: owner-toasters(a)mathworks.com > > > To: "toasters(a)mathworks.com" <toasters(a)mathworks.com> > cc: chinatsu(a)ctc-g.co.jp, ue(a)ctc-g.co.jp, "Syouichi.Nakayama" > <syou(a)ctc-g.co.jp> > Subject: ONTAP with RedHat linux > > > > Hello, > > Dose anyone had experience about filer with RedHat 7.1 or later ? > I know RedHad 6.x working with ONTAP. > > Please let me know, > If you had experience, What ONTAP version you use ? > > Thank you, > -Motoyoshi > -- > Kunihiko Motoyoshi > Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 > Storage Group / Product Support Dept. > CTC Technology > -- Frank Smith fsmith(a)hoovers.com Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501

1 0

Re: ONTAP with RedHat linux
by Jered Heeschen 17 Oct '01

17 Oct '01

I've had users with RedHat 6.2 through 7.1 connecting to our filers, running various versions of ONTAP 6.x. The only strangeness we've run into seems more related to our network - machines running the Linux kernel 2.4.x tend to hang on NFS writes when using UDP and a packet size greater than a byte. It started around the time CodeRed starting making the rounds, and since I haven't been able to talk to whoever's in charge of the larger network here, we've just worked around it - I assume they're filtering some types of UDP traffic, since around that time we had trouble serving NFS from some Linux boxes that hadn't given us trouble previously. I'm not sure what kernel 2.4 does differently from 2.2 when making NFS connections, but the workaround has been either to use TCP instead of the default UDP when mounting NFS shares, or to set the rsize and wsize to less than a byte. Jered Kunihiko Motoyoshi <k_moto(a)ctc-g.co.jp>@mathworks.com on 10/17/2001 09:06:16 AM Sent by: owner-toasters(a)mathworks.com To: "toasters(a)mathworks.com" <toasters(a)mathworks.com> cc: chinatsu(a)ctc-g.co.jp, ue(a)ctc-g.co.jp, "Syouichi.Nakayama" <syou(a)ctc-g.co.jp> Subject: ONTAP with RedHat linux Hello, Dose anyone had experience about filer with RedHat 7.1 or later ? I know RedHad 6.x working with ONTAP. Please let me know, If you had experience, What ONTAP version you use ? Thank you, -Motoyoshi -- Kunihiko Motoyoshi Phone:+81-3-3649-4937 / Fax:+81-3-3649-6425 Storage Group / Product Support Dept. CTC Technology

2 1

ontap 6.1x
by neil lehrer 17 Oct '01

17 Oct '01

hi, my management is very interested in doing quotas for our nt users. that requires 6.1x. does anyone have any comments on the 6.1x releases? we are nfs,cifs,nis,nt 4,atm,clustered 760's. thanks. --

5 6

RE: root volume
by White, Lance 17 Oct '01

17 Oct '01

Good point...then don't use vol copy, but instead just the /etc dir across the mount. I returned with a "create a new volume" because Debbie wanted to REDUCE her existing volume (something that we know we can't do, so creation of a new one is the best way). If an existing 2 disk volume was already in your system, then go for that instead, as Michael explains. Lance -----Original Message----- From: Honeycutt, Michael [mailto:MichaelHoneycutt@NC.SLR.com] Sent: Wednesday, October 17, 2001 8:46 AM To: 'White, Lance'; 'Lane, Debbie'; toasters(a)mathworks.com Subject: RE: root volume You dont need spares to do it. You can copy the /etc directory to another volume and set it as root. Thats what I did to remove 2 drives from vol0. -----Original Message----- From: White, Lance [mailto:Lance.White@netapp.com] Sent: Wednesday, October 17, 2001 11:12 AM To: 'Lane, Debbie'; toasters(a)mathworks.com Subject: RE: root volume Assuming you still have a couple of spares... 1. Create your new root volume on the new drives (let's call it vol1 for this article) 2. Issue the offline command on vol1 3. If running OnTap 5.3.6R2 or lower, reboot the Filer. If running OnTap 6.0 or greater, carry on... 4. Delete the data that you no longer want on vol0 5. Initiate the vol copy command (vol copy start vol0 vol1) 6. Now, make vol1 the root volume (vol options vol1 root) 7. Reboot the Filer to boot from vol1 8. Rename vol0 to mydata (vol rename vol0 mydata) 9. Rename vol1 to vol0 (vol rename vol1 vol0) 10. Reboot 1 last time so all shares & exports get mounted/exported properly 11. Offline mydata, and if running OnTap 6.0 or higher, destroy mydata to put mydata disks back to spare state -----Original Message----- From: Lane, Debbie [mailto:Debbie.Lane@intermec.com] Sent: Wednesday, October 17, 2001 7:59 AM To: toasters(a)mathworks.com Subject: root volume Our filers vol0 contains user data. We are going to be getting rid of about 80GB of this data. We then want to take some of the disk out of vol0 and put them in another volume. What is the best way to go about this? I have limited filer experience. Thanks for your help. --Debbie

2 1

swap broken disk/still broken status
by Kris Haislip 17 Oct '01

17 Oct '01

Hello all, I have a F760 running Data Ontap 5.3.6R1. Recently, one of the disks has entered into a broken status. I received a replacement drive and proceeded to swap out. I gave the filer plenty of time to recognize the drive pull. However, when I pulled the drive, I received no notification on console or in the messages file confirming a drive pull/empty slot. Of course placing the new drive in, results in an unchanged broken status. sysconfig -a reports the drive as unloaded. Is "Unloaded" the correct status for broken disk? 16: SEAGATE ST318203FC NA05 17.0GB (Unloaded) Any ideas? -- Kris Haislip <khaislip(a)interliant.com> UNIX System Administrator Interliant, Atlanta

2 1

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