toasters

toasters@lists.teaparty.net

13520 discussions

CIFS UMASK
by Travis Zadikem 11 Nov '99

11 Nov '99

I as wondering if anyone knew of a way to set the default umask for somebody connecting via cifs. I do not want to use NFS and was not sure if this was possible or not. -- Travis A. Zadikem Senior Network Engineer PH: (303)-415-6175 Fax: (303)-786-9190 A mind is like a garden it only grows when fed and watered correctly.

1 0

Re: AW: 'Loop break detected' followed by failover
by alexei＠mindspring.net 11 Nov '99

11 Nov '99

bentele(a)mtu-friedrichshafen.com writes: > Replacing motherboard and FC-Adapter-Card at last solved the > problem, after we replaced all cables, all shelves of this loop, and about 3 > disks. One of my main complaints about the current fcal implementation for the filers is that there is no visual indicator of loop status. I know NetApp is working toward addressing this, but it would have been nice to have from the start. I wish fcal were more like token ring or fddi and that the loop were "self healing". When I had an LRC fail on an fcal shelf, there was no way of finding which LRC (used process of elimination) was the culprit, as the entire loop was offline, not just the failed shelf and those after it. Alex

5 4

Fast ENet cards for F330 and F540
by Walsh, Warren (MN65) 11 Nov '99

11 Nov '99

Hi All - We've got two toasters, a F330 and F540. They're currently networked with FDDI, but we would like to migrate to 100BaseT. NetApp has EOL'd these models, even thought they're three years old, and does not sell these parts. Anyone have suggestions for finding an alternate vendor for NetApp NICs? Or a recommendation for a used/surplus dealer? Thanks in advance. -warren Warren M. Walsh Honeywell Technology Center 612-951-7837 walsh_warren(a)htc.honeywell.com

1 0

Two files with same name under NFS
by Stephen C. Losen 11 Nov '99

11 Nov '99

We are running ONTAP 5.2.3D1 in a mixed CIFS and NFS environment. Recently we encountered a directory that had two different files with the same name under NFS. This was reported by ls -ali | grep NEW 1176207 -rwxr-xr-x 1 1224 1224 674 Nov 10 10:32 NEW2.GIF 3907524 -rwxr-xr-x 1 1224 1224 674 Nov 10 10:32 NEW2.GIF Yes, we checked very carefully and there are no spaces or other unprintable characters in the names. Not trusting "ls" I even wrote a little perl script that calls readdir to print out the filenames and they are indeed identical. Actually, this ls output is erroneous because the two files have different permissions and mod time. Still, this does show the different inode numbers, indicating two distinct files. From W98 you can see these are two different files. One is named NEW2.GIF and the other is named NEW2~0.GIF. And the mod times are indeed different. So I conclude that we have a filename mapping problem where two different files map to the same NFS name. Is this a normal situation that should be expected periodically, or should this "never happen"? We know that under NFS you can create two files with the same spelling but different capitalization, but these are not allowed under CIFS. So when a NFS dir containing such conflicts gets converted to CIFS, the filenames are "massaged" by having ~number appear in the CIFS name. However, we couldn't come up with a repeat-by where we could create two files under CIFS with the same NFS name. Anyone else figure out how to do it? Also, once you have a situation like the above, it seems like it's a toss up as to which of the two files you see under NFS. Running ls -li NEW2.GIF on one NFS client showed one of the inums while running the same command on another NFS client showed the other. So this could cause confusion. Has anyone else experienced this? Steve Losen scl(a)virginia.edu phone: 804-924-0640 University of Virginia ITC Unix Support

2 1

Re: Failure of rm -rf
by Aimee Schmidt 10 Nov '99

10 Nov '99

> Since my original mail I've discovered that the problem > is also occuring on another filer which is still running > 5.2.2P1. I'm now wondering if it's more related to running > Solaris 2.7 - the Sun system on which we now regularly see the > problem was upgraded to 2.7 a few weeks ago. > > My admin hosts, on which I see the problem, remain at 2.5.1 and even > 2.5 (horrors). Try installing the appropriate Solaris patches and tune NFS/DNLC parameters. This will improve performance by an order of magnitude or so. Patches: 5.6 sparc - 105720-08 5.6 i386 - 105721-08 5.7 sparc - 106541-06 5.7 i386 - 106542-06 Tunings (for /etc/system): set nfs:nfs_nra = 10 set nfs:nfs3_nra = 10 set nfs:nfs_max_threads = 24 set nfs:nfs3_max_threads = 24 set ncsize=8192 Aimee _____________________________________________________ Aimee Schmidt aimee(a)netapp.com Software Test Engineer Voice: 408.822.6840 Network Appliance Fax: 408.822.4559 / |\ / | \ "We cannot direct the wind __o / | \ but we can adjust our sails" _`\<,_ / | \ (_)/ (_) ---------- \________/ |_|

2 2

RE: 'Loop break detected' followed by failover
by tomi.rautio＠nokia.com 10 Nov '99

10 Nov '99

Hi there, we also have loop break couple months ago and it stays mystery. F740 single head, 5.1.2, FC-AL 18 GB disks in 6 shelves. We test all disk shelves one shelf at time with 2 disks and all works ok, but adding all 6 shelves loop stays broken. Swapping one shelf nro3 and problem disappears. What disk fw do you have at that time, I have pretty old. -TomiR- tomi.rautio(a)nokia.com > -----Original Message----- > From: EXT bentele(a)mtu-friedrichshafen.com > [mailto:bentele@mtu-friedrichshafen.com] > Sent: 10. November 1999 11:18 > To: toasters(a)mathworks.com; jay(a)cimedia.com > Subject: AW: 'Loop break detected' followed by failover > Importance: High > > > Hi Jay, > > we also had a ' isp2100_timeout]: Resetting ISP2100 in > slot ..' a > few weeks ago. > F740 , DOT 5.2.3, FC-AL 18 GB, Gbit Card. > > !! Be careful !! > > Replacing motherboard and FC-Adapter-Card at last solved the > problem, after we replaced all cables, all shelves of this > loop, and about 3 > disks. > > > > Mit freundlichen Grüßen > > Markus Bentele > MTU Friedrichshafen GmbH > * 07541-90-2654 > * bentele(a)mtu-friedrichshafen.com > > > ---------- > > Von: Jay Soffian[SMTP:jay@cimedia.com] > > Gesendet: Mittwoch, 10. November 1999 08:07 > > An: toasters(a)mathworks.com > > Betreff: 'Loop break detected' followed by failover > > > > > > I've opened a case with NOW on this. > > > > One of my filers (F740/512MB/28x9GB disks/DOT 5.2.3) > tonight just did > > this: > > > > Tue Nov 9 19:00:01 EST [subzero: statd]: 7:00pm up 44 days, 13:45 > > 2570782327 NFS ops, 0 CIFS ops, 0 HTTP ops > > Tue Nov 9 19:16:46 EST [subzero: isp2100_main]: Loop break > detected on > > ISP2100 in slot 1. > > Tue Nov 9 19:16:50 EST [subzero: isp2100_timeout]: > Resetting ISP2100 in > > slot 1 > > Tue Nov 9 19:19:14 EST [subzero/viking: cf_takeover]: > relog syslog Tue > > Nov 9 19:17:15 EST [subzero: isp2100_timeout]: Resetting > ISP2100 in slot > > 1 > > Tue Nov 9 19:19:14 EST [subzero/viking: cf_takeover]: > relog syslog Tue > > Nov 9 19:17:27 EST [subzero: isp2100_timeout]: Resetting > ISP2100 in slot > > 1 > > Tue Nov 9 19:19:15 EST [subzero/viking: asup_main]: > Cluster Notification > > mail sent > > > > No core dump, I found the filer at an 'ok' prompt. > > > > I rebooted the filer, did a cf giveback a few minutes later and all > > appears fine now. > > > > Anything recommended besides checking that all cables are tight and > > all drives are fully seated? > > > > I couldn't find any bugs relating to this on NOW (except a > bug in the > > Diagnostics not resetting the FC-AL loop properly when a loop break > > occurs). I've heard rumors that some F740's were shipped with bad > > on-board FC-AL controllers, but this F740 has been in operation for > > over a year w/o any problems (it's only been clustered since June > > though). > > > > Suggestions? > > > > j. > > >

1 0

'Loop break detected' followed by failover
by Jay Soffian 10 Nov '99

10 Nov '99

I've opened a case with NOW on this. One of my filers (F740/512MB/28x9GB disks/DOT 5.2.3) tonight just did this: Tue Nov 9 19:00:01 EST [subzero: statd]: 7:00pm up 44 days, 13:45 2570782327 NFS ops, 0 CIFS ops, 0 HTTP ops Tue Nov 9 19:16:46 EST [subzero: isp2100_main]: Loop break detected on ISP2100 in slot 1. Tue Nov 9 19:16:50 EST [subzero: isp2100_timeout]: Resetting ISP2100 in slot 1 Tue Nov 9 19:19:14 EST [subzero/viking: cf_takeover]: relog syslog Tue Nov 9 19:17:15 EST [subzero: isp2100_timeout]: Resetting ISP2100 in slot 1 Tue Nov 9 19:19:14 EST [subzero/viking: cf_takeover]: relog syslog Tue Nov 9 19:17:27 EST [subzero: isp2100_timeout]: Resetting ISP2100 in slot 1 Tue Nov 9 19:19:15 EST [subzero/viking: asup_main]: Cluster Notification mail sent No core dump, I found the filer at an 'ok' prompt. I rebooted the filer, did a cf giveback a few minutes later and all appears fine now. Anything recommended besides checking that all cables are tight and all drives are fully seated? I couldn't find any bugs relating to this on NOW (except a bug in the Diagnostics not resetting the FC-AL loop properly when a loop break occurs). I've heard rumors that some F740's were shipped with bad on-board FC-AL controllers, but this F740 has been in operation for over a year w/o any problems (it's only been clustered since June though). Suggestions? j.

1 0

Failure of rm -rf
by Dave Atkin 09 Nov '99

09 Nov '99

Since we moved to 5.3 (actually 5.3.2R1P1) we see occasional failures in various Unix automated management procedures. I've finally traced this to the "rm -rf" command failing. On Solaris systems it fails with: rm -rf /<filer>/x rm: Unable to remove directory /<filer>/x/y/z: File exists On SGI systems the slightly more meaningful error message is /<filer>/x/y/z: Directory not empty However, just repeating the rm -rf command once more works perfectly and the directory tree has gone. I don't think it's anything to to with CIFS file locking since some of the directories are old and have not been used for a long time. Has anyone else seen this? Dave Atkin ------------------------------------------------------ Dave Atkin, Head of Technical Services Computing Service, University of York, YORK YO10 5DD Phone: +44-1904-433804 (ddi) Fax: +44-1904-433740 Email: D.Atkin(a)york.ac.uk ------------------------------------------------------

6 7

RE: the latest on NDMP and NetBackup?
by Melvin, Grant 09 Nov '99

09 Nov '99

Hi Tony, We have just updated our external web site with information regarding NetBackup & Data Ontap compatibility at: http://now.netapp.com/knowledge/contents/TIP/TIP_605.shtml Other certification matrices available on NOW are: Legato BudTool: http://now.netapp.com/knowledge/contents/TIP/TIP_601.shtml Workstation Solutions Quick Restore: http://now.netapp.com/knowledge/contents/TIP/TIP_698.shtml Since I think this document will be useful to NetApp users, I hope you don't mind, but this seems like a good opportunity to also introduce our new white paper on "Data Protection Strategies for Network Appliance Filers" at: http://www.netapp.com/tech_library/3066.html Cheers, Grant -----Original Message----- From: Rudie, Tony [mailto:Tony.Rudie@fmr.com] Sent: Tuesday, November 09, 1999 10:28 AM To: 'toasters(a)mathworks.com' Subject: the latest on NDMP and NetBackup? I see postings of some months back in the archives about this, but I wonder what the latest is? We have a cluster of 740s running DOT 5.3D11 Each filer has an Overland Data DLT7000 with 15-tape mini library. Our Solaris 2.6 NetBackup server (running NetBackup 3.12) seems to be directing NDMP backups to the local tape drives without any substantial problems. Have I got a "lucky guess" of an OS rev here? Is anyone doing NetBackup NDMP on any other release level successfully?

1 0

How to subscribe
by Pierre Maubert 09 Nov '99

09 Nov '99

Can somebody remind me how to subscribe to that list. I forgot thge process. thanks -- Regards, Pierre . +------------------------------------------------------+ | Pierre Maubert, Sys_Admin Texas Instruments France | | email:p-maubert@ti.com Tel: +33 49322.2681 | | Fax: +33 49202.4669 Pager: 0606498982 | +------------------------------------------------------+

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