toasters

toasters@lists.teaparty.net

3 participants
13514 discussions

AW: CIFS: Error on named pipe
by Alexander Schalek 16 Apr '08

16 Apr '08

That's not a specific user problem. This error also occurs when there is no user accessing the filer. Von: George, Andrew [mailto:Andrew.George@anz.com] Gesendet: Mittwoch, 16. April 2008 02:17 An: Alexander Schalek; toasters(a)mathworks.com Betreff: RE: CIFS: Error on named pipe If its working for everyone else I'd be asking what's different about that user. do a cifs lookup <domain>\<Userid> to make sure the user account is resolvable from the filer get the user to try a different PC (to see if its a problem with the connection settings in the client registry) Check the user and computer account in AD for weirdness ________________________________ From: owner-toasters(a)mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Alexander Schalek Sent: Wednesday, 16 April 2008 3:54 AM To: toasters(a)mathworks.com Cc: Alexander Schalek Subject: CIFS: Error on named pipe Hi, one of our customers is geting this error constatly: Tue Apr 15 14:20:19 GST [abcfas01: cifs.pipe.errorMsg:error]: CIFS: Error on named pipe with ADS10: Error connecting to server, open pipe failed Tue Apr 15 14:20:19 GST [abcfas01: smbrpc.pipeCreate.fail:error]: CIFSRPC: Attempt to create pipe LSA for LsarLookupNames failed with error 0xc000005e. When I ran cifs domaininfo, everything looks fine: abcfas01> cifs domaininfo NetBios Domain: ABCNET Windows 2000 Domain Name: abcnet.com Type: Windows 2000 Filer AD Site: abc-def Current Connected DCs: \\ADS10<file:///\\ADS10> Total DC addresses found: 14 Preferred Addresses: X.X.X.X ADS10 PDC Favored Addresses: X.X.X.X PDC Other Addresses: Y.Y.Y.Y PDC Z.Z.Z.Z PDC Not currently connected to any AD LDAP server Preferred Addresses: None Favored Addresses: None Other Addresses: None I couldn't find any information on the now site or google search regarding this error. Any ideas? Thanks in advance! Regards, alex "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication."

2 2

Serious A-sis bugs
by Darragh, Stephen J (CSC) (US SSA) 16 Apr '08

16 Apr '08

If you are running a-sis with 7.2.3 or 7.2.3, there are a few bugs that can cause the filer to panic and mark that volume offline forcing a wafl_check on the containing aggregate. Not only that, but we had to netboot a developer release and had extensive outages. We have been told that 7.2.4 had fixed these bugs, but if you have run asis on an old version, the bug may be there dormant. I believe these were the bugs that were identified in our incident report. bug 256799 Bug 266312 Bug 276084 bug 266312 bug 251673 The bug hit our primary storage, and it also his the VSM volumes on our DR filer, and it would is in the ACL/directory of the backup tapes as well.

6 6

Oddball SnapManager for SQL retention issue
by Raj Patel 15 Apr '08

15 Apr '08

Hi all, Is there a definitive command for snapshot deletion/retention - we've been struggling with this for awhile now and no combination of the '-D' or '-R' flag seems to do what we'd like it to do. For most our our SQL servers this isn't a real issue - once every few months we can manually remove old snaps; however we have a server that has a big database and a high-rate of change so we'd like to take snaps more often but lower the retention time - unfortunately as the deletions don't occur we fill the volume fairly quickly. The string we're using as a SQL 2005 agent job is similar to this - C:\Program Files\NetApp\SnapManager for SQL Server\SmSqlBi.exe -H "INFSQL1" -D 4 -R -G -S "INFSQL1" -C 8 "ArchiveManager" -Q "INFSQL1" -UM Has anyone else had similar issues or is there something I'm missing in the command string ? Alternatively is there a sdcli.exe / smsqlbi.execommand I can schedule to remove x number of old snaps ? Thanks in advance, Raj.

1 0

Wafl susp in a sim
by Nicholas Bernstein 15 Apr '08

15 Apr '08

I'm running the command "wafl_susp" and am getting the error: "found zero suspended messages" -- has anyone seen this before? Very strange. I tried this on a sim and a filer. Ontap 7.2.1. -- Nicholas Bernstein Technologist, Consultant, Instructor http://nicholasbernstein.com

6 5

FW: Serious A-sis bugs
by Freeman, Larry 14 Apr '08

14 Apr '08

Hi Stephan, regarding the issue you've described below, we are in the process of writing a Customer Service Bulletin and notifying users that all dedupe (A-SIS) systems require a mandatory upgrade to 7.2.4. I don't want to diminish the severity of this issue, but I think its important to point out that very few users have experienced panics as a result of this, but of course if you are one of those few that has...that is of little consolation. I apologize for the aggravation this issue caused you. NetApp felt it was very important to first identify the root cause and then define a corrective action plan before notifying our dedupe users. The corrective action plan will include the above mentioned upgrade to 7.2.4 and also tools for users to scan and repair any inconsistencies in their ACL or directory metadata without having to live through the kind of experience you were faced with. I'd also like to mention that no file data corruption occurs as a result of this issue, only inconsistencies between metadata and data blocks which can be detected and repaired with the maintenance tools we will provide. Again, not trying to diminish the seriousness of this issue, believe me it has a very high priority at NetApp. Notifications will begin next week. If anyone else on toasters has questions about this issue or would like more info, please contact NetApp Customer Support. Thanks, Larry Freeman NetApp > From: "Darragh, Stephen J \(CSC\) \(US SSA\)" > <stephen.j.darragh(a)baesystems.com> > Date: April 10, 2008 8:04:33 AM PDT > To: <toasters(a)mathworks.com> > Subject: Serious A-sis bugs > > If you are running a-sis with 7.2.3 or 7.2.3, there are a few bugs > that can cause the filer to panic and mark that volume offline forcing > a wafl_check on the containing aggregate. > Not only that, but we had to netboot a developer release and had > extensive outages. > > We have been told that 7.2.4 had fixed these bugs, but if > you have run > asis on an old version, the bug may be there dormant. > > I believe these were the bugs that were identified in our incident > report. > > bug 256799 > Bug 266312 > Bug 276084 > bug 266312 > bug 251673 > > The bug hit our primary storage, and it also his the VSM volumes on > our DR filer, and it would is in the ACL/directory of the backup tapes > as well. > > > > >

2 1

OFCS2 clones in Oracle RAC environments
by Daniel Keisling 11 Apr '08

11 Apr '08

Toasters, Is anyone using clones of OCFS2 filesystems in an Oracle RAC environment? I am testing cloning database LUNs to present back to the same server in order to accomplish zero downtime backup and ease of file-level and LUN-level recovery. The problem I am running into is that the UUID of the OCFS2 filesystem is cloned into the new filesystem (as expected), which causes the OCFS2 daemons to refuse to mount an already mounted filesystem (even though it's really not). While it's possible to change the UUID on OCFS2, it cannot be changed until all filesystems sharing that UUID are unmounted (and there is no "force" option). The only solutions I see so far are: 1) After the clone is taken, unmount the live database and change the UUID on the clone. Obviously this is probably not the wisest solution for high-availability databases. 2) Mount the clone on a Linux host not in this RAC environment. Any Linux host running the OFCS2 modules and on the SAN can be used. The post-processing by the DBA (copying the last ARC and control file) can be done via SCP to the mounted filesystem on the secondary host. autofs would also be a nice solution to enable access of the filesystem from the RAC environment. I'd rather not have to rely on a secondary server to accomplish this. 3) Edit the filesystem superblock of the clone to change the UUID. This is highly technical, but possible. If anyone has ever done this, let me know. I ran into the same problem with ASM (which does not let you change the label at all), which led me to try out OCFS2. I'm curious as to how other people are accomplishing ZDB and having a clone of an RAC-enabled database mounted on the same server. TIA, Daniel ______________________________________________________________________ This email transmission and any documents, files or previous email messages attached to it may contain information that is confidential or legally privileged. If you are not the intended recipient or a person responsible for delivering this transmission to the intended recipient, you are hereby notified that you must not read this transmission and that any disclosure, copying, printing, distribution or use of this transmission is strictly prohibited. If you have received this transmission in error, please immediately notify the sender by telephone or return email and delete the original transmission and its attachments without reading or saving in any manner.

1 0

nfsd.invalid.nsec.time
by Willeke, Jochen 11 Apr '08

11 Apr '08

Hello toasters, since some time we do see strange error messages in the logs of one filer. Here is the message: [nafiler: nfsd.invalid.nsec.time:warning]: Client 192.168.139.43 has an invalid nsec mtime (V3):2196581216 on inode:700615 The client is a SLES10 SP1 and has the kernel 2.6.16.46-0.12-smp. I have searched NOW and the web but did not find a proper explanation of what is causing this error messages :( We do see this message only for that client, never seen it for any other system. Best Regards 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.

2 2

CIFS BUG!!! Solution ID: kb23196 (???)
by Milazzo Giacomo 09 Apr '08

09 Apr '08

Hi all A customer of ours migrating to a new NetApp all their shares (from a Samba server on Linux) got this well documented error, both from NetApp and Microsoft. Data Ontap is 7.2.4. The problem is that neither me or some collegues of mine have had this issue, from XP clients or other Windows OS!!! So, why this customer is getting this bug now? He ha also tried to change the registry key (its clients are all XP SP2) but nothing change! Any file system operation performer by an XP client need a refresh (F5) of the explorer... Any idea? NetApp says: Solution ID: kb23196 CIFS: Files created by Windows XP are not visible without pressing F5 Symptoms When a Windows XP workstation is mapping filer shares through a DFS root and a new file is added, the new file may not be visible in Windows Explorer until the user explicitly refreshes the window (in Windows Explorer by pressing F5). CIFS: Files created by Windows XP are not visible without pressing F5 Solution Microsoft says: http://support.microsoft.com/?scid=kb%3Ben-us%3B823291&x=22&y=7 Dott. Giacomo Milazzo Technical Account Manager Sinergy SpA Filiale di Roma + 00148. viale Castello della Magliana, 38 ' (+39) 3406001045 0665970252 7 +39 02 26922048 - g.milazzo(a)sinergy.it

3 3

UTF-8 appended to language code.
by Milazzo Giacomo 08 Apr '08

08 Apr '08

Hi all I need to append the .UTF-8 to the language code of some volume with a mixed security. I need to know if this can change or alter the name of the files there contained, accessing them both from NFS and CIFS. This because using Enterprise Vault SP2 on a NetApp share and placeholder (policy ad hoc for ev) the size of archived files reports "0" bytes instead of the real value reflecting the original data... My EV is 7.5 SP2 but I've only found a doc related to EV v.6 SP2 (http://seer.entsupport.symantec.com/docs/282785.htm) and I put here an extract of the readme attached to EV installation: Anyway supposing that they're right, can I add this UTF-8 and be sure? Thanks a lot NetApp Filer placeholder shortcuts appear to be 0 KB [Ref E1029910, E1017992, DOR1006] Placeholder shortcuts created on NetApp Filers fail to reflect the original file size, appearing instead to be 0 KB, if either of the following conditions applies: * The language setting on the NetApp Filer is Shift JIS (Japanese) * The language setting on the NetApp Filer is not appended with .UTF-8, and the name of the file that is converted to a placeholder contains Unicode characters. To avoid the second condition, you can append .UTF-8 to the language setting on the NetApp Filer. To do this, enter the following command from the NetApp Filer's administration console: vol lang volume_name language_code.UTF-8 where volume_name specifies the volume, and language_code is the code for the language setting. For example: vol lang vol0 en.UTF-8 Note: You can view a list of the language settings the NetApp Filer supports by entering the following command: vol lang

2 1

MPIO and path failure
by Jon Hill 08 Apr '08

08 Apr '08

We had an incident the other day where we lost one of our two paths to storage. We noticed the path failure quite by accident, and some time after it actually happened. Does anyone know whether there's a way that the NTAP fibre DSM can be configured to generate an alert (by SNMP or e-mail) whenever a path fails?

4 6

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