X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C81759.E7140AD4@onstor-exch02.onstor.net>; Thu, 25 Oct 2007 14:53:47 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81759.E7140AD4"
Content-class: urn:content-classes:message
Subject: RE: Enabling/Disabling NFS shares
Date: Thu, 25 Oct 2007 14:53:47 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E063836D3@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E063836CB@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Enabling/Disabling NFS shares
Thread-Index: AcgXVzRkwbsK2rm5S5GfIQAtinbCqAAADBGQAAAnSSAAAAd6sAAAQS/gAAARjqAAABTdoA==
References: <BB375AF679D4A34E9CA8DFA650E2B04E063836A0@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E063836A9@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E063836AE@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E063836B3@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E063836C5@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E063836CB@onstor-exch02.onstor.net>
From: "Eric Barrett" <eric.barrett@onstor.com>
To: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Jonathan Goldick" <jonathan.goldick@onstor.com>,
	"Huy Duong" <huy.duong@onstor.com>,
	"dl-Customer Service Group" <csgroup@onstor.com>,
	"dl-se" <dl-se@onstor.com>,
	"dl-Software" <dl-software@onstor.com>,
	"dl-QA" <dl-qa@onstor.com>
Cc: "Narayan Venkat" <narayan.venkat@onstor.com>,
	"Joshua Goldenhar" <joshua.goldenhar@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C81759.E7140AD4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

That, and "vsvr disable" and "vol offline" tend to have lots of
dependencies, and be very slow, so usually the system is down before you
can finish them.  So if we get rid of the "nfs share disable" commands,
we need to ensure "vsvr disable" takes effect immediately, or at least
is remembered after reboot even if the system crashes a couple of
seconds into the disable process.


> _____________________________________________=20
> From: 	Maxim Kozlovsky =20
> Sent:	Thursday, October 25, 2007 3:52 PM
> To:	Jonathan Goldick; Huy Duong; dl-Customer Service Group; dl-se;
> dl-Software; dl-QA
> Cc:	Narayan Venkat; Joshua Goldenhar
> Subject:	RE: Enabling/Disabling NFS shares
>=20
> What if you have a multiprotocol volume and only NFS clients cause a
> crash? Disabling NFS shares allows CIFS users to continue working
> until the problem is fixed. Or if you know the client, you can disable
> only affected share.
>=20
> _____________________________________________
> From: Jonathan Goldick=20
> Sent: Thursday, October 25, 2007 3:50 PM
> To: Maxim Kozlovsky; Huy Duong; dl-Customer Service Group; dl-se;
> dl-Software; dl-QA
> Cc: Narayan Venkat; Joshua Goldenhar
> Subject: RE: Enabling/Disabling NFS shares
>=20
> The same thing is achieved by 'volume offline" or "vsvr disable" or
> disabling the IP addresses and it takes all protocols into account.
>=20
>=20
> _____________________________________________
> From: Maxim Kozlovsky=20
> Sent: Thursday, October 25, 2007 3:42 PM
> To: Huy Duong; Jonathan Goldick; dl-Customer Service Group; dl-se;
> dl-Software; dl-QA
> Cc: Narayan Venkat; Joshua Goldenhar
> Subject: RE: Enabling/Disabling NFS shares
>=20
> CIFS clients usually don't try to reconnect and do exactly the same
> thing after a failure. They know better - after all, the product was
> developed by Microsoft.
>=20
> _____________________________________________
> From: Huy Duong=20
> Sent: Thursday, October 25, 2007 3:40 PM
> To: Maxim Kozlovsky; Jonathan Goldick; dl-Customer Service Group;
> dl-se; dl-Software; dl-QA
> Cc: Narayan Venkat; Joshua Goldenhar
> Subject: RE: Enabling/Disabling NFS shares
>=20
> WE should have one or CIFS now that you mention it :-)=20
>=20
> _____________________________________________
> From: Maxim Kozlovsky=20
> Sent: Thursday, October 25, 2007 3:39 PM
> To: Jonathan Goldick; dl-Customer Service Group; dl-se; dl-Software;
> dl-QA
> Cc: Narayan Venkat; Joshua Goldenhar
> Subject: RE: Enabling/Disabling NFS shares
>=20
> I think it was useful when we entered a crash loop because of a bug in
> NFS. Disabling a share prevents a client from connecting and crashing
> the system. Since the occurrences of NFS crash loops became much less
> frequent, the command lost most of its usefulness.
>=20
> (I think we should preserve it, since when we will go to systemx we
> are bound to have some crash loops. :-) )
>=20
> _____________________________________________
> From: Jonathan Goldick=20
> Sent: Thursday, October 25, 2007 3:34 PM
> To: dl-Customer Service Group; dl-se; dl-Software; dl-QA
> Cc: Narayan Venkat; Joshua Goldenhar
> Subject: Enabling/Disabling NFS shares
>=20
> This question is in the context of SystemX but about the current
> product.
>=20
> We have a command to enable/disable NFS shares but not one for CIFS
> shares.  "nfs disable share [all | PATHNAME]"
>=20
> Does anyone ever use these commands given that they do not prevent
> CIFS users from connecting and CIFS has no equivalent?  I'm trying to
> determine whether to preserve the functionality in SystemX given the
> limited value.
>=20
> Unless I hear otherwise, this is going away in SystemX.
>=20

------_=_NextPart_001_01C81759.E7140AD4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7652.24">
<TITLE>RE: Enabling/Disabling NFS shares</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT SIZE=3D2 FACE=3D"Arial">That, and &quot;vsvr disable&quot; and =
&quot;vol offline&quot; tend to have lots of dependencies, and be very =
slow, so usually the system is down before you can finish them.&nbsp; So =
if we get rid of the &quot;nfs share disable&quot; commands, we need to =
ensure &quot;vsvr disable&quot; takes effect immediately, or at least is =
remembered after reboot even if the system crashes a couple of seconds =
into the disable process.</FONT></P>
<BR>

<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Maxim Kozlovsky&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Thursday, October 25, 2007 3:52 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Jonathan Goldick; Huy Duong; dl-Customer Service Group; =
dl-se; dl-Software; dl-QA</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Cc:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Narayan Venkat; Joshua Goldenhar</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: Enabling/Disabling NFS =
shares</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">What if you have a =
multiprotocol volume and only NFS clients cause a crash? Disabling NFS =
shares allows CIFS users to continue working until the problem is fixed. =
Or if you know the client, you can disable only affected =
share.</FONT></P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jonathan Goldick<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, October 25, 2007 3:50 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Maxim Kozlovsky; Huy Duong; dl-Customer Service Group; =
dl-se; dl-Software; dl-QA<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Narayan Venkat; Joshua Goldenhar<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Enabling/Disabling NFS shares</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">The same thing is =
achieved by &#8216;volume offline&#8221; or &#8220;vsvr disable&#8221; =
or disabling the IP addresses and it takes all protocols into =
account.</FONT></P>
<BR>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, October 25, 2007 3:42 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Huy Duong; Jonathan Goldick; dl-Customer Service Group; =
dl-se; dl-Software; dl-QA<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Narayan Venkat; Joshua Goldenhar<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Enabling/Disabling NFS shares</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">CIFS clients usually =
don&#8217;t try to reconnect and do exactly the same thing after a =
failure. They know better - after all, the product was developed by =
Microsoft.</FONT></P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Huy Duong<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, October 25, 2007 3:40 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Maxim Kozlovsky; Jonathan Goldick; dl-Customer Service =
Group; dl-se; dl-Software; dl-QA<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Narayan Venkat; Joshua Goldenhar<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Enabling/Disabling NFS shares</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">WE should have one or =
CIFS now that you mention it</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Wingdings">J</FONT><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial"> </FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Maxim Kozlovsky<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, October 25, 2007 3:39 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jonathan Goldick; dl-Customer Service Group; dl-se; =
dl-Software; dl-QA<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Narayan Venkat; Joshua Goldenhar<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: Enabling/Disabling NFS shares</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I think it was useful =
when we entered a crash loop because of a bug in NFS. Disabling a share =
prevents a client from connecting and crashing the system. Since the =
occurrences of NFS crash loops became much less frequent, the command =
lost most of its usefulness.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">(I think we should =
preserve it, since when we will go to systemx we are bound to have some =
crash loops.</FONT> <FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Wingdings">J</FONT><FONT COLOR=3D"#000080" SIZE=3D2 =
FACE=3D"Arial"> )</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jonathan Goldick<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, October 25, 2007 3:34 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Customer Service Group; dl-se; dl-Software; =
dl-QA<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Cc:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Narayan Venkat; Joshua Goldenhar<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> Enabling/Disabling NFS shares</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This question is in the context of =
SystemX but about the current product.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">We have a command to enable/disable NFS =
shares but not one for CIFS shares.&nbsp; &#8220;nfs disable share [all =
| PATHNAME]&#8221;</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Does anyone ever use these commands =
given that they do not prevent CIFS users from connecting and CIFS has =
no equivalent?&nbsp; I&#8217;m trying to determine whether to preserve =
the functionality in SystemX given the limited value.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Unless I hear otherwise, this is going =
away in SystemX.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C81759.E7140AD4--
