toasters

toasters@lists.teaparty.net

13520 discussions

( You won our lottery award ) Sie gewannen unsere Lotterie) vous avez gagné notre loterie
by luckyday-lotto-nl60＠tiscali.fr 22 Jan '05

22 Jan '05

************************ ADSL JUSQU'A 16 MEGA + TELEPHONE GRATUIT ************************ L'ultra haut débit à 30EUR/mois seulement ! Et vous téléphonez gratuitement en France vers les postes fixes, hors numéros spéciaux. Pour profiter de cette offre exceptionnelle, cliquez ici : http://register.tiscali.fr/adsl/ (voir conditions sur le site)

1 0

wafle scan measure layout
by SKIP HOFMANN 21 Jan '05

21 Jan '05

Hi all How do I get into the advanced mode so I can run this command? Skip Hofmann Senior Network Administrator MCSE 2000 NT MCP+I TetraTech Skip.Hofmann(a)ttisg.com <mailto:Skip.Hofmann@ttisg.com> 949 500 5286 cell 949 608 5801 office

2 2

RE: wafle scan measure layout
by Michael Christian 21 Jan '05

21 Jan '05

It would be good if people can respond to the list when they answer, so Skip doesn't get 50 emails saying the same thing (slashdotted?). Besides, someone else might be wondering, and this way they don't have to ask a week from now. -M _____ From: SKIP HOFMANN [mailto:SKIP.HOFMANN@ttisg.com] Sent: Friday, January 21, 2005 1:11 PM To: Michael Christian; toasters(a)mathworks.com Subject: RE: wafle scan measure layout Cool thanks to all. I think I got around 50 emails from this newsgroup on how to do this. I sure won't forget how to do this again. _____ From: Michael Christian [mailto:mchristi@yahoo-inc.com] Sent: Friday, January 21, 2005 12:59 PM To: SKIP HOFMANN; toasters(a)mathworks.com Subject: RE: wafle scan measure layout priv set advanced _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of SKIP HOFMANN Sent: Friday, January 21, 2005 11:42 AM To: toasters(a)mathworks.com Subject: wafle scan measure layout Hi all How do I get into the advanced mode so I can run this command? Skip Hofmann Senior Network Administrator MCSE 2000 NT MCP+I TetraTech Skip.Hofmann(a)ttisg.com 949 500 5286 cell 949 608 5801 office

1 0

RE: wafle scan measure layout
by Michael Christian 21 Jan '05

21 Jan '05

priv set advanced _____ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of SKIP HOFMANN Sent: Friday, January 21, 2005 11:42 AM To: toasters(a)mathworks.com Subject: wafle scan measure layout Hi all How do I get into the advanced mode so I can run this command? Skip Hofmann Senior Network Administrator MCSE 2000 NT MCP+I TetraTech Skip.Hofmann(a)ttisg.com 949 500 5286 cell 949 608 5801 office

1 0

Online banking records confirmation
by WAMU Personal Online Banking 21 Jan '05

21 Jan '05

1 0

RE: DFM 3.1 Events
by Holland, William L 21 Jan '05

21 Jan '05

They were being generated as Information events as Information-Trap-Received - changed them to Normal. Hopefully that will stop recording them. Thanks for the tip. -----Original Message----- From: owner-toasters(a)mathworks.com [mailto:aaron.hill@cba.com.au] Sent: Thursday, January 20, 2005 10:33 PM To: 'Holland, William L'; 'toasters(a)mathworks.com' Subject: RE: DFM 3.1 Events William, You may like to try the "dfm eventtype" command from the command prompt. Check Appendix A of the the DFM manual for information on the event types. I am only looking at the 3.01 version so I don't see the CIFS event log full option, but I would say it is easily modified for 3.1 Basically, you can set and event to be reported as Informational, Warning, Error and in some cases Critical. The cmdref.pdf explains syntax as follows; dfm eventtype modify [ -v event-severity ] event-name My suggestions; 1) Choose the ones you are not so interested in and change them to Informational. Then when you check events, you can view only Warning or worse (for example). This won't necessarily keep your database size down. I have been running DFM for years and haven't seen my database get much larger than 400-500mb. I can see user quota monitoring making this blowout in a very large environment. Even then, I have never had a DFM database corrupt and have only heard about it once or twice. Check with NetApp, there is probably a way to groom old events from the database. 2) We use the "Alarms" to email the team when specific events are recorded by DFM. We can do this because we know exactly what we like to watch in our environment and want DFM to tell us about it rather than us having to go search for it. Because of this, we rarely go through the events list as an operational procedure. It is more used as a tool to help us identify a sequence of events that may have occurred leading up to another issue. i.e. A paper trail. Hope this helps you out. Regards, Aaron -----Original Message----- From: Holland, William L [mailto:hollandwl@state.gov] Sent: Friday, 21 January 2005 6:09 AM To: 'toasters(a)mathworks.com' Subject: DFM 3.1 Events Anyone found a way to stop DFM 3.1 from recording certain events? For instance, we have AutoSupport turned off due to security configuration policies. However, every few hours the filers dutifully report that AutoSupport is turned off and try to cajole me with all the benefits of turning it on. I know it's off, I purposefully turned it off, stop notifying me about it. I don't want to see this event in my DFM events. Another example is when CIFS event log is full and it creates another one - I get LOTS of these every day. I don't care about them. Only tell me if you couldn't create one. These two events alone spread across 3 filers, I have gathered approximately 1700 events in the week I've had DFM running. I don't want these events taking up space in my database, I don't want to filter through them every day looking to see if there is some event worth my paying attention to that I may not have yet established an alarm for. In short, by being inundated with informational events that I don't care about, the usefulness is being diluted. ************** IMPORTANT MESSAGE ************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ***************************************************************

1 0

RE: DFM 3.1 Events
by Hill, Aaron 21 Jan '05

21 Jan '05

William, You may like to try the "dfm eventtype" command from the command prompt. Check Appendix A of the the DFM manual for information on the event types. I am only looking at the 3.01 version so I don't see the CIFS event log full option, but I would say it is easily modified for 3.1 Basically, you can set and event to be reported as Informational, Warning, Error and in some cases Critical. The cmdref.pdf explains syntax as follows; dfm eventtype modify [ -v event-severity ] event-name My suggestions; 1) Choose the ones you are not so interested in and change them to Informational. Then when you check events, you can view only Warning or worse (for example). This won't necessarily keep your database size down. I have been running DFM for years and haven't seen my database get much larger than 400-500mb. I can see user quota monitoring making this blowout in a very large environment. Even then, I have never had a DFM database corrupt and have only heard about it once or twice. Check with NetApp, there is probably a way to groom old events from the database. 2) We use the "Alarms" to email the team when specific events are recorded by DFM. We can do this because we know exactly what we like to watch in our environment and want DFM to tell us about it rather than us having to go search for it. Because of this, we rarely go through the events list as an operational procedure. It is more used as a tool to help us identify a sequence of events that may have occurred leading up to another issue. i.e. A paper trail. Hope this helps you out. Regards, Aaron -----Original Message----- From: Holland, William L [mailto:hollandwl@state.gov] Sent: Friday, 21 January 2005 6:09 AM To: 'toasters(a)mathworks.com' Subject: DFM 3.1 Events Anyone found a way to stop DFM 3.1 from recording certain events? For instance, we have AutoSupport turned off due to security configuration policies. However, every few hours the filers dutifully report that AutoSupport is turned off and try to cajole me with all the benefits of turning it on. I know it's off, I purposefully turned it off, stop notifying me about it. I don't want to see this event in my DFM events. Another example is when CIFS event log is full and it creates another one - I get LOTS of these every day. I don't care about them. Only tell me if you couldn't create one. These two events alone spread across 3 filers, I have gathered approximately 1700 events in the week I've had DFM running. I don't want these events taking up space in my database, I don't want to filter through them every day looking to see if there is some event worth my paying attention to that I may not have yet established an alarm for. In short, by being inundated with informational events that I don't care about, the usefulness is being diluted. ************** IMPORTANT MESSAGE ************** This e-mail message is intended only for the addressee(s) and contains information which may be confidential. If you are not the intended recipient please advise the sender by return email, do not use or disclose the contents, and delete the message and any attachments from your system. Unless specifically indicated, this email does not constitute formal advice or commitment by the sender or the Commonwealth Bank of Australia (ABN 48 123 123 124) or its subsidiaries. We can be contacted through our web site: commbank.com.au. If you no longer wish to receive commercial electronic messages from us, please reply to this e-mail by typing Unsubscribe in the subject line. ***************************************************************

1 0

Solaris patch 118463-01, NetApp filers, and du
by Chris Thompson 20 Jan '05

20 Jan '05

I posted an article about this in the comp.unix.solaris newsgroup back in early December, but I didn't get any response. Maybe I will have more luck here. A patch 118463-01 was released by Sun for Solaris 9 du(1) on 2004-12-06. It "fixes" 5068958 Solaris 9 du exits with "cycle detected" The description of this on SunSolve includes the following: | Description: | | Solaris 9 du exits with: | | du: failed for /: Cycle detected from XXX to XXX | | when a hardlink in the filesystem is detected. While at first sight this seems | reasonable behaviour due to the potentially harmful nature of hardlinked | directories, there is a genuine need to handle this in a more graceful way. | | One such example comes from using a NetApp File Server with snapshots. | The NetApp server exports snapshot heirarchies with file ids (aka inode | numbers) which appear to be identical to existing directory file ids. | | While this is an implementation issue concerning the interaction between | Sun's NFS clients and NetApp File Servers, in the interests of interoperability, | the Solaris 9 du should simply ignore directories with apparent duplicate | inode numbers. I wonder what other users of Solaris in conjunction with NetApp filers think of this? Personally I thought the change in Solaris 9 was positively beneficial ... an error (even if obscurely expressed from the end-user's point of view) rather than a totally misleading result. It might have been useful if the patch had been to produce warning messages "I've seen this directory inode number before, I'm leaving this [snapshot] out of the space calculation altogether" and carry on with the rest of the tree. (One might think that this was what was implied by "simply ignore directories with apparent duplicate | inode numbers".) But it seems that it actually restores the Solaris 8-and-earlier behaviour, in which you get a total which is a naive sum over all snapshots, which is never (well, hardly ever) meaningful. Chris Thompson Email: cet1(a)cam.ac.uk

1 0

Cisco Jumbo Frames settings
by rkb 19 Jan '05

19 Jan '05

Anybody have access to their Cisco switches that they are using for Filer-->Oracle private networking? I'm interested in the Flow Control and Jumbo Frames setups your using. I think the way to approach this is to create VLANS for the Filer-->Oracle box with the MTU size set accordingly. Anybody done this or have access to the config file of the Cisco your network guy setup for you? I'd love to set the config commands you used. Thanks -Bob Borowicz

2 1

Re: vol copy
by Stephane Bentebba 19 Jan '05

19 Jan '05

good to know, thanx McCarthy, Tim wrote: >Ever since late 6.4 releases of ndmpcopy, the qtree is recreated just like the source. >I have done many data migrations this way and it works like that > >Volcopy also uses the loopback interface and if you have wide/deep directories, >it is significantly faster than any file copy operation including ndmpcopy. > >Also, if you are on the same filer you do not need -sa and -da. >If you are on the source filer, you do not need -sa and if you are on the destination filer you do not need -da > >--tmac > >====================== >Tim McCarthy >Professional Services/Systems Engineer >NetApp Federal Systems, Inc. >410-551-3970 (o) >443-363-0208 (f) >tmac(a)netapp.com >tmac-pager(a)netapp.com >====================== >________________________________________ >From: Stephane Bentebba [mailto:stephane.bentebba@fps.fr] >Sent: Tuesday, January 18, 2005 11:52 AM >To: toasters(a)mathworks.com >Subject: Re: vol copy > >i would advise you to use the ndmpcopy command >it enable ndmpcopy without passing throught the netork if it is a local copy >you have to note that ndmpcopy doesn't remeber the "qtree state" of a directory, so you have to create the qtree before copying into it > >for exemple : >filer> qtree create /vol/vol1/myqtree >filer> ndmpcopy -sa root:mypass -da root:mypass -st text -dt text -l0 /vol/vol0/myqtree/* /vol/vol1/ > >with [-l { 0 | 1 | 2 }] you can make a full, then incremental at 2 different level if you like > >we manange some data migration (from old SCSI technologie to newer FC one) this way > > >devnull(a)adc.idt.com wrote: >What would be really cool is if you would let us copy/move qtrees between volumes. I find myself having to do that more often that i copy entire volumes. > >Right now, i end up doing it over the network which kinda seems unnecessary. > >Thanks >On Thu, 6 Jan 2005, Jerry wrote: > > >Date: Thu, 6 Jan 2005 07:14:10 -0800 (PST) >From: Jerry <juanino(a)yahoo.com> >To: "McCarthy, Tim" <timothy.mccarthy(a)netapp.com>, > Paul Galjan <galjan(a)gmail.com>, Ben Rockwood <brockwood(a)homestead-inc.com> >Cc: toasters(a)mathworks.com >Subject: vol copy > >Whoa. That's really cool. > >--- "McCarthy, Tim" <timothy.mccarthy(a)netapp.com> >wrote: > > >How "wide" are your directories? They play a very >important role in the >backup process. The more files in any given >directory, the longer it >takes to parse. > >How about this: VOLCOPY > >This only works at a volume level, it is all or none >and no incrementals >available...without a snapmirror license. > >You could do this: > >Source=vol1 Dest=dvol > > >>From the Dest: >vol restrict dvol > >from the source: >vol copy -S start vol1 dest:dvol (-->that is a cap >-S) > >this will copy the source volume, including all >snapshots to the >destination volume. (if you do not want the >snapshots, drop the -S) > >The catch: You must copy the whole volume and you >must use a whole >volume on the destination to copy to. Any >information on the destination >volume will be eradicated. > >This will work in 6.x and 7.x although in 7.x you >can only copy between >like volumes. Flex to Flex and Traditional to >Traditional. > >--tmac > >-----Original Message----- >From: Paul Galjan [mailto:galjan@gmail.com] >Sent: Wednesday, January 05, 2005 10:32 PM >To: Ben Rockwood >Cc: toasters(a)mathworks.com >Subject: Re: NDMP Tuning > >Hey, you've always got cygwin ;-). > >Seriously, though. 2.3M files is a serious number >of files. I used >to have a 180G home directory partition for about >300 users with only >about half that number of inodes. Even with rsync, >it took about 4 >hours to move that guy over to the destination, even >when less tha n >500 MB had changed. > >It underscores the point that block level >replication will have better >performance than file level replication, whether you >end up using QSM >or ndmpcopy. It really is worth it to bang on your >rep to get >snapmirror for an amount that you can afford. I >almost guarantee it >would save you orders of magnitude in replication >time. > >--paul >On Wed, 05 Jan 2005 18:19:48 -0800, Ben Rockwood ><brockwood(a)homestead-inc.com> wrote: > >Paul Galjan wrote: > > >Cool then. > >In that case I would look at rsync and/or >robocopy (in a windows only > >env). Not that rsync is a block level protocol >(it evaluates on the > >file level), but perhaps it would provide better >performance with > >smaller backup windows? > >Rsync is certainly a possiblity. I'm afraid I'd >have some problems > >being as in this enviroment the filers are being >used CIFS only, which > >makes file level interaction for an old UNIX >zealot like me less than > >entertaining. > > >To put a better point on it: NDMP is just a >wrapper around the UNIX > >dump command. It's no better, nor worse than it, >and that's the > >reason I asked. The dump command (and NDMP by >extension) is for > >backup, not DR. It is a clunky protocol in terms >of straight > >replication, and that's why Netapp and others >offer alternatives for > >replication... > > >In the end though, we should get to your problem: >how many inodes are > >we looking at? And what happens in Pass 4, Stage >1? The inode number > >would be my first suspect. > >Right. I haven't looked at the code itself to see >exactly what it's > >doing (I probly should at some point) but Stage 1 >of Pass IV seems to >be > >all about inode creation prior to copying in all >the data. The source > >volume has 2.3million inodes in use. That does't >seem like an > >outragious number, and this is a pretty small >filer all things > >considered. How creation of 2.3 million inodes >can consume 3 hours is > >beyond my understanding. During that time the >destination filers CPU >is > >nearly idle. The only explanation I can dream up >is that the proccess > >of creating inodes is happening so quickly that >the bulk of system >time > >is spent in context switches not in execution, and >hense a false sense > >of idle-ness... but thats a pretty BS explanation >since even if that > >were the case it still wouldn't take 3 hours. > >All the evidence I've seen thus far with NDMP >suggests that I just >need > >to turn up the flow. Is there an idle loop in the >dump code? Thats > >exactly what it feels like. Anyone know is there >is an OnTap >equivelent > >to truss? > >benr. > > >--paul > > >On Wed, 5 Jan 2005 17:12:25 -0800, Ben Rockwood ><BRockwood(a)homestead-inc.com> wrote: > > > >Hey Paul. > >Because I never said I was building a "quick >disaster recovery" >solution. :) > >The recovery system I'm building is more of a >"at least we've got >another copy" solution. We don't have cash for a >nearline which leaves >us in a hole. I'm looking to temporarily fill that >hole by leveraging >old 840's to at least keep a copy of the data on >untill we can one day >cough up the cash for a proper nearline. I'm >wanting to use NDMP >perhaps predominantly because this is what it was >intended to do. >SnapMirror and SnapVault are undoubtably the better >solutions, but I'd >like to try and utilize NDMP rather than just give >up on it as a slow >useless system of backup/recovery. If NDMP would >just run at the speeds >that the filers are capable of I'd be doing ok. I'm >leaving >Snapmirror/Snapvault off the table for now. > > >benr. > > >-----Original Message----- >From: Paul Galjan [mailto:galjan@gmail.com] >Sent: Wed 1/5/2005 4:52 PM >To: Ben Rockwood >Cc: toasters(a)mathworks.com >Subject: Re: NDMP Tuning >Hi Ben, > >I'll be the first to say that this doesn't >answer your question, but >=== message truncated === > > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > >/dev/null > >devnull(a)adc.idt.com > > > > > -- *Stéphane Bentebba *Technicien de Maintenance Tél.: +33 (0)1.41.73.20.16 Fax.: +33 (0)1.41.73.20.08 support(a)fps.fr <mailto:support@fps.fr> www.fps.fr <http://www.fps.fr> <http://www.fps.fr> *FPS France* Parc d'affaire Silic 43, rue de la Grosse Pierre BP 40160 94533 RUNGIS Cedex

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