toasters

toasters@lists.teaparty.net

13514 discussions

RE: APC UPS Monitoring
by Hill, Aaron 25 May '03

25 May '03

We had a "real" power outage with our F880 when the whole Datacentre lost power and the UPS freaked out for some reason. The F880 handled it perfectly. We had Sybase databases running in production at the time and when power was restored, they came up fine, now problems at all. I don't think that even a dbcc had to be run to clean the db's. Wish I could say the same for our old LSI/Metastor direct-attach SCSI. Took hours to get those monsters sorted out! Thanks, Aaron -----Original Message----- From: Bokkelkamp Ernst [mailto:ernst.bokkelkamp@siemens.com] Sent: Saturday, May 24, 2003 5:36 AM To: Andrew Siegel; toasters(a)mathworks.com Subject: RE: APC UPS Monitoring I have done it quite often over the last few months on filers in the lab to show "non-believers" how well the filer handles the situation and recovers after power on. Can't tell you anything exciting except that it always worked ;-) Bye Ernie -----Original Message----- From: Andrew Siegel [mailto:abs@blueskystudios.com] Sent: Friday, May 23, 2003 5:03 PM To: toasters(a)mathworks.com Subject: Re: APC UPS Monitoring As far as I know, NetApps can survive a power cut without a problem. I heard that back in the old days, Tom Mendoza used to demonstrate the robustness of the filer by yanking the power during customer presentations. On Friday, May 23, 2003, at 09:39 AM, devnull(a)adc.idt.com wrote: > Dear Toasters, > > Can anyone please give me some tips on APC-UPS monitoring. > > I have many APC Smart UPS'es and i use them to protect my File > Servers. In > the past when we used Sun hardware, we used to use the "Powerchute" > software from APC. Now APC needs you to run some sort of Windows-box > to be > able to monitor all your machines. > > I heard about apcupsd on another list and gave that a shot and it > seems to > do a pretty decent job when it comes to linux. > > To protect my NetApp's, i am planning to use apcupsd on a linux machine > and then try and somehow "correctly" use it to shutdown the netapp. > I need to be careful about shutting down the netapp ONLY when the > power is > down and not every time the linux machine needs to be brought down.(so > maybe an rc script WONT work)

1 0

need drives/shelves for F230
by Chris Caputo 25 May '03

25 May '03

Anyone have drives/shelves for an F230 that they want to unload cheap? I'll pay for shipping plus maybe a little something more if it is reasonable... Also, any recent news on the hobbiest licensing for Data ONTAP? Thanks, Chris

1 0

RE: APC UPS Monitoring
by Bokkelkamp Ernst 23 May '03

23 May '03

I have done it quite often over the last few months on filers in the lab to show "non-believers" how well the filer handles the situation and recovers after power on. Can't tell you anything exciting except that it always worked ;-) Bye Ernie -----Original Message----- From: Andrew Siegel [mailto:abs@blueskystudios.com] Sent: Friday, May 23, 2003 5:03 PM To: toasters(a)mathworks.com Subject: Re: APC UPS Monitoring As far as I know, NetApps can survive a power cut without a problem. I heard that back in the old days, Tom Mendoza used to demonstrate the robustness of the filer by yanking the power during customer presentations. On Friday, May 23, 2003, at 09:39 AM, devnull(a)adc.idt.com wrote: > Dear Toasters, > > Can anyone please give me some tips on APC-UPS monitoring. > > I have many APC Smart UPS'es and i use them to protect my File > Servers. In > the past when we used Sun hardware, we used to use the "Powerchute" > software from APC. Now APC needs you to run some sort of Windows-box > to be > able to monitor all your machines. > > I heard about apcupsd on another list and gave that a shot and it > seems to > do a pretty decent job when it comes to linux. > > To protect my NetApp's, i am planning to use apcupsd on a linux machine > and then try and somehow "correctly" use it to shutdown the netapp. > I need to be careful about shutting down the netapp ONLY when the > power is > down and not every time the linux machine needs to be brought down.(so > maybe an rc script WONT work)

1 0

RE: APC UPS Monitoring
by Gifford, Josh 23 May '03

23 May '03

We had a F720 in a site that had regular power problems. At times every weekend the power would be down for more than an hour which would drain the UPS and the filer would fall flat on it's face. As far as the filer was concerned, there were no problems. On occasion the virus scanner servers would not reconnect on their own though. -Josh -----Original Message----- From: Andrew Siegel [mailto:abs@blueskystudios.com] Sent: Friday, May 23, 2003 11:03 AM To: toasters(a)mathworks.com Subject: Re: APC UPS Monitoring As far as I know, NetApps can survive a power cut without a problem. I heard that back in the old days, Tom Mendoza used to demonstrate the robustness of the filer by yanking the power during customer presentations. On Friday, May 23, 2003, at 09:39 AM, devnull(a)adc.idt.com wrote: > Dear Toasters, > > Can anyone please give me some tips on APC-UPS monitoring. > > I have many APC Smart UPS'es and i use them to protect my File > Servers. In > the past when we used Sun hardware, we used to use the "Powerchute" > software from APC. Now APC needs you to run some sort of Windows-box > to be > able to monitor all your machines. > > I heard about apcupsd on another list and gave that a shot and it > seems to > do a pretty decent job when it comes to linux. > > To protect my NetApp's, i am planning to use apcupsd on a linux machine > and then try and somehow "correctly" use it to shutdown the netapp. > I need to be careful about shutting down the netapp ONLY when the > power is > down and not every time the linux machine needs to be brought down.(so > maybe an rc script WONT work)

1 0

RE: Folder update time
by Alan McLachlan 23 May '03

23 May '03

Hi Chris, I had assumed that atime was stored in the directory entry itself (which would have a pointer to an inode that was a simple list of data blocks), which would have explained the behaviour reported by Jeff Burton in his post. TR2002 ("Filesystem Design for an NFS file server appliance") doesn't specify anything about directory entry contents. The testing you show below seems to nails it, but I will go and have a play when I get a moment just fo see it for myself. Now, even if the directory entry doesn't contain the attributes but is simply a name with a pointer to an inode that contains the file attributes, a change in the file attributes will still require the pointer in the directory entry to be changed to point to the new inode. (WAFL NEVER makes changes to existing inodes, it always writes new ones). Therefore the block containing that directory entry will still need to be rewritten (you seem to imply that it won't). If you are at least partly right it would mean that OnTAP is deliberately ignoring the change to directory entries in order to appear more consistent with traditional filesystem behaviour. This still doesn't help us solve Jeff's problem... -----Original Message----- From: Chris Thompson [mailto:cet1@cus.cam.ac.uk] Sent: Friday, 23 May 2003 12:48 AM To: amclachlan(a)asi.com.au Cc: toasters(a)mathworks.com Subject: Re: Folder update time Alan McLachlan writes: > > A write to a file will change the file size attribute in the directory > entry, which will of course change the mod time on the directory itself. No, it doesn't: $ ls -ld temp temp/foobar drwxr-xr-x 2 cet1 cet1 4096 May 22 11:00 temp -rw-r--r-- 1 cet1 cet1 21 May 22 09:00 temp/foobar $ echo foobar >>temp/foobar $ ls -ld temp temp/foobar drwxr-xr-x 2 cet1 cet1 4096 May 22 11:00 temp -rw-r--r-- 1 cet1 cet1 28 May 22 15:19 temp/foobar > In fact, if you don't have "atime update" turned OFF, even opening a file > will change the directory mod time since the access time attribute for the > file needs to be updated in the directory entry. No, it doesn't: $ ls -ld temp; ls -ldu temp/foobar drwxr-xr-x 2 cet1 cet1 4096 May 22 11:00 temp -rw-r--r-- 1 cet1 cet1 28 May 22 15:17 temp/foobar $ cat temp/foobar Oh what a goose I am foobar $ ls -ld temp; ls -ldu temp/foobar drwxr-xr-x 2 cet1 cet1 4096 May 22 11:00 temp -rw-r--r-- 1 cet1 cet1 28 May 22 15:22 temp/foobar (That was done on a different client from the previous test. Client-side caching can confuse attempts to look at atimes otherwise.) > Remember, in WAFL all metadata lives in files. That includes directories. So > ANY change to a directory entry will cause the modification time on the > directory to be updated. But the directory entry doesn't change. It's the inode that changes. You seem to have confused the two. >> Alan: No I haven't. I had simply assumed that mtime and atime were both stored in the directory entry itself. However, your are wrong here: the directory entry still has to change to reflect the new inode location. The inode doesn't "change", a new version of it is written elsewhere. Don't confuse WAFL with UFS... > This will in turn change the mod time on all > relevant parent directories up to the root. Restate that as "the relevant block in the inode metafile has been changed, so all the index blocks up to the root have to be rewritten as well". >> Alan: See above. All directories must change as well since the inodes their entries point to are relocated as part of the CP. Even if the directory entry has a pointer to the file ino > On a traditional filesystem like > NTFS or UFS this would be a performance disaster as it would generate lots > of additional seeks, so they don't do it. However in WAFL an change to a > file will cause all relevant metadata inodes up to the root inode to be > rewritten [in new locations without seeks] anyway, without a performance > cost. All the changed blocks will (usually) be written close together as part of the next checkpoint. But none of these blocks are directory blocks, or blocks containing the inode for the directory (unless they happen to be the same block as that containing the inode for the file). > Hope this helps. Honestly, I don't think it did. Steve Losen wrote: ] ] My guess is that the application is doing more than a simple file open. ] Perhaps it is an editor that is creating a .bak file or something like ] that. As far as I know, to change the mod time of a directory (folder) ] you need to create, delete, or rename a file in the directory. Simply ] reading or writing an existing file does not change the directory mod ] time. An application could also explicitly set the mod time of the ] directory. Another possibility is that the application is deleting and then re-creating the file, which would certainly change the mtime and ctime of the directory. Jeff Burton didn't make it very clear whether the "simple open" was for reading or writing. ] I can think of one other possibility, but I have doubts since this is ] a NTFS volume. If you create a directory with NFS, then it is not in ] unicode format (unless you specify an option to change this). ] The first time you access the directory via CIFS, it is converted to ] unicode, and this might also trip the directory mod time, but I don't ] know. Of course, this only happens once at the first CIFS access. That obviously changes the directory contents, but does it change its mtime (or even the ctime)? I can't do that experiment here as we aren't licensed for CIFS access. Chris Thompson University of Cambridge Computing Service, Email: cet1(a)ucs.cam.ac.uk New Museums Site, Cambridge CB2 3QH, Phone: +44 1223 334715 United Kingdom. **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

2 1

RE: Folder update time
by Alan McLachlan 22 May '03

22 May '03

Steve, Jeff, A write to a file will change the file size attribute in the directory entry, which will of course change the mod time on the directory itself. In fact, if you don't have "atime update" turned OFF, even opening a file will change the directory mod time since the access time attribute for the file needs to be updated in the directory entry. Remember, in WAFL all metadata lives in files. That includes directories. So ANY change to a directory entry will cause the modification time on the directory to be updated. This will in turn change the mod time on all relevant parent directories up to the root. On a traditional filesystem like NTFS or UFS this would be a performance disaster as it would generate lots of additional seeks, so they don't do it. However in WAFL an change to a file will cause all relevant metadata inodes up to the root inode to be rewritten [in new locations without seeks] anyway, without a performance cost. Hope this helps. Alan McLachlan Senior Systems Engineer Storage Management Solutions ASI Solutions www.asi.com.au Ph +61 2 6230 1566 Fax +61 2 6230 5343 Mobile +61 428 655644 e-mail amclachlan(a)asi.com.au -----Original Message----- From: Steve Losen [mailto:scl@sasha.acc.virginia.edu] Sent: Thursday, 22 May 2003 7:30 AM To: Jeff Burton Cc: toasters(a)mathworks.com Subject: Re: Folder update time > Anyone know why DOT updates the modification time on a ntfs folder > when a file in that folder is simply opened? This is not the way > it works on our other NT systems. Is this a "feature", a bug, or > just a difference between ntfs and wafl's interpretation of ntfs? > I'm on a F880c running 6.3.1R1....and I'm a unix person so I may > be missing the obvious, but I don't think so. Thanks, > > ______________________________________________________________ > Jeff Burton > Storage Architect Abbott Laboratories > EMAIL: Jeffrey.Burton(a)Abbott.com Dept. GB16/Bldg. AP14B-1 > PHONE: 847-935-5778 100 Abbott Park Rd. > FAX: 847-938-5824 Abbott Park, IL 60064-6042 My guess is that the application is doing more than a simple file open. Perhaps it is an editor that is creating a .bak file or something like that. As far as I know, to change the mod time of a directory (folder) you need to create, delete, or rename a file in the directory. Simply reading or writing an existing file does not change the directory mod time. An application could also explicitly set the mod time of the directory. I can think of one other possibility, but I have doubts since this is a NTFS volume. If you create a directory with NFS, then it is not in unicode format (unless you specify an option to change this). The first time you access the directory via CIFS, it is converted to unicode, and this might also trip the directory mod time, but I don't know. Of course, this only happens once at the first CIFS access. Steve Losen scl(a)virginia.edu phone: 434-924-0640 University of Virginia ITC Unix Support **** ASI Solutions Disclaimer **** The material transmitted may contain confidential and/or privileged material and is intended only for the addressee. If you receive this in error, please notify the sender and destroy any copies of the material immediately. ASI will protect your Privacy according to the 10 Privacy Principles outlined under the new Privacy Act, Dec 2001. This email is also subject to copyright. Any use of or reliance upon this material by persons or entities other than the addressee is prohibited. E-mails may be interfered with, may contain computer viruses or other defects. Under no circumstances do we accept liability for any loss or damage which may result from your receipt of this message or any attachments. **** END OF MESSAGE ****

4 4

Folder update time
by Jeff Burton 22 May '03

22 May '03

Anyone know why DOT updates the modification time on a ntfs folder when a file in that folder is simply opened? This is not the way it works on our other NT systems. Is this a "feature", a bug, or just a difference between ntfs and wafl's interpretation of ntfs? I'm on a F880c running 6.3.1R1....and I'm a unix person so I may be missing the obvious, but I don't think so. Thanks, ______________________________________________________________ Jeff Burton Storage Architect Abbott Laboratories EMAIL: Jeffrey.Burton(a)Abbott.com Dept. GB16/Bldg. AP14B-1 PHONE: 847-935-5778 100 Abbott Park Rd. FAX: 847-938-5824 Abbott Park, IL 60064-6042

3 3

RE: Filer F840 Network Path?
by Jon Evans 22 May '03

22 May '03

This option caused me all sorts of trouble with intermittent network connection failures (I think due to a bug in Microsoft's implementation of this RFC) I would recommend turning it off if you are having any problems at all: ip.tcp.sack.enable off -----Original Message----- From: Stephane Bentebba [mailto:stephane.bentebba@fps.fr] Sent: 19 May 2003 15:14 To: alexis.osorio(a)intek.com.co Cc: NetApp List (E-mail) Subject: Re: Filer F840 Network Path? network path not found ... if you are in 6.3 or 6.4 , check for an option called : ip.tcp.sack.enable check it is on, so turn it off and redo the test , does it works ? sack was still experimental not a long time ago i think , sack from microsoft shouldn't discuss the same way filer's sack talk i think this option should be turn off for a while Helberth Alexis Osorio O. wrote: >I have a F840 on Windows NT Domain? > >Wheni try to mapping the path C$ or any other path of the filer, the system >cannot find the network path. > >In the administrative Tools, "Server Manager" i see the computer, type and >description, selecting the computer and properties i receive the next >message: > >"The network path was not found", please anybody can help me. > > >Thank you very much. > > > >Helberth Alexis Osorio O. >Professional Services Manager > > >Information Technologies de Colombia "INTEK" >Teléfono: (57-1)6206370 ext 15 >Fax: (57-1)6206365 >Celular: (57-315)3108457 >Santafé de Bogotá, D.C. Colombia >www.intek.com.co > >STORAGETEK >INFORMATION made POWERFUL > > > > > > -- -- jetez un oeil ici http://www.sensiva.com/ -- -- have a look here http://www.sensiva.com/ --

1 0

exportfs -u -a
by Robert Borowicz 21 May '03

21 May '03

Perhaps I'm rusty with my NFS knowledge.... I made a change to my /usr/local export. (-root on a build host) I did an "exportfs -u -a" and to my horror all of the *existing* /usr/local mounts went stale. I do not remember this happening with Auspex's (in a previous life) and SunOS 4.1.2. Perhaps I need to go back to the blue NFS/NIS O'Reilly book.... Is this a Solaris 2.8 ism, or am I missing something obvious in my re-entry to the world of NFS... Here is my vfstab entry: well:/vol/sysvol0/local - /usr/local nfs no yes bg,soft,intr TIA -Bob

2 1

Re: exportfs -u -a
by Robert Borowicz 21 May '03

21 May '03

I *KNOW* what the command does. I've read the man page and the book. HOWEVER, the way this used to work (and apparently not anymore) was you were free to unexport/unshare a dir/vol globally (IE: exportfs -u -a /usr/local) but it would *NOT* affect *EXISTING* mounts. Just newly requested ones. I'll go quietly now... -Bob At 11:16 AM 5/21/2003 -0500, you wrote: >man page says it all, dude! > >SunOS/BSD Compatibility Package Commands exportfs(1B) > >NAME > exportfs - translates exportfs options to share/unshare com- > mands > >SYNOPSIS > /usr/sbin/exportfs [ -aiuv ] [ -o options ] [ pathname ] > >DESCRIPTION > exportfs translates SunOS 4.x exportfs options to the > corresponding share/unshare options and invokes > share/unshare with the translated options. > > With no options or arguments, exportfs invokes share to > print out the list of all currently shared NFS filesystems. > > exportfs is the BSD/Compatibility Package command of > share(1M) and unshare(1M). Use share(1M)/ unshare(1M) when- > ever possible. > >OPTIONS > -a Invokes shareall(1M), or if -u is specified, invokes > unshareall(1M). > > -i Ignore options in /etc/dfs/dfstab. > > -u Invokes unshare(1M) on pathname. > > -v Verbose. > > -o options > Specify a comma-separated list of optional charac- > teristics for the filesystems being exported. exportfs > translates options to share-equivalent options. (see > share(1M) for information about individual options). > >ATTRIBUTES > See attributes(5) for descriptions of the following attri- > butes: > > ____________________________________________________________ > | ATTRIBUTE TYPE | ATTRIBUTE VALUE | > |_____________________________|_____________________________| > | Availability | SUNWcsu | > |_____________________________|_____________________________| > >SEE ALSO > share(1M), shareall(1M), unshare(1M), unshareall(1M), attri- > butes(5) > >SunOS 5.8 Last change: 28 Mar 1994 1 >Bob Bailey >Network Centric Systems (NCS) >North Texas Engineering Automation >Central Operations Desk >Phone: 972-952-2518 >Pager: 972-670-7336 >Alpha Pager: 9726707336(a)messaging.nextel.com > > >Robert Borowicz <rbaus(a)swbell.net> >Sent by: owner-toasters(a)mathworks.com > >05/21/2003 10:19 AM > > To: toasters(a)mathworks.com > cc: > Subject: exportfs -u -a > > >Perhaps I'm rusty with my NFS knowledge.... > >I made a change to my /usr/local export. (-root on a build host) I did an >"exportfs -u -a" and to my horror all of the *existing* /usr/local mounts >went stale. > >I do not remember this happening with Auspex's (in a previous life) and >SunOS 4.1.2. Perhaps I need to go back to the blue NFS/NIS O'Reilly book.... > >Is this a Solaris 2.8 ism, or am I missing something obvious in my re-entry >to the world of NFS... > >Here is my vfstab entry: > >well:/vol/sysvol0/local >- /usr/local nfs no yes bg,soft,intr > >TIA > >-Bob > >

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