toasters

toasters@lists.teaparty.net

13520 discussions

RE: weird cifs problem
by Willeke, Jochen 15 Oct '07

15 Oct '07

Hi, >>Possibly a stupid question, but has someone ran wireshark/tcpdump/windump >>on the client side to verify that it is actually the client waiting after >>a filer response, and not just network latency? Yes i did a tracing. And you see that the client is not waiting. Here some output No time SRC DEST Protocol Info 282 0.000145 client nafiler SMB Write AndX Request, FID: 0x026b, 36 bytes at offset 0 283 0.001178 nafiler client SMB Write AndX Response, FID: 0x026b, 36 bytes 284 0.056002 client nafiler SMB Close Request, FID: 0x026b 285 0.000391 nafiler client SMB Close Response, FID: 0x026b This is only one examlpe. The filer seems to be the faster part within this connection, doesn't it? But what causes the client to wait so long?? I was only creating a file from my client on that share. Rgds Jochen

3 4

Microsoft DFS participation and Virtual File Manager
by Mike Partyka 14 Oct '07

14 Oct '07

Hello All, I¹ve seen some posts recently talking about using the filer to participate in a DFS schema. I asked NetApp support if a filer could participate in MS DFS and was told no, and referred to Virtual File Manager which seems to replace the DFS schema not allow the filer to participate. What is required from a NetApp storage perspective to participate in MS DFS? Also does anyone have familiarity with VFM and whether if has any advantages over VFM? Thx -- Michael Partyka - Technical Engineer . . . . . . . . . . . . . . . . . . . . . . . . . . Applied Communications of MN 3496 Shoreline Drive Spring Park, MN, 55348 o. 952 .471 .8558 c. 612 .669 .8268 e. mpartyka(a)acmn.com

4 4

cannot mount snapshots
by Skip Norman 12 Oct '07

12 Oct '07

Has anyone come across snapshots that could not be mounted by snapdrive 4.2.1? I currently have a case open with support, but this is bugging the life out of me... My current scenario is a windows 2003 sp2 server with 2 LUN's, one for a scientific application called waters empower (D:) and the other for the oracle database that is associated with it (E:). A backup script of the scientific application runs nightly and calls a script that creates a snapshot while the database is in hot backup mode. All of this seems fine and dandy until I try to mount the snapshot to backup the contents to tape. Using sdcli I should be able to execute the following command via a script to mount the snapshot in preparation for writing it to tape: sdcli snap mount -k d -s snap0 -d y I have done some testing in which I tried to mount these snapshots from a remote server running snapdrive 4.2.1 as well and it was also unsuccessful. I also created a separate lun in which I took some snapshots of and I was able to mount it (this eliminates a problem with snapdrive on the machine and means to me that there is something happening to the snapshots that make them unmountable.) What can I look for to see what is wrong with my snapshots? Snap list shows them to be normal... Any thoughts would be appreciated.

8 12

(no subject)
by Carl Howell 12 Oct '07

12 Oct '07

I'm trying to get the DFM output to compute for an aggregate that contains both non-mirrored(space guaranteed=yes) and mirrored(space guaranteed=no) volumes. The aggregate used space is 1541 in the .csv file, but using KB9300 from the NOW site, I compute it as 1962. Where am I going wrong? Thanks, --Carl

1 0

Netapp, OS X and CIFS
by Anders Bruvik 12 Oct '07

12 Oct '07

We have problems configuring for CIFS-file sharing against OS X clients. Domain controllers are Win 2003, OS X clients are 10.4.10, NetApp are FAS3050 running 7.2.3P2 and 7.0.5. In order to run cifs setup, we had to turn off netbios over tcp on the filers (if not, the filer could not communicate with the DC's). We use AD domain authentication. Now, windows-clients are able to connect to the filer, but OS X clients, which are not able to use SMB over TCP, are not able to connect. We can turn on netbios over tcp on the filer, this enables OS X clients to connect, if they use kerberos for authentication (which is perfectly acceptable). However, the filer will loose its connection with the DC (as reported by cifs testdc), and I have a feeling that this is not the correct way to configure this. So what is the recommended way to configure netapps for CIFS-file sharing in a mixed OS X and windows environment? Thanks in advance for any help. -- kind regards, Anders Skolseg Bruvik <a.s.bruvik(a)usit.uio.no> USIT (BSD), University of Oslo

2 1

RE: Netapp, OS X and CIFS
by Kevin Parker 11 Oct '07

11 Oct '07

Is netbios over tcpip enabled/disabled on the DC's? **Sent using wireless handheld... please excuse any typo's or brevity** Kevin Parker - NWN Corporation kparker(a)nwnit.com (m) 919.830.5819 (o) 919.653.4489 -----Original Message----- From: "Anders Bruvik" <a.s.bruvik(a)usit.uio.no> To: "toasters(a)mathworks.com" <toasters(a)mathworks.com> Sent: 10/11/2007 9:29 AM Subject: Netapp, OS X and CIFS We have problems configuring for CIFS-file sharing against OS X clients. Domain controllers are Win 2003, OS X clients are 10.4.10, NetApp are FAS3050 running 7.2.3P2 and 7.0.5. In order to run cifs setup, we had to turn off netbios over tcp on the filers (if not, the filer could not communicate with the DC's). We use AD domain authentication. Now, windows-clients are able to connect to the filer, but OS X clients, which are not able to use SMB over TCP, are not able to connect. We can turn on netbios over tcp on the filer, this enables OS X clients to connect, if they use kerberos for authentication (which is perfectly acceptable). However, the filer will loose its connection with the DC (as reported by cifs testdc), and I have a feeling that this is not the correct way to configure this. So what is the recommended way to configure netapps for CIFS-file sharing in a mixed OS X and windows environment? Thanks in advance for any help. -- kind regards, Anders Skolseg Bruvik <a.s.bruvik(a)usit.uio.no> USIT (BSD), University of Oslo Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.

2 1

weird cifs problem
by Willeke, Jochen 11 Oct '07

11 Oct '07

Hi toasters, i have a weird cifs problem. We have a FAS6070 serving 350gb cifs space to several clients. The filer is about 50% CPU load and stats for the volume look great at all (response times are about 1ms). But the problem is once a user adds this share as an additional drive on his Windows XP the whole systems seems to get slow. I have done some tracing with wireshark and found out that the filer is responding very fast (always about 1ms or less like stats on the filer show as well) but after a request finished the client waits for about 14-70 ms for sending the next request. This seems to be some kind of client prob, but this can only be seen for that specific filer. When using another filer everything works as it is ought to. Has anybody ideas on that?? Rgds Jochen

1 0

Re: FUD?
by Jack Lyons 11 Oct '07

11 Oct '07

Thanks for all the comments. The comments came from a vendor who can't do dedupe, pointer based snapshots, flex clones, etc so they pull out the F(ear) U(ncertainity) and D(oubt) sales tool which says: if you can't beat it throw in something from left field and act as if it is a big deal.

5 4

Re: CIFS share creation security question
by Reinoud Reynders 11 Oct '07

11 Oct '07

Hi Scott, Very difficult question. The only thing what I can see is that you create 2 'root' shares on the 2 volumes. Than you create 2 DFS (distribute filesystem service from microsoft) trees (it's possible that you need two different windowsservers to separate the access control). Each department has full control on their dfs tree. They can create new shares in dfs, and use always the one root share on the filer as mount-path combined with the correct directories. It's a 'crazy' idea, but I think this must work. Good luck, Reinoud Reynders IT-manager Infrastructure & Operations UZ Leuven Belgium ----- Original Message ----- From: owner-toasters(a)mathworks.com <owner-toasters(a)mathworks.com> To: owner-toasters(a)mathworks.com <owner-toasters(a)mathworks.com>; toasters(a)mathworks.com <toasters(a)mathworks.com> Sent: Wed Oct 10 22:51:31 2007 Subject: CIFS share creation security question Quick question, is there anyway to allow AD users/groups the ability to create or delete cifs shares on specific volumes, but not others? Say we have an HR and Sales volume on the same filer. Each has their own IT personnel that create shares on each specific volume, but not each other's. Right now they are in the local admin group so they can theoretically do whatever they please, but we are looking for a more granular way to lock this down. Any suggestions? Thx! This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.

2 1

RE: CIFS share creation security question
by Kevin Parker 10 Oct '07

10 Oct '07

Not without V-filer/multistore. **Sent using wireless handheld... please excuse any typo's or brevity** Kevin Parker - NWN Corporation kparker(a)nwnit.com (m) 919.830.5819 (o) 919.653.4489 -----Original Message----- From: "scott.belisle(a)americas.bnpparibas.com" <scott.belisle(a)americas.bnpparibas.com> To: "owner-toasters(a)mathworks.com" <owner-toasters(a)mathworks.com>; "toasters(a)mathworks.com" <toasters(a)mathworks.com> Sent: 10/10/2007 5:38 PM Subject: CIFS share creation security question Quick question, is there anyway to allow AD users/groups the ability to create or delete cifs shares on specific volumes, but not others? Say we have an HR and Sales volume on the same filer. Each has their own IT personnel that create shares on each specific volume, but not each other's. Right now they are in the local admin group so they can theoretically do whatever they please, but we are looking for a more granular way to lock this down. Any suggestions? Thx! This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc. ________________________________ Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.

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