Re: Finding out which client has mapped a share?

List overview All Threads
Download

newer

older

ssh related errors in filer's...

Finding out which client has...

John Stoffel

30 Jun 2011 30 Jun '11

8:40 p.m.

Kyle> How about cifs sessions *? supportnetapp01> cifs sessions *

Doesn't seem to work. When I do this command, I don't see any clients mapping this share, but it still won't let me delete it.

Very frustrating.

John

Show replies by date

Fultz, Jeff

30 Jun 30 Jun

9:10 p.m.

New subject: Finding out which client has mapped a share?

Please try "cifs sessions -s"

bash-2.03$ rsh exchfiler3.extest cifs sessions -s

users Security Information

10.55.65.2(JEFFF1-LXP) (extest\1 - root) *************** UNIX uid = 0 user is a member of group daemon (1) user is a member of group daemon (1)

NT membership EXTEST\1 EXTEST\Exchange Services EXTEST\Domain Admins EXTEST\Domain Users EXTEST\Exchange Domain Servers EXTEST\admin_global EXTEST\Exchange Public Folder Administrators EXTEST\Exchange Organization Administrators EXTEST\Exchange View-Only Administrators EXTEST\Exchange Server Administrators (e21a) EXTEST\admin_universal EXTEST\Schema Admins EXTEST\Enterprise Admins EXTEST\Exchange Recipient Administrators EXTEST\DnsAdmins EXTEST\Debugger Users EXTEST\SQLServer2005SQLAgentUser$MSSQLSERVER EXTEST\SQLServer2005MSSQLUser$MSSQLSERVER EXTEST\Exchange Enterprise Servers EXTEST\SQLServer2005SQLBrowserUser EXTEST\domain _local BUILTIN\Administrators BUILTIN\Users User is also a member of Everyone, Network Users, Authenticated Users *************** bash-2.03$

Thanks Jeff Fultz Netapp MEI Senior QA Software Engineer 916-933-7120

Dont let the impossibilty of the ideal keep you from doing something constructive.

-----Original Message----- From: John Stoffel [mailto:john.stoffel@taec.toshiba.com] Sent: Thursday, June 30, 2011 1:40 PM To: Kyle Oliver Cc: John Stoffel; toasters@mathworks.com Subject: Re: Finding out which client has mapped a share?

Kyle> How about cifs sessions *? supportnetapp01> cifs sessions *

Doesn't seem to work. When I do this command, I don't see any clients mapping this share, but it still won't let me delete it.

Very frustrating.

John

Clark, Andre

9:24 p.m.

New subject: Finding out which client has mapped a share?

Try the following from cli:

netapp> cifs terminate ; cifs shares -delete -f applications ; cifs restart

The semicolon ';' allows you to chain multiple commands into one line.

Regards, André M. Clark | Sr. Consulting Engineer, Team Lead | Insight Integrated Systems | 718.360.8701 Tell me I will forget... Show me I may remember... Involve me I WILL UNDERSTAND!!! Start by doing what's necessary, then what's possible, and suddenly you are doing the impossible!!!

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of John Stoffel Sent: Thursday, June 30, 2011 16:40 To: Kyle Oliver Cc: John Stoffel; toasters@mathworks.com Subject: Re: Finding out which client has mapped a share?

Kyle> How about cifs sessions *? supportnetapp01> cifs sessions *

Doesn't seem to work. When I do this command, I don't see any clients mapping this share, but it still won't let me delete it.

Very frustrating.

John

Clark, Andre

9:25 p.m.

New subject: Finding out which client has mapped a share?

Modification

netapp> cifs terminate -t 0 ; cifs shares -delete -f applications ; cifs restart

-----Original Message----- From: Clark, Andre Sent: Thursday, June 30, 2011 17:24 To: 'John Stoffel'; Kyle Oliver Cc: toasters@mathworks.com Subject: RE: Finding out which client has mapped a share?

Try the following from cli:

netapp> cifs terminate ; cifs shares -delete -f applications ; cifs restart

The semicolon ';' allows you to chain multiple commands into one line.

Kyle> How about cifs sessions *? supportnetapp01> cifs sessions *

Doesn't seem to work. When I do this command, I don't see any clients mapping this share, but it still won't let me delete it.

Very frustrating.

John

Kießl Walter

1 Jul 1 Jul

5:26 a.m.

New subject: AW: Finding out which client has mapped a share?

I have seen this, too.

Perhaps some locks on the directory/share?

You can check cifs locks with "lock status -p cifs" and search for the share/directory in the output. There is a "lock break" command, too. But be careful with using this. I've seen a filer panic when issuing this command ...

i. A. Dipl.-Inform. (FH) Walter J. Kießl

------------------------------------------------------------ mailto:kiessl@heidenhain.de tel.: +49 8669 31 1954 fax: +49 8669 32 1954 ------------------------------------------------------------

DR. JOHANNES HEIDENHAIN GmbH Dr.-Johannes-Heidenhain-Str. 5 83301 Traunreut, Deutschland http://www.heidenhain.de/

-----Ursprüngliche Nachricht----- Von: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Im Auftrag von John Stoffel Gesendet: Donnerstag, 30. Juni 2011 22:40 An: Kyle Oliver Cc: John Stoffel; toasters@mathworks.com Betreff: Re: Finding out which client has mapped a share?

Kyle> How about cifs sessions *? supportnetapp01> cifs sessions *

Doesn't seem to work. When I do this command, I don't see any clients mapping this share, but it still won't let me delete it.

Very frustrating.

John

------------------------------------------------------------------------------------------------------- Registergericht: Traunstein / Registry Court: HRB 275 – Sitz / Head Office: Traunreut Aufsichtsratsvorsitzender / Chairman of Supervisory Board: Rainer Burkhard Geschäftsführung / Management Board: Thomas Sesselmann (Vorsitzender / Chairman), Michael Grimm, Matthias Fauser, Sebastian Tondorf

E-Mail Haftungsausschluss / E-Mail Disclaimer: http://www.heidenhain.de/disclaimer

Page, Jeremy

12:28 p.m.

New subject: Finding out which client has mapped a share?

We've run into this too with 7.3.2. Even a cifs terminate does not always let you remove the share (it basically hangs). We've had to fail the head to get it to stop. I am not sure what the problem is but it seems to happen on our busiest volumes only (maybe 1k concurrent CIFS users).

-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Kießl Walter Sent: Friday, July 01, 2011 1:27 AM To: John Stoffel Cc: toasters@mathworks.com Subject: AW: Finding out which client has mapped a share?

I have seen this, too.

Perhaps some locks on the directory/share?

i. A. Dipl.-Inform. (FH) Walter J. Kießl

------------------------------------------------------------ mailto:kiessl@heidenhain.de tel.: +49 8669 31 1954 fax: +49 8669 32 1954 ------------------------------------------------------------

DR. JOHANNES HEIDENHAIN GmbH Dr.-Johannes-Heidenhain-Str. 5 83301 Traunreut, Deutschland http://www.heidenhain.de/

Kyle> How about cifs sessions *? supportnetapp01> cifs sessions *

Doesn't seem to work. When I do this command, I don't see any clients mapping this share, but it still won't let me delete it.

Very frustrating.

John

Please be advised that this email may contain confidential information. If you are not the intended recipient, please notify us by email by replying to the sender and delete this message. The sender disclaims that the content of this email constitutes an offer to enter into, or the acceptance of, any agreement; provided that the foregoing does not invalidate the binding effect of any digital or other electronic reproduction of a manual signature that is included in any attachment.

Steve Losen

1:11 p.m.

New subject: Finding out which client has mapped a share?

...

We've run into this too with 7.3.2. Even a cifs terminate does not always let you remove the share (it basically hangs). We've had to fail the head to get it to stop. I am not sure what the problem is but it seems to happen on our busiest volumes only (maybe 1k concurrent CIFS users).

I think I hit this when I upgraded a filer to 8.0.1. I installed the 8.0.1 (download took a long time) and when I ran halt -t 0 CIFS failed to terminate, so the filer would not reboot. I tried "cifs terminate -t 0" and got the same error (CIFS not terminating). I finally had to halt -d and when the filer came back up I had to wait a long time for the core file to be saved. And then I saw that it was still running 7.3. Not knowing how to boot the 8.0.1 kernel, I quickly ran cifs terminate -t 0 (which worked, thankfully) and installed 8.0.1 again (and sat through that long download again). Then I was able to reboot and come up running 8.0.1. Whew! But that downtime was a LOT longer than we expected. The core dump and second download took about an hour.

Steve Losen scl@virginia.edu phone: 434-924-0640

University of Virginia ITC Unix Support

John Stoffel

3:06 p.m.

New subject: Finding out which client has mapped a share?

Jeremy> We've run into this too with 7.3.2. Even a cifs terminate Jeremy> does not always let you remove the share (it basically Jeremy> hangs). We've had to fail the head to get it to stop. I am not Jeremy> sure what the problem is but it seems to happen on our busiest Jeremy> volumes only (maybe 1k concurrent CIFS users).

Wonderful. How hard is it to get CIFS to terminate? Anyway, we've had no luck getting this filer (FAS2050, 7.2.6.1P8) to shutdown CIFS so we can remove this share.

So it looks like a reboot is in order here.

But, we've determined that we can do an upgrade to OnTap 7.3.5.1 to get larger volume DeDupe size support, so hopefully doing an upgrade will help this issue in the future.

Thank for all the suggestions and help, I really appreciate it.

John

Page, Jeremy

3:07 p.m.

New subject: Finding out which client has mapped a share?

Essentially we had to reboot. We're clustered so I just did a cf takeover. Sorry :(

-----Original Message----- From: John Stoffel [mailto:john.stoffel@taec.toshiba.com] Sent: Friday, July 01, 2011 11:06 AM To: Page, Jeremy Cc: Kießl Walter; John Stoffel; toasters@mathworks.com Subject: RE: Finding out which client has mapped a share?

Jeremy> We've run into this too with 7.3.2. Even a cifs terminate does Jeremy> not always let you remove the share (it basically hangs). We've Jeremy> had to fail the head to get it to stop. I am not sure what the Jeremy> problem is but it seems to happen on our busiest volumes only Jeremy> (maybe 1k concurrent CIFS users).

Wonderful. How hard is it to get CIFS to terminate? Anyway, we've had no luck getting this filer (FAS2050, 7.2.6.1P8) to shutdown CIFS so we can remove this share.

So it looks like a reboot is in order here.

But, we've determined that we can do an upgrade to OnTap 7.3.5.1 to get larger volume DeDupe size support, so hopefully doing an upgrade will help this issue in the future.

Thank for all the suggestions and help, I really appreciate it.

John

4928

Age (days ago)

4929

Last active (days ago)

toasters@lists.teaparty.net

8 comments

6 participants

tags (0)

participants (6)

Clark, Andre
Fultz, Jeff
John Stoffel
Kießl Walter
Page, Jeremy
Steve Losen