toasters April 1999

toasters@lists.teaparty.net

117 participants
153 discussions

Re: Need help regarding quotas
by sirbruce＠ix.netcom.com 16 Apr '99

16 Apr '99

On 04/08/99 18:51:42 you wrote: >I submitted a Request for Enhancment on how to solve this. >Basically, I asked for something along the lines of: > > * Add a flag to the per-quota-entry data structure which the > filer uses to maintain current state. If this flag is set, > it indicates if a message has already been logged about that > quota being exceeded. > > * Every time the quota entry is checked (during a disk write, > or whatever), do the following: > if (quota not exceeded) { > flag = 0 > } else { > /* quota exceeded */ > if (flag == 0) { > syslog("quota exceeded ...") > flag = 1 > } > } > I.e, don't bother logging a message if that user has already > had a message logged about them. However, if they go under > quota, clear the flag, so we get a message when they exceed > it again. > >The only response I've received (second hand) is along the lines of >``we've fixed it, but a different way''. Yeah, this has been a well known problem for years, but I had trouble getting action on it until engineers actually had to deal with the problem first hand and realized just how bad it was. As to the fix, I don't recall what it was, but I recall a proposal similar to the one you listed being considered and rejected (for example, your suggestion wouldn't work, since when the user fails to go over quota they'll generally fall right back under it, thus resetting the flag). >[Hmm; I should put support(a)netapp.com (or whatever) on autosupport; >maybe then they'll listen after getting a 30MB email message every >week ;-] I think they already filter such things. Bruce

2 1

Samba client and filers
by Garrett Burke 16 Apr '99

16 Apr '99

Hi, Anyone know of any issues with smbclient (version 1.9.18p8) and filers running CIFS (OnTap 5.2.1)? Session setup is failing. I can use smbclient to connect to my NT servers but not the filer. I notice from the debug output of smbclient that it says "Using encrypted passwords" Could this be the problem? Can't see anything on the smbclient man page to force it to use unencrypted passwords. Here's some "-d 3" output from smbclient: Connected max mux 32 max vcs 1 max raw 65536 capabilities 0x42dd Sec mode 8195 max xmt 8192 Got 8 byte crypt key Chose protocol [NT LM 0.12] Server time is Thu Apr 15 14:16:23 1999 Timezone is UTC+1.0 Password: Using encrypted passwords Session setup failed for username=<username> myname=<FreeBSD hostname> destname=TOASTER ERRSRV - ERRerror (Non-specific error code.) (Before you all say "use NFS", I'm writing some monitoring tools that will run on a FreeBSD box and will actually fetch a file from the filer and calc a CRC to ensure it's ok. This way I know the file service is available) Thanks, GB

3 2

RE: Anybody using 3com switches with NetAPP?
by Jonas Jonsson 16 Apr '99

16 Apr '99

I've used Rad, Alteon, Cisco in conjunction with NC and haven't seen this. /// Regards, Jonas -----Original Message----- From: Jaye Mathisen [mailto:mrcpu@internetcds.com] Sent: Thursday, April 15, 1999 11:50 PM To: toasters(a)mathworks.com Subject: Anybody using 3com switches with NetAPP? I have both my ports on a linkswitch 3000, at 100mb, full-duplex. ---------------------Stuff zapped------------------------------

2 1

Re: Need help regarding quotas
by Luke Mewburn 16 Apr '99

16 Apr '99

Daniel Quinlan writes: > > Exceeded quotas are also logged to /etc/messages. > This is *damned* annoying. With 2500 students all hammering one of my filers (a F330 in this case), we generally get /etc/messages.? ranging in size from 10 MB to 150 MB (yes, 150 *megabytes* in a week!) (My local NetApp tech asked to get off my autosupport because the mail was too large ;-) This causes the filer to choke (i.e, 100% load) whilst sending the `autosupport' email, and my mail program gets a bit unhappy with it. I wrote a procmail rule to trim the mail down to a more manageble 30KB: something like: :0 w: root/netapp/$LOCK * ^TOnetapp-admin(a)cs.rmit.edu.au | egrep -v '(last message repeated [0-9]+ times$|(disk|tree) quota exceeded)' | $RCVSTORE +root/netapp I submitted a Request for Enhancment on how to solve this. Basically, I asked for something along the lines of: * Add a flag to the per-quota-entry data structure which the filer uses to maintain current state. If this flag is set, it indicates if a message has already been logged about that quota being exceeded. * Every time the quota entry is checked (during a disk write, or whatever), do the following: if (quota not exceeded) { flag = 0 } else { /* quota exceeded */ if (flag == 0) { syslog("quota exceeded ...") flag = 1 } } I.e, don't bother logging a message if that user has already had a message logged about them. However, if they go under quota, clear the flag, so we get a message when they exceed it again. The only response I've received (second hand) is along the lines of ``we've fixed it, but a different way''. [Hmm; I should put support(a)netapp.com (or whatever) on autosupport; maybe then they'll listen after getting a 30MB email message every week ;-] > > I'd recommend using a userland program (on login) to regularly tell > users how close they are to exceeding their quota, in addition to > monitoring quotas for your own information. > I wrote a perl script which can do all sorts of funky reporting based on the output of `quota report', including playing ``what if'' games based on the quota report and the `/etc/quotas' file you're about to apply. It currently works for OnTAP 5.2.1, although I could probably hack support back in for 4.x if people wanted it. Checkout: http://www.cs.rmit.edu.au/~lukem/src/quotarep An aside; on our main student filer (an F330), we have nearly 6000 users, and 2500 separate quota entries; we generate an individual quota entry per student based on subject enrolment. Works quite well, although the `quota resize' takes over two minutes to complete, and I'm a bit sick of the huge messages file :/ We've had our share of quota bugs (especially the ``quota -v doesn't display anything'' problem), but in general, the NetApp quota system works well. It's definately easier to manage than standard UFS quotas (as well as the ability to recalculate on the fly; UFS quotacheck requires a quiscient filesystem to work).

3 5

RE: Anybody using 3com switches with NetAPP?
by Kinney, Roger 16 Apr '99

16 Apr '99

Please reference: http://now.netapp.com/knowledge/contents/FAQ/FAQ_1020.shtml <http://now.netapp.com/knowledge/contents/FAQ/FAQ_1020.shtml> Roger -----Original Message----- From: Jonas Jonsson [mailto:jonas.jonsson@proact.se] Sent: Thursday, April 15, 1999 3:52 PM To: 'Jaye Mathisen'; toasters(a)mathworks.com Subject: RE: Anybody using 3com switches with NetAPP? I've used Rad, Alteon, Cisco in conjunction with NC and haven't seen this. /// Regards, Jonas -----Original Message----- From: Jaye Mathisen [mailto:mrcpu@internetcds.com] Sent: Thursday, April 15, 1999 11:50 PM To: toasters(a)mathworks.com Subject: Anybody using 3com switches with NetAPP? I have both my ports on a linkswitch 3000, at 100mb, full-duplex. ---------------------Stuff zapped------------------------------

1 0

Re: Samba client and filers
by mday＠netapp.com 15 Apr '99

15 Apr '99

Garrett Burke <Garrett.Burke(a)msc.ie> wrote: > Anyone know of any issues with smbclient (version 1.9.18p8) and filers > running CIFS (OnTap 5.2.1)? Ack, sorry Garrett, I just noticed that you're running Samba 1.9.18p8 and I gave you a patch for Samba 2.0.3. I took a look at the Samba 1.9.18p10 source I had handy and it wasn't immediately clear to me what the correct patch is. Samba 1.9.18p10 uses a BUFFER_SIZE constant (defined as 0xFFFF) when calling Session Setup, but that constant is used in a *lot* more places than the CLI_BUFFER_SIZE constant in Samba 2.0.3, so I'm hesitant to fiddle with it. You're probably better off downloading 2.0.3 and applying that patch, since I'm sure that will get you a working smbclient. But if you want to stick with 1.9.18, you can give the following (untested!) patch a shot. (Let me know how it goes.) Matt *** samba-1.9.18p10/source/smb.h- Tue Jun 2 18:06:57 1998 --- samba-1.9.18p10/source/smb.h Thu Apr 15 13:02:02 1999 *************** *** 24,30 **** #ifndef _SMB_H #define _SMB_H ! #define BUFFER_SIZE (0xFFFF) #define SAFETY_MARGIN 1024 #define NMB_PORT 137 --- 24,30 ---- #ifndef _SMB_H #define _SMB_H ! #define BUFFER_SIZE (0x2000) #define SAFETY_MARGIN 1024 #define NMB_PORT 137

1 0

What is this qual_devices file?
by Jaye Mathisen 15 Apr '99

15 Apr '99

Looks like drive model numbers. Anybody slapped on 3rd party drives from that list and see if they work? I could always use a different source to update my filers.

1 0

Re: Samba client and filers
by mday＠netapp.com 15 Apr '99

15 Apr '99

Garrett Burke <Garrett.Burke(a)msc.ie> wrote: > Anyone know of any issues with smbclient (version 1.9.18p8) and filers > running CIFS (OnTap 5.2.1)? > > Session setup is failing. I can use smbclient to connect to my NT servers > but not the filer. I notice from the debug output of smbclient that it says > "Using encrypted passwords" Could this be the problem? Can't see anything > on the smbclient man page to force it to use unencrypted passwords. > > Here's some "-d 3" output from smbclient: > > [..] > > (Before you all say "use NFS", I'm writing some monitoring tools that will > run on a FreeBSD box and will actually fetch a file from the filer and calc > a CRC to ensure it's ok. This way I know the file service is available) Hi Garrett, Yes, there is a problem with the filer's handling of Session Setup requests in 5.2 that prevents smbclient from connecting. What's happening is smbclient is trying to connect with a client buffer size of 0x4400, but 5.2 rejects any client using a buffer size greater than 0x2000. So, you can recompile smbclient with the CLI_BUFFER_SIZE constant set to 0x2000 to get an smbclient that can connect to 5.2. (See below for the patch.) With that patch, smbclient should work well enough for you to at least connect and fetch a file. (There could be other bugs, though... we haven't spent any time testing smbclient yet, on any release.) In 5.3 this client buffer size limitation has been removed, so that patch isn't required. Unfortunately, though, a bug was introduced in 5.3 that causes smbclient to get filenames that are short by one character (do a "dir" and you'll see what I mean). That shouldn't prevent you from connecting and fetching a file, though. This bug will be fixed in 5.3.2. (It only affects smbclient, by the way.) Hope that helps, Matt *** samba-2.0.3/source/include/client.h- Fri Feb 5 18:17:46 1999 --- samba-2.0.3/source/include/client.h Thu Apr 15 12:18:47 1999 *************** *** 27,33 **** /* the client asks for a smaller buffer to save ram and also to get more overlap on the wire. This size gives us a nice read/write size, which will be a multiple of the page size on almost any system */ ! #define CLI_BUFFER_SIZE (0x4400) /* * These definitions depend on smb.h --- 27,33 ---- /* the client asks for a smaller buffer to save ram and also to get more overlap on the wire. This size gives us a nice read/write size, which will be a multiple of the page size on almost any system */ ! #define CLI_BUFFER_SIZE (0x2000) /* * These definitions depend on smb.h

1 0

RE: Dump command issues?
by Melvin, Grant 15 Apr '99

15 Apr '99

Hi Mike, Officially NetApp doesn't support the ATL L200 or L500, but we do have a bunch of L200s in-house and we see different issues with them which normally results in a firmware upgrade from ATL. The latest upgrade is version 28 you may want to try this. FYI, the only "stackers" we officially support are the Quantum 4700 and Breece Hill Q2.15. We have had issues with timing on other tape stackers and have made recent changes to Data ONTAP that should cope with these variations, but we have no roadmap to "certify" a bunch more stackers. I know that 3rd party vendors have also been having some difficulty getting the L200/L500 units to work via NDMP without software changes. So if you are using a 3rd party tool which is NDMP-compliant or NOT then you may want to ask about their support (think patches) for these units. If you still have an issue after getting your unit upgraded/ checked out then feel free to send me an e-mail with your dump output and we'll see if we can get to the bottom of it. Cheers, Grant -----Original Message----- From: Mike Ball [mailto:mball@rtp.opensystems.com] Sent: Tuesday, April 13, 1999 10:54 AM To: toasters@mathworks. com Subject: Dump command issues? Currently we have a F720 filer and a ATL Powerstor L500 tape library attached locally. We are running into a issue when we try to dump to multiple tapes. If we use the command below, it is supposed to dump our entire vol0 (90GB of data) to multiple tapes in our tape library. rsh -l dump 0uf urst0a,urst0a /vol/vol0 Unfortunately, the dump command above backs up to the first tape, then rewinds the tape when it is full but never unloads it. The first tape is then overwritten as the dump continues. The dump command above does not unload the tape and continue the dump onto the second tape in the library. Has anyone else experienced this before, or does anyone have any recommendations to correct the problem? Thank you, Mike Ball

2 1

RE: Migration problems
by Benn, Paul 15 Apr '99

15 Apr '99

Just for clarification.... The problem with Microsoft's Migration Tool for NetWare is that you can only migrate data to a domain controller (the problem exists for NT member servers as well as filers), right? I'm not sure how helpful this link is to you at this point (I just discovered it myself) but here it is anyway: http://support.microsoft.com/support/ntserver/migration/ Regards, Paul Oh, and to answer your question: Personally, I've never heard of any other tools to do this. I have, however, performed a NW=>NT migration. We chose to do everything manually because the end result was much cleaner. We did use the Microsoft tool, but only to migrate user accounts. The company was large so we performed the migration in steps (say 100 users per weekend and ~20 each week day). -----Original Message----- We tried to do this at the first time with a tool called Migration Tool for Netware. With this tool it is impossible to transfer the data from the Novell servers to the Netapp.

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
16
Older →

Jump to page:

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 April 1999