toasters June 1998

toasters@lists.teaparty.net

36 participants
44 discussions

Re: always safe to delete dump snapshots?
by varun＠netapp.com 25 Jun '98

25 Jun '98

> From sirbruce(a)ix.netcom.com Thu Jun 25 06:45:51 1998 ... > Well, there USED to be an old bug that's been around since the > beginning that trying to delete one while a dump was in progress > would crash the filer. This bug was even mentioned in bold > letters in the admin guide (either in the snapshot or the dump > sections). Assuming they've fixed it to do what you say, then > you're correct. > This is bug 650. Fixed since release 4.2. You should get a "Snapshot in use by dump." message if you attempt to delete a snapshot that's being dumped.

1 0

Re: always safe to delete dump snapshots?
by sirbruce＠ix.netcom.com 25 Jun '98

25 Jun '98

On 06/25/98 01:38:27 you wrote: > >Is it always safe to attempt to delete a snapshot_for_dump.<num>? > >Another way to phrase my question -- it will *never* succeed when a >dump is in progress, right? > >Yes, I know it's supposed to not succeed, but since I'm writing a >program to automatically delete snapshots, I'm exercising more >paranoia than usual. Well, there USED to be an old bug that's been around since the beginning that trying to delete one while a dump was in progress would crash the filer. This bug was even mentioned in bold letters in the admin guide (either in the snapshot or the dump sections). Assuming they've fixed it to do what you say, then you're correct. If they haven't, then you don't want to automatically delete those files, unless you have some way of knowing ahead of time that they are no longer associated with a dump process (say, one that failed in some ungraceful way). Since this usually happened because of a crash, one thing I used to do was include an automatic snap delete at the end of the rc file to delete the snapshot_for_dump after the filer had started up. The appearance of the snapshot_for_dump.n mechanism broke that... I made the suggestion that having the OS automatically delete those might be a good idea, but on the other hand it might not... the user may really want to restart the backup off that old image, rather than taking a new one right at that moment. Bruce

1 0

always safe to delete dump snapshots?
by Daniel Quinlan 25 Jun '98

25 Jun '98

Is it always safe to attempt to delete a snapshot_for_dump.<num>? Another way to phrase my question -- it will *never* succeed when a dump is in progress, right? Yes, I know it's supposed to not succeed, but since I'm writing a program to automatically delete snapshots, I'm exercising more paranoia than usual. Thanks. - Dan

1 0

NFS performance question
by Alexei Rodriguez 24 Jun '98

24 Jun '98

Hey folks. I have a PII-400 machine running Solaris x86 2.6 which is using the dnet0 interface (built in interface on the motherboard) for the mounts. The mount that is giving us some problems is off of a f630 running 4.3.4D5 over gigabit. The PII has a 10/100 interface (adaptec I believe). The behavior I am seeing is as follows: - large file ops (like cat /dev/zero > foo) are bursty - iostat shows the filer 100% busy but the filer is not breaking a sweat. The stats: root@sealion:~/ # iostat -xn 2 extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 fd0 1.9 0.6 18.5 4.0 0.0 0.0 17.8 10.5 0 2 c0t0d0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 4.5 0 0 maytag:/home 0.0 0.0 0.0 0.0 0.0 0.0 0.0 27.9 0 0 maytag:/export/cim 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/httpd 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/logarchive 0.0 41.8 0.0 331.8 660.8 3.1 15796.9 74.4 20 62 whirlpool:/export/c0 0.0 0.0 0.4 0.0 0.0 0.0 0.1 94.9 0 0 maytag:/export/depot/col.x86-solaris26 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sealion:vold(pid261) extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 fd0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/home 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/cim 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/httpd 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/logarchive 0.0 0.0 0.0 0.0 0.0 4.0 0.0 0.0 0 100 whirlpool:/export/c0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/depot/col.x86-solaris26 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sealion:vold(pid261) extended device statistics r/s w/s kr/s kw/s wait actv wsvc_t asvc_t %w %b device 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 fd0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 c0t0d0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/home 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/cim 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/httpd 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/logarchive 0.0 0.0 0.0 0.0 0.0 4.0 0.0 0.0 0 100 whirlpool:/export/c0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 maytag:/export/depot/col.x86-solaris26 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0 sealion:vold(pid261) ^C root@sealion:~/ # root@sealion:~/ # nfsstat -m /content from whirlpool:/export/c0 Flags: vers=3,proto=udp,sec=sys,hard,intr,link,symlink,rsize=8192,wsize=8192,retrans=5 Lookups: srtt=7 (17ms), dev=3 (15ms), cur=2 (40ms) Reads: srtt=2 (5ms), dev=2 (10ms), cur=1 (20ms) Writes: srtt=7 (17ms), dev=3 (15ms), cur=2 (40ms) All: srtt=7 (17ms), dev=3 (15ms), cur=2000 (40000ms) I was just wondering if anybody else had seen this sort of behavior on their end. I suspect this is hardware on my end (cable, card, etc) but swapping has not helped. Thanks. Alexei

1 0

Re: 'quota resize' - any way around it ?
by sirbruce＠ix.netcom.com 22 Jun '98

22 Jun '98

On 06/22/98 13:44:18 you wrote: >- just accept the fact that NetApp doesn't consider this wish to very >important and turn the quotas on/off as often as is feasible. So long as once/day was acceptable, this is what I would do. But if not, then... >- preload the /etc/quotas file with entries for all possible UIDs, then >just change the quota as they request it. This way the /etc/quotas will >always be the same length and contain the same number of users. ... this is probably what I would do. Assuming that's not too many UIDs that it's computationally expensive. Depending on how many users I expect to reasonably have, I might start with a smaller number and then add new ones in blocks ahead of their actual use (and then do a quota off/on that night). Bruce

1 0

Re: ATM and Fore SPANS failover
by Barbara Naden 18 Jun '98

18 Jun '98

At 10:35 PM 6/17/98 -0400, David B. Ritch wrote: >Actually, etherchannel is supported by Sun, Auspex, and Cisco. There >may be others, but those are the one that I know of. > >David Ritch > EtherChannel support is in the DATAOntap 5.1 release and is currently in external test. Barbara Naden >Alexei Rodriguez wrote: >[...] >> Sounds like etherchannel... I think Alteon was trying this with their Gigabit >> stuff; unfortunately, no other vendor supports this feature. > >

1 0

Re: CIFS file locking
by Paul Albers 18 Jun '98

18 Jun '98

Michael, You can also use "cifs sessions *" to see all the files that are open/locked by all the users. One limitation of this command is that it is not available to 'rsh'. So, you would have to run this from a telnet session and weed through the output, or capture the console output to a file that you could then parse for the file. Regards, Paul Albers At 12:31 PM 6/18/98 +0100, you wrote: >I think the command "cifs cessions username" does what you want: > >toaster> cifs sessions >Server Registers as 'TOASTER' in group 'NETAPP' >UNIX compatible Access Control is being used >Using the UNIX password database for authentication >======================================== >PC (user) #shares #files >ANDREW (abond) 1 1 >toaster> cifs sessions andrew > >users > shares/files opened > >ANDREW (abond) > HOME > Read-denyN - \ajb.1 > >Also, from release 5.1 (due later this month) you can see this information >from the NT Server Manager (In Use button). > >Regards, >Andrew Bond, UK Systems Engineer > >At 11:29 am 17-06-98 -0700, you wrote: >>I know that spreedsheet applications opened from the PC create >>a lock on that file that prevents all other access. But is there some >>way to find out who has that particular file open? >> >>On the toaster, I can find who has files opened - but that doesn't >>help much. >> >>This spreedsheet data was migrated from Novel. On Novel, you >>have the ability to see who has what file opened. >> >>Any ideas? >> >> >>-- >> ------------------------------------------------------------------------ >> >> Michael McBride CommQuest Technologies,Inc. >> >> Senior Unix Administrator 527 Encinitas Boulevard >> >> mcbride(a)CommQuest.com Encinitas, CA. 92024-3740 >> >> Voice: (760) 634-6239 Fax: (760) 634-6138 >> >> >> >> >> > >

1 0

CIFS file locking
by Mike McBride 18 Jun '98

18 Jun '98

I know that spreedsheet applications opened from the PC create a lock on that file that prevents all other access. But is there some way to find out who has that particular file open? On the toaster, I can find who has files opened - but that doesn't help much. This spreedsheet data was migrated from Novel. On Novel, you have the ability to see who has what file opened. Any ideas? -- ------------------------------------------------------------------------ Michael McBride CommQuest Technologies,Inc. Senior Unix Administrator 527 Encinitas Boulevard mcbride(a)CommQuest.com Encinitas, CA. 92024-3740 Voice: (760) 634-6239 Fax: (760) 634-6138

2 1

Re: posting history - who's wordy and who's quiet?
by sirbruce＠ix.netcom.com 18 Jun '98

18 Jun '98

On 06/17/98 14:07:10 you wrote: > >i was looking for a reason to have fun with perl modules for chopping up >email addresses, so here's the prolixity summary for the lifetime of the >list. i've cut-off at ten posts. > > 99 Brian Tao > 86 sirbruce(a)ix.netcom.com > 16 Bruce Sterling Woodcock Actually, if you combine mine, I managed to narrow out Brian for a minor (pyrrhic?) victory. Bruce

1 0

ATM and Fore SPANS failover
by Scott Miller 18 Jun '98

18 Jun '98

This is actually a request/question for netapp, but I'm hoping to generate a few "me too"'s from the list. We're a large (1200 systems) ATM shop. For various reasons, we're using Fore SPANS signalling, and will be for awhile. The move to standards-based ATM is going to be ugly, and we (and the standards) aren't quite ready yet. NetApp supports SPANS ATM, using Fore's PCI card and a port of the SPANS protocol engine in their ATM drivers. This is good. But, there are two features of Fore SPANS that NetApp doesn't support, that we rely on. This message is a request to NetApp to consider adding support for these two features: 1. load balancing. Fore SPANS on other platforms (IRIX, Solaris) provides interface aggregation such that multiple ATM interfaces on the same host are used equally. This is connection-based load balancing, in that new connections are assigned round-robin to all the interfaces in a given load balance group, on a given machine. On some platforms, all interfaces in a given system can have the same IP address, which simplifies management, and means there is one "view" of a multi-interface machine from the outside. Routing gets simpler, too. We can get some balancing using static routing configuations that spreads the load over all the interfaces in a system, but it's not quite the same. Plus, support for load balancing may help provide support for: 2. fail over. If an interface, or switch fabric, or other component fails, Fore SPANS will fail an interface, and all the connections will be re-established on the other available interfaces. Our core switch architecture is such that each server has multiple ATM "feet", in different switches and backplanes, so we've got fault tolerance with automatic failover when somthing in the network path croaks. It's the failover that we're most interested in, for the fault tolerance and redundancy reasons. load balancing makes administration easier, and helps us better utilize the switch architecture we have in place. So, NetApp, what are the chances of getting SPANS fail over and load balancing in your ATM implementation? -Skottie -- ----- Scott Miller | Walt Disney Feature Animation skottie(a)fa.disney.com | Digital Studio Technology

3 2

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 June 1998