toasters

toasters@lists.teaparty.net

1 participants
13523 discussions

SV: Strange SnapVault error
by Karlsson Ulf Ibrahim :ULK 02 Feb '09

02 Feb '09

Hello1 > > What do the "messages" logfiles on both the filers tell you? > Sun Feb 1 02:09:06 CET [replication.dst.waflErr:error]: SnapVault: destination transfer from 192.168.10.10:/vol/linux/home to /vol/sv_pnap1h1_linux/pnap1h1_linux_home : replication destination could not set permissions on a file or directory:Invalid argument. /Uffe

1 0

Re: Local FCP nodename does not match the cluster partner's FCP nodename.
by Linux Admin 01 Feb '09

01 Feb '09

What would be the impact of running in this state? Is this just an issue for cluster takeovers/failover? On Sat, Jan 31, 2009 at 11:18 PM, Webster, Stetson < Stetson.Webster(a)netapp.com> wrote: > I personally went through this problem about a year ago. At the time > when I remedied it, I was not serving data. Luckily, it was in the > beginning stages of my implementation. Though I don't remember if both > controllers were brought down, my circumstances were such that it didn't > matter. > > > > *Stetson M. Webster** > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Sunday, February 01, 2009 12:09 AM > > *To:* Webster, Stetson > *Cc:* NetApp Toasters List > *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Thanks again Stetson, great help!!! > > Did anyone in the group ever remedy this bug manually: > Do I need to run "fcp stop/start" on both nodes? > > On Sat, Jan 31, 2009 at 10:58 PM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > > You can change either to the other. The idea is to get them to match, so > it doesn't matter which one. I believe there will be an outage. I would > not recommend trying it while serving live data. I cannot comfortably tell > you to do a failover to change it either. > > > > *Stetson M. Webster > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:53 PM > *To:* Webster, Stetson > *Cc:* NetApp Toasters List > *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Stetson, > > Thanks!!!! > > Quick follow up to you and the group: > > It says: > > > > In such a case, the user must run an "fcp nodename" command on the partner and > > obtain the partner's nodename. Update the local head's nodename (WWN) with the > > > > partner's nodename using the "fcp set nodename WWN". Then, verify that it is > > set with "fcp nodename" on the local head. Then run "fcp start" to start the fcp > > service. > > > > > > > > netapp01> fcp nodename > > Fibre Channel nodename: 50:xx:xx:xx:xx:xx:xx:xx > > netapp02> fcp nodename > Fibre Channel nodename: 50:yy:yy:yy:yy:yy:yy:yy > > Which one do I set with "fcp set" command: netapp1 and netapp2. Does it > cause outage? > (fcp start?) > > On Sat, Jan 31, 2009 at 10:42 PM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > > Try this: > > http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=202390 > > > > > > *Stetson M. Webster > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:23 PM > *To:* NetApp Toasters List > *Subject:* Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Ho folks > > What does this error means and how do I remedy it? > > > > >

1 0

Re: Local FCP nodename does not match the cluster partner's FCP nodename.
by Linux Admin 01 Feb '09

01 Feb '09

Thanks again Stetson, great help!!! Did anyone in the group ever remedy this bug manually: Do I need to run "fcp stop/start" on both nodes? On Sat, Jan 31, 2009 at 10:58 PM, Webster, Stetson < Stetson.Webster(a)netapp.com> wrote: > You can change either to the other. The idea is to get them to match, so > it doesn't matter which one. I believe there will be an outage. I would > not recommend trying it while serving live data. I cannot comfortably > tell you to do a failover to change it either. > > > > *Stetson M. Webster** > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:53 PM > *To:* Webster, Stetson > *Cc:* NetApp Toasters List > *Subject:* Re: Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Stetson, > > Thanks!!!! > > Quick follow up to you and the group: > > It says: > > > In such a case, the user must run an "fcp nodename" command on the partner and > obtain the partner's nodename. Update the local head's nodename (WWN) with the > > partner's nodename using the "fcp set nodename WWN". Then, verify that it is > set with "fcp nodename" on the local head. Then run "fcp start" to start the fcp > service. > > > > netapp01> fcp nodename > > Fibre Channel nodename: 50:xx:xx:xx:xx:xx:xx:xx > > netapp02> fcp nodename > Fibre Channel nodename: 50:yy:yy:yy:yy:yy:yy:yy > > Which one do I set with "fcp set" command: netapp1 and netapp2. Does it > cause outage? > (fcp start?) > > > On Sat, Jan 31, 2009 at 10:42 PM, Webster, Stetson < > Stetson.Webster(a)netapp.com> wrote: > > Try this: > > http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=202390 > > > > > > *Stetson M. Webster > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:23 PM > *To:* NetApp Toasters List > *Subject:* Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Ho folks > > What does this error means and how do I remedy it? > > >

1 0

Re: Local FCP nodename does not match the cluster partner's FCP nodename.
by Linux Admin 01 Feb '09

01 Feb '09

Stetson, Thanks!!!! Quick follow up to you and the group: It says: In such a case, the user must run an "fcp nodename" command on the partner and obtain the partner's nodename. Update the local head's nodename (WWN) with the partner's nodename using the "fcp set nodename WWN". Then, verify that it is set with "fcp nodename" on the local head. Then run "fcp start" to start the fcp service. netapp01> fcp nodename Fibre Channel nodename: 50:xx:xx:xx:xx:xx:xx:xx netapp02> fcp nodename Fibre Channel nodename: 50:yy:yy:yy:yy:yy:yy:yy Which one do I set with "fcp set" command: netapp1 and netapp2. Does it cause outage? (fcp start?) On Sat, Jan 31, 2009 at 10:42 PM, Webster, Stetson < Stetson.Webster(a)netapp.com> wrote: > Try this: > > http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=202390 > > > > > > *Stetson M. Webster** > *Professional Services Engineer > NCIE-SAN, NCIE-B&R, SNIA-SCSE > NetApp Global Services - Southeast District > > 919.250.0052 Mobile > Stetson.Webster(a)netapp.com > > Learn how: netapp.com/guarantee > > > > [image: guarantee-email-sig2]<http://www.netapp.com/us/solutions/infrastructure/virtualization/guarantee.…> > > > > > *From:* Linux Admin [mailto:sysadmin.linux@gmail.com] > *Sent:* Saturday, January 31, 2009 11:23 PM > *To:* NetApp Toasters List > *Subject:* Local FCP nodename does not match the cluster partner's FCP > nodename. > > > > Ho folks > > What does this error means and how do I remedy it? > >

1 0

Local FCP nodename does not match the cluster partner's FCP nodename.
by Linux Admin 01 Feb '09

01 Feb '09

Ho folks What does this error means and how do I remedy it?

1 0

RE: 10k and 15k disks, sparedisk handling (UNCLASSIFIED)
by Willeke, Jochen 28 Jan '09

28 Jan '09

Hi, thanks a lot! Setting "options raid.rpm.fcal.enable off" does the trick! Thanks a lot for all replies. Regards Jochen -----Original Message----- From: Blackburn, James M CTR USA USAASC [mailto:james.m.blackburn1@us.army.mil] Sent: Wednesday, January 28, 2009 3:23 PM To: toasters(a)mathworks.com Cc: Willeke, Jochen Subject: RE: 10k and 15k disks, sparedisk handling (UNCLASSIFIED) Classification: UNCLASSIFIED Caveats: NONE You wrote: > Hello toasters, > > i came accross an issue with one filer where we have mixed 10k and 15k > 144gb disks. Due to the fact that netapp stops delivering 10k FC disks > we are running out of 10k spares for that filer. > > We had the issue that one 10k 144gb disk failed and the filer had the > choice to take a 15k 144gb or a 10k 320gb disk. Gues what, the filer > chose the 320gb over the 144gb one because of the better fit in RPM. > > Now my two questions are, will this behaviour change?? And can i stop > the filer from complaining about low spares?? As 10k 144gb disks are > not available any longer, i am afraid to receive this message for quiet > a long time (till we got rid of all 10k disks). > > Best regards from germany and thanks in advance Good day, Would you happen to have already tried "options raid.rpm.fcal.enable off"? Hope this helps; thanks. -- Jim Blackburn james.m.blackburn1(a)us.army.mil Classification: UNCLASSIFIED Caveats: NONE -- WINCOR NIXDORF International GmbH Sitz der Gesellschaft: Paderborn Registergericht Paderborn HRB 3507 Gesch�ftsf�hrer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. J�rgen Wunram Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193 Diese E-Mail enth�lt vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt�mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet. This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

1 0

10k and 15k disks, sparedisk handling
by Willeke, Jochen 28 Jan '09

28 Jan '09

Hello toasters, i came accross an issue with one filer where we have mixed 10k and 15k 144gb disks. Due to the fact that netapp stops delivering 10k FC disks we are running out of 10k spares for that filer. We had the issue that one 10k 144gb disk failed and the filer had the choice to take a 15k 144gb or a 10k 320gb disk. Gues what, the filer chose the 320gb over the 144gb one because of the better fit in RPM. Now my two questions are, will this behaviour change?? And can i stop the filer from complaining about low spares?? As 10k 144gb disks are not available any longer, i am afraid to receive this message for quiet a long time (till we got rid of all 10k disks). Best regards from germany and thanks in advance Jochen -- WINCOR NIXDORF International GmbH Sitz der Gesellschaft: Paderborn Registergericht Paderborn HRB 3507 Gesch�ftsf�hrer: Eckard Heidloff (Vorsitzender), Stefan Auerbach, Dr. J�rgen Wunram Vorsitzender des Aufsichtsrats: Karl-Heinz Stiller Steuernummer: 339/5884/0020 - Ust-ID Nr.: DE812927716 - WEEE-Reg.-Nr. DE44477193 Diese E-Mail enth�lt vertrauliche Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrt�mlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser E-Mail ist nicht gestattet. This e-mail may contain confidential information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

1 0

Performance numbers for FAS3140?
by Davin Milun 27 Jan '09

27 Jan '09

Does anyone have any performance numbers (or impressions, if not actual numbers) of the FAS3140? NetApp does not seem to have published any on the spec.org site - they have the 3040, 3070 and 3170 - but not the 3140. I'm curious how the 3140 compares to a 3070, and to a 3170. I'm mostly interested in NFS performance - but I expect that all protocols should scale similarly-enough between models for comparisons of any protocol to be useful. Thanks. Davin.

1 0

Re: panics with 7.2.6.1
by Jack Lyons 24 Jan '09

24 Jan '09

Are there any other people experiencing issues with 7.2.6.1? We put off our upgraded based on this thread, but I still see 7.2.6.1 on NOW. Was this possibly a 7.2.6 issue that happened after an upgrade didn't complete correctly? Peter D. Gray wrote: > Hmmmmmm... it looks like this is another release that should not have > seen the light of day. Netapp, you need to up your game a bit > in this area. I usually hold up netapp as a company that have their > quality control right. This has dented their reputation seriously at > our site. > > Regards, > pdg > > -- > > See mail headers for contact information. > > >

1 0

RE: 7.3.1 and 2020 nonsense :-)
by Glenn Walker 23 Jan '09

23 Jan '09

That was my point - having spares is always a good idea and I don't consider it 'waste'. This means the root volume will waste a few GB, like any other volume. Glenn ________________________________ From: genO [mailto:genec220@verizon.net] Sent: Tuesday, January 20, 2009 12:59 PM To: G.Milazzo(a)sinergy.it; toasters(a)mathworks.com Cc: Glenn Walker Subject: RE: 7.3.1 and 2020 nonsense :-) Giacomo, You could usea 16TB RAID-DP protected aggregate with multiple flexible volumes, the rootvol being one of those flexvols, as long as you allocate 2 spares. g ________________________________ From: Milazzo Giacomo [mailto:G.Milazzo@sinergy.it] Sent: Tuesday, January 20, 2009 12:02 PM To: Glenn Walker; toasters(a)mathworks.com Subject: R: 7.3.1 and 2020 nonsense :-) Maybe something has been not clear for you. The issue is for this nonsense 2020 usage of 7.3.1. For 2020 and 16TB aggregate only: you must create a SEPARATE aggregate raid dp that will have to contain THE ROOT ONLY, no other volumes, no user data. If you want you could also use R4...but with 2 spares. The result is the same. For a 2020 using 1 TB SATA disk I will waste 3 TB for root!!! Nonsense...unuseful, ridicoulous...what else? :-) ________________________________ Da: Glenn Walker [ggwalker(a)mindspring.com] Inviato: martedì 20 gennaio 2009 17.27 A: Milazzo Giacomo; toasters(a)mathworks.com Oggetto: RE: 7.3.1 and 2020 nonsense :-) I don't see the issue: Create massive aggregate, use RAID-DP and leave 2 spare disks. Put all data in the one aggregate. We (as a general rule) do not use a separate aggregate for our root volumes - we just maintain a healthy number of spares and use RAID-DP. Glenn ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Milazzo Giacomo Sent: Tuesday, January 20, 2009 7:09 AM To: toasters(a)mathworks.com Subject: 7.3.1 and 2020 nonsense :-) Hi all, reading this from 7.3.1 release note I've been really beated from this. I was thinking to a 2020 full of 1 TB SATA. To have a 16 TB aggregate I should waste 3 TB for few gigs of root! :-) Luckly I don't think that somebody will suggest a 2020 to manage 16 TB of data!!! :-) Bye Increased aggregate capacity for FAS2020 systems Beginning with Data ONTAP 7.3.1, FAS2020 systems support aggregates up to 16 TB raw capacity, provided that the root volume is hosted in a dedicated aggregate (that is, one that contains only the root volume and no user data). Note: An alternative to maintaining a dedicated root aggregate is to maintain two spare disks. A dedicated root aggregate configuration of three disks is the recommended best practice for all systems. However, if such a configuration is not practical in your environment, you must maintain two spare disks if you configure your FAS2020 system for aggregates larger than 8 TB raw capacity. If you do not configure aggregates larger than 8 TB raw capacity on your FAS2020 system, the conditions for two spare disks or a dedicated root aggregate do not apply. For more information about FAS2020 systems' storage capacity, see the System Configuration Guide. Dott. Giacomo Milazzo Technical Account Manager Sinergy SpA Filiale di Roma * 00148. viale Castello della Magliana, 38 ' (+39) 3406001045 0665970252 7 +39 02 26922048 * Giacomo.Milazzo(a)Sinergy.it

5 4

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