toasters July 2003

toasters@lists.teaparty.net

88 participants
94 discussions

RE: disk failed, netapp keeps crashing when trying to reconstruct on spare
by DFinn＠studentadvantage.com 25 Jul '03

25 Jul '03

it seems to report this to the console right before going down Fri Jul 25 00:16:03 EDT [wafl_hipri:ALERT]: WAFL converting directory. Fri Jul 25 00:26:18 EDT [wafl_hipri:ALERT]: WAFL converting directory. Fri Jul 25 00:26:48 EDT [wafl_hipri:ALERT]: WAFL converting directory. PANIC: WAFL hung. in process wafl_hipri on release NetApp Release 6.1.3 on Fri Jul 25 04:27:48 2003 -----Original Message----- From: Dan Finn [mailto:dfinn@studentadvantage.com] Sent: Thursday, July 24, 2003 9:30 PM To: John Clear Cc: toasters(a)mathworks.com Subject: RE: disk failed, netapp keeps crashing when trying to reconstruct on spare Yes. The failed disk was pulled out. On Thu, 24 Jul 2003, John Clear wrote: > Did you pull the original failed disk out? A badly broken disk can > make the entire filer unhappy. > > John > > -----Original Message----- > From: DFinn(a)studentadvantage.com > To: toasters(a)mathworks.com > Sent: 7/24/2003 10:37 PM > Subject: disk failed, netapp keeps crashing when trying to reconstruct > on spare > > from the console: > > Thu Jul 24 21:29:42 EDT [mgr.stack.string:notice]: Panic string: WAFL > hung. > in process wafl_hipri on release NetApp Release 6.1.3 > Thu Jul 24 21:29:42 EDT [mgr.stack.at:notice]: Panic occurred at: Fri > Jul 25 > 01:22:32 2003 > Thu Jul 24 21:29:42 EDT [mgr.stack.proc:notice]: Panic in process: > wafl_hipri > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 0: > sk_panic(0xfffffc00005e64f0) + 0x394 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 1: > check_water_marks(0xfffffc000049d900) + 0xe0 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 2: > wafl_timer(0xfffffc000049d880) + 0x54 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 3: > wafl_process_one_msg(0xfffffc00005037a0) + 0x690 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 4: > wafl_hipri(0xfffffc0000502a80) + 0x164 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 5: > sk_hw_save_state_and_loop(0xfffffc00003f92e0) + 0x70 > Thu Jul 24 21:29:43 EDT [asup.sendError.throttled:info]: Too many > autosupport messages in too short a time: throttling REBOOT (panic) > mail. > > a disk died. it started to rebuild on a spare, the above continued to > happen several times so I thought maybe the spare it was trying to > rebuild > on was bad so I pulled it out. It came back up and began to rebuild on > a > different spare and the above happened again. Is it possible that this > other spare is also bad? What else could it be? > > Thanks > Dan Finn > >

1 0

RE: disk failed, netapp keeps crashing when trying to reconstruct on spare
by Dan Finn 25 Jul '03

25 Jul '03

Yes. The failed disk was pulled out. On Thu, 24 Jul 2003, John Clear wrote: > Did you pull the original failed disk out? A badly broken disk can > make the entire filer unhappy. > > John > > -----Original Message----- > From: DFinn(a)studentadvantage.com > To: toasters(a)mathworks.com > Sent: 7/24/2003 10:37 PM > Subject: disk failed, netapp keeps crashing when trying to reconstruct > on spare > > from the console: > > Thu Jul 24 21:29:42 EDT [mgr.stack.string:notice]: Panic string: WAFL > hung. > in process wafl_hipri on release NetApp Release 6.1.3 > Thu Jul 24 21:29:42 EDT [mgr.stack.at:notice]: Panic occurred at: Fri > Jul 25 > 01:22:32 2003 > Thu Jul 24 21:29:42 EDT [mgr.stack.proc:notice]: Panic in process: > wafl_hipri > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 0: > sk_panic(0xfffffc00005e64f0) + 0x394 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 1: > check_water_marks(0xfffffc000049d900) + 0xe0 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 2: > wafl_timer(0xfffffc000049d880) + 0x54 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 3: > wafl_process_one_msg(0xfffffc00005037a0) + 0x690 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 4: > wafl_hipri(0xfffffc0000502a80) + 0x164 > Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 5: > sk_hw_save_state_and_loop(0xfffffc00003f92e0) + 0x70 > Thu Jul 24 21:29:43 EDT [asup.sendError.throttled:info]: Too many > autosupport messages in too short a time: throttling REBOOT (panic) > mail. > > a disk died. it started to rebuild on a spare, the above continued to > happen several times so I thought maybe the spare it was trying to > rebuild > on was bad so I pulled it out. It came back up and began to rebuild on > a > different spare and the above happened again. Is it possible that this > other spare is also bad? What else could it be? > > Thanks > Dan Finn > >

1 0

disk failed, netapp keeps crashing when trying to reconstruct on spare
by DFinn＠studentadvantage.com 25 Jul '03

25 Jul '03

from the console: Thu Jul 24 21:29:42 EDT [mgr.stack.string:notice]: Panic string: WAFL hung. in process wafl_hipri on release NetApp Release 6.1.3 Thu Jul 24 21:29:42 EDT [mgr.stack.at:notice]: Panic occurred at: Fri Jul 25 01:22:32 2003 Thu Jul 24 21:29:42 EDT [mgr.stack.proc:notice]: Panic in process: wafl_hipri Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 0: sk_panic(0xfffffc00005e64f0) + 0x394 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 1: check_water_marks(0xfffffc000049d900) + 0xe0 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 2: wafl_timer(0xfffffc000049d880) + 0x54 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 3: wafl_process_one_msg(0xfffffc00005037a0) + 0x690 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 4: wafl_hipri(0xfffffc0000502a80) + 0x164 Thu Jul 24 21:29:43 EDT [mgr.stack.framename:notice]: Stack frame 5: sk_hw_save_state_and_loop(0xfffffc00003f92e0) + 0x70 Thu Jul 24 21:29:43 EDT [asup.sendError.throttled:info]: Too many autosupport messages in too short a time: throttling REBOOT (panic) mail. a disk died. it started to rebuild on a spare, the above continued to happen several times so I thought maybe the spare it was trying to rebuild on was bad so I pulled it out. It came back up and began to rebuild on a different spare and the above happened again. Is it possible that this other spare is also bad? What else could it be? Thanks Dan Finn

1 0

RE: Upgrading to 6.4.1 a good risk?
by Hill, Aaron 24 Jul '03

24 Jul '03

We had a nightmare with NDMP when 6.4.1 was installed on our FAS960 cluster. Netbackup 4.5 NDMP refused to work. NetApp rolled back the upgrade to 6.3.1 and everything worked great. From what I can tell, the D* versions have addressed this Netbackup/NDMP issue. To upgrade or not upgrade? My advice is; Don't do it unless 6.4.1D* gives you functionality that is critical to your production operation. If 6.4.1D* is critical, my advice is to upgrade and test the backups. But make sure you have a clear understanding of the downgrade procedure if you need to do it. Thanks, Aaron -----Original Message----- From: Chris Thompson [mailto:cet1@cus.cam.ac.uk] Sent: Friday, 25 July 2003 7:18 AM To: toasters(a)mathworks.com Subject: Upgrading to 6.4.1 a good risk? In the "Netapp Ontap 6.4.1 and Veritas Netbackup 4.5" thread I noticed ... from <Klaus.Micheler(a)infineon.com> > We are using Ontap 6.4.1D8 and NBU 4.5FP4 - no problems. ... from <gregory.touretsky(a)intel.com>> > We backup ONTAP 6.4.1D10 filers with NBU 4.5 - no issues. Is everyone running 6.4.1 actually using D* versions, and if so does this say something about the reliability of plain 6.4.1? I'm currently wavering about whether to upgrade from 6.3.x before or after a major filing system reorganisation. Chris Thompson Email: cet1(a)cam.ac.uk ************** 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. **************************************************

1 0

Mirroring using raidsize=2
by Bruce Arden 24 Jul '03

24 Jul '03

Our company (in its wisdom) has decided that all "critcal" data must be on mirrored filesystems, not on raid. On filers, if you set the raidsize to 2, you effectively get a mirrored volume. Does anyone do this? Does it cause a performance problem? Is there a limit on the number of raid groups in a volume? - Bruce -- Bruce Arden arden(a)nortelnetworks.com barden2(a)csc.com CSC, Nortel, London Rd, Harlow, England +44 1279 40 2877

3 2

Upgrading to 6.4.1 a good risk?
by Chris Thompson 24 Jul '03

24 Jul '03

In the "Netapp Ontap 6.4.1 and Veritas Netbackup 4.5" thread I noticed ... from <Klaus.Micheler(a)infineon.com> > We are using Ontap 6.4.1D8 and NBU 4.5FP4 - no problems. ... from <gregory.touretsky(a)intel.com>> > We backup ONTAP 6.4.1D10 filers with NBU 4.5 - no issues. Is everyone running 6.4.1 actually using D* versions, and if so does this say something about the reliability of plain 6.4.1? I'm currently wavering about whether to upgrade from 6.3.x before or after a major filing system reorganisation. Chris Thompson Email: cet1(a)cam.ac.uk

1 0

INFO.
by GEORGE BENSON IDAH. 24 Jul '03

24 Jul '03

DAYZERS PROMOTION LOTERIJ, THE NETHERLANDS. ALFONSTRAAT B56-58 1002 BS AMSTELVEEN, THE NETHERLANDS. TEL/FAX : +31- (0)20-4020-634. FROM: THE DESK OF THE PROMOTIONS MANAGER, INTERNATIONAL PROMOTIONS/PRIZE AWARD DEPARTMENT, REF: DWP/LP /26510460037/02 BATCH: 24/00319/DLP ATTENTION: AWARD NOTIFICATION . We are pleased to inform you that you are part of the winners at the recent LOTTERY INTERNATIONAL PROMOTION held 21st of march 2003. You are attached to ticket number 023-0148-790-459, with serial number 5073-11 drew the lucky numbers 43-11-44- 37-10-43, which consequently won the lottery in the 3rd category. You have therefore been approved for a lump sum payment of US$1.4 Million credited to file REF .This is from total prize money of US$15 Million among the international winners in this category. All participants were selected through a computer ballot system drawn from 25,000 names from Australia, New Zealand, America, Europe, North America and Asia as part of International Promotions Program, which is conducted annually. CONGRATULATIONS!!! Your funds is now deposited with a financial institute insured in your name/ticket and batch number. Due to the mix-up of some names and ticket numbers, we ask that you keep this award strictly from public notice until your claim have been processes and your funds will be transfer to your designated bank account. This is part of our security protocol to avoid double claiming or unscrupulous acts by participants of this program. We hope with a part of you prize, you will participate in our end of year high stakes US$1.3 billion International Lottery. To begin your claim, please contact your claim agent; MR : GEORGE BENSON IDAH . FOREIGN SERVICE MANAGER, Email : gbidah(a)netscape.net Telephone:+31-630-122-829. for due processing and the remittance of your prize money to a designated account of your choice. Remember, all prize money must be claimed not later than 30th August 2003. After this date, all funds will be returned as unclaimed. NOTE: In order to avoid unnecessary delays and complications, please remember to quote your reference and batch numbers to any of our correspondences worldwide. Furthermore, should there be any change of your address, do inform your claims agent as soon as possible. Any breach confidentiality on the part of any winners will result to disqualification Congratulations again from all our staffs and thanks for being part of our promotions program. Sincerely, SANDRA HANNS THE PROMOTIONS SECETARY N.B...... WE APOLOGIES FOR THE DELAY OF THE THIS INFORMATION.!!!

1 0

RE: Mirroring using raidsize=2
by Alexei Rodriguez 24 Jul '03

24 Jul '03

> In the advanced administration and troubleshooting guide > netapp indeed points out that a raidgroup should not have > less than three data disks. Otherwise you will have a It used to be (afaicr) that this was due to the way the writes were queued then flushed. Doing a burst across 3 drives was a performance optimization. I imagine that if you have 2 disks then you have unbalanced writes (eg: 1 write to disk A then 2 writes to disk B). It has been a while since I heard the detailed explanation of why 3 disks, so I may be mis-recollecting :) > all "critcal" data must be on mirrored filesystems, not on raid Hmm. I am pretty sure that mirroring falls under one of the defined RAID levels :) http://www.acnc.com/04_01_00.html I suppose they mean "not parity protected" rather than raid. > On filers, if you set the raidsize to 2, you effectively get > a mirrored volume. Interesting. I had not really thought of it that way, but I guess you sort of do, in a twisted way. But the reality is that you are still relying on parity protection in this scenario, even if you can survive a 1 disk failure. So you are not doing real mirroring (eg: duplication of writes & reads). The cost and performance overhead of doing this (2 drive raidgroup) solution would make me want to further investigate this mandate. Depending on the reason mirroring is being mandated, the features in the filer can be used to counter most, if not all of these reasons. alexei

3 2

RE: out of inodes - how to increase inodes?
by Neto, Antonio Jose Rodrigues 24 Jul '03

24 Jul '03

Sorry, maxfiles. -----Original Message----- From: Neto, Antonio Jose Rodrigues Sent: Thursday, July 24, 2003 4:02 PM To: s o f i a; toasters(a)mathworks.com Subject: RE: out of inodes - how to increase inodes? maxdirfiles -----Original Message----- From: s o f i a [mailto:sofiavalera@yahoo.com] Sent: Thursday, July 24, 2003 2:59 PM To: toasters(a)mathworks.com Subject: out of inodes - how to increase inodes? hello all, i have just inherited a filer; and excuse me for my naive question. 1. my /vol/vol0 is out of inodes: Thu Jul 24 10:54:42 PDT [wafl_lopri:notice]: file system on volume vol0 is out of inodes 2. df -i output is: df -i Filesystem iused ifree %iused Mounted on /vol/vol0/ 1032962 0 100% /vol/vol0/ /vol/vol1/ 5489 5159380 0% /vol/vol1/ 3. But seems like i still have disk space, only max'ed out inodes or max files: vol0 (root) online block/on 9% 23.9 GB 21.7 GB 2 1.03m 1.03m QUESTION - can I increase my inodes dynamically? if so, what is the command to do so? tia, sofia v. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

increasing inodes.
by s o f i a 24 Jul '03

24 Jul '03

thank you for all the responses. i was able to do so. one quick question, 1. why was i unable to increase to 11m but ok to increase to 8m? mfiler2> maxfiles vol0 11000000 Max inode count cannot exceed 8263815 Cannot support more than 1 inode per 4 KB of disk space mfiler2> maxfiles vol0 8000000 what does that mean cannot support more than 1 inode per 4kb of disk space? - sv. > > -----Original Message----- > From: s o f i a [mailto:sofiavalera@yahoo.com] > Sent: Thursday, July 24, 2003 2:59 PM > To: toasters(a)mathworks.com > Subject: out of inodes - how to increase inodes? > > __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

1 0

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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 July 2003