headers
Le Rouzic | 1 Jun 2007 13:23
Picon

Re: Kerberized NFS SetUp and Control Commands

J. Bruce Fields a écrit :

>On Wed, May 30, 2007 at 09:56:29AM +0200, Le Rouzic wrote:
>  
>
>>For those who fight regularly to install a kerberized nfs, you can find 
>>at http://nfsv4.bullopensource.org/
>>three commands to facilitate and controlling the setup of a linux 
>>kerberized NFS environmment:
>>
>>        - krbkdcsv  to setup a Kerberos KDC and a Kerberos 
>>administration Server
>>        - krbnfssv  to setup a Kerberos NFS Server
>>         -krbnfscl  to setup a Kerberos NFS Client
>>    
>>
>
>Thanks!  It's good to have people looking at how we can make this easier
>to set up.
>
>  
>
>>First, krbkdcsv has to be run on the machine choiced to be the Kerberos 
>>KDC and a Kerberos administration Server.
>>After, krbnfssv is run on the machine choiced to be the Kerberos NFS Server.
>>Then, krbnfscl is run on the machine to the Kerberos NFS Client.
>>    
>>
>
>I assume the three work just as well on their own.  (For example, in the
(Continue reading)

Permalink | Reply | 0 comments |
headers
Fredric Isaman | 1 Jun 2007 15:28
Picon
Favicon

Re: Referral in NFSv4


On Fri, 1 Jun 2007, Juilee Hapse wrote:

> Hi,
>
> Of the things you asked...
> 1. Can you do a normal v4 mount of dfswin1:/vicepa?
> --> yes this can be done.
>
> 2. firewall issue.
> --> firewall is disabled on all 3 m/cs ( 2 servers and one client)
>
> 3. Network trace.
> --> Have taken one through wireshark. Attaching that file.
>
> 4. Versions of client and server:
> ---> server is 2.6.18 (both the servers)
> ---> client 2.6.20
>
> Also attaching the logs for  client/server output of :
> #tail -f /var/log/messages
>
>
> Thanks,
> Juilee
>
>

The vanilla 2.6.18 server does not support referrals (though there are 
CITI patches that add support...the closest I see archived on our site is
(Continue reading)

Permalink | Reply | 4 comments |
headers
Juilee Hapse | 1 Jun 2007 20:35
Picon

Re: Referral in NFSv4

Hi,
 Ok will upgrade servers. I had referred to :

http://www.citi.umich.edu/projects/nfsv4/linux/using-referrals.html

On this page its mentioned server should be at 2.6.18 and client at 2.6.20. :(

Anyways thanks alot,

 Juilee


On 6/1/07, Fredric Isaman <iisaman <at> citi.umich.edu > wrote:


On Fri, 1 Jun 2007, Juilee Hapse wrote:

> Hi,
>
> Of the things you asked...
> 1. Can you do a normal v4 mount of dfswin1:/vicepa?
> --> yes this can be done.
>
> 2. firewall issue.
> --> firewall is disabled on all 3 m/cs ( 2 servers and one client)
>
> 3. Network trace.
> --> Have taken one through wireshark. Attaching that file.
>
> 4. Versions of client and server:
> ---> server is 2.6.18 (both the servers)
> ---> client 2.6.20
>
> Also attaching the logs for  client/server output of :
> #tail -f /var/log/messages
>
>
> Thanks,
> Juilee
>
>

The vanilla 2.6.18 server does not support referrals (though there are
CITI patches that add support...the closest I see archived on our site is
<http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.18-rc6-1/linux-2.6.18-rc6-CITI_NFS4_ALL-1.diff >)
Server support was added to the vanilla kernel for 2.6.19.

        Fred


_______________________________________________
NFSv4 mailing list
NFSv4 <at> linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
Permalink | Reply | 1 comment |
headers
Fredric Isaman | 1 Jun 2007 20:46
Picon
Favicon

Re: Referral in NFSv4


On Sat, 2 Jun 2007, Juilee Hapse wrote:

> Hi,
> Ok will upgrade servers. I had referred to :
>
> http://www.citi.umich.edu/projects/nfsv4/linux/using-referrals.html
>
> On this page its mentioned server should be at 2.6.18 and client at 2.6.20.
> :(
>
> Anyways thanks alot,
>
> Juilee
>

Sorry for the trouble.  I've fixed the webpage.

 	Fred
Permalink | Reply | 0 comments |
headers
Steve Dickson | 2 Jun 2007 12:34
Picon
Favicon

Re: Referral in NFSv4


Fredric Isaman wrote:
> The vanilla 2.6.18 server does not support referrals (though there are 
> CITI patches that add support...the closest I see archived on our site is 
>
<http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.18-rc6-1/linux-2.6.18-rc6-CITI_NFS4_ALL-1.diff>) 
> Server support was added to the vanilla kernel for 2.6.19.
FYI... Referrals are supported in the latest nfs-utils and kernel in
Fedora Core 6 and 7.

steved.
Permalink | Reply | 1 comment |
headers
Kevin Coffman | 2 Jun 2007 17:10
Picon
Favicon

Re: nfs-utils 1.1.0

Sorry, I need to update our web page.  All the _necessary_ patches are
currently in 1.1.0.  We have some local changes for new features and
enhancements (like secinfo), but I am not sure they are ready for the
public yet.

On 5/30/07, Guillaume Rousse <Guillaume.Rousse <at> inria.fr> wrote:
> I saw nfs-utils 1.1.0 was out, with several nfs4-related changes.
>
> They are still no nfs4 patches available at
> http://www.citi.umich.edu/projects/nfsv4/linux/nfs-utils-patches/,
> tough. Have they all been merged, or is just work in progress to produce
> a new patch set ?
> --
> Guillaume Rousse
> Moyens Informatiques - INRIA Futurs
> Tel: 01 69 35 69 62
Permalink | Reply | 0 comments |
headers
Juilee Hapse | 4 Jun 2007 06:39
Picon

Re: Referral in NFSv4

Hi,
  Thanks for the info. Will be upgrading to kernel 2.6.22 and nfs-utils 1.0.11.
Reference:
http://www.citi.umich.edu/projects/nfsv4/linux/

Thanks,
Juilee

On 6/2/07, Steve Dickson <SteveD <at> redhat.com> wrote:


Fredric Isaman wrote:
> The vanilla 2.6.18 server does not support referrals (though there are
> CITI patches that add support...the closest I see archived on our site is
> < http://www.citi.umich.edu/projects/nfsv4/linux/kernel-patches/2.6.18-rc6-1/linux-2.6.18-rc6-CITI_NFS4_ALL-1.diff>)
> Server support was added to the vanilla kernel for 2.6.19.
FYI... Referrals are supported in the latest nfs-utils and kernel in
Fedora Core 6 and 7.

steved.


_______________________________________________
NFSv4 mailing list
NFSv4 <at> linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
Permalink | Reply | 0 comments |
headers
Avishay Traeger | 4 Jun 2007 17:55
Picon
Favicon

Changing the grace period

Hello,
I have a few questions about changing the grace period (I want to make
it shorter for testing purposes since 90 seconds is annoying).

1. Is there any way to do this without modifying the code?  From what I
can see, there isn't.

2. I looked at ways to change the lease times, because grace_time relies
on those.  In 2.6.22-rc3, in nfsctl.c line 591, it says:
extern time_t nfs4_leasetime(void);

>From what I can tell, this is a typo, and should be nfs4_lease_time
(underscore between "lease" and "time").  Correct?

3. Also, the proc file doesn't seem to be functioning properly:
[root <at> v4server]# echo 80 > /proc/fs/nfsd/nfsv4leasetime 
[root <at> v4server]# cat /proc/fs/nfsd/nfsv4leasetime 
90
In addition, nothing is printed in dmesg after the echo (probably
related to that typo?).

4. The comment in write_leasetime() says:
/* if size > 10 seconds, call
 * nfs4_reset_lease() then write out the new lease (seconds) as reply
 */
However, nfs4_reset_lease() changes the user_lease_time variable.  The
print statement calls nfs4_lease_time() which prints the lease_time
variable.  So it looks like you are changing one variable and then
printing the other.  Is this intentional?

Thanks,
Avishay
Permalink | Reply | 501 comments |
headers
J. Bruce Fields | 4 Jun 2007 18:27

Re: Changing the grace period

On Mon, Jun 04, 2007 at 11:55:29AM -0400, Avishay Traeger wrote:
> I have a few questions about changing the grace period (I want to make
> it shorter for testing purposes since 90 seconds is annoying).
> 
> 1. Is there any way to do this without modifying the code?  From what I
> can see, there isn't.

If I remember correctly, the way it's supposed to work is you write to
/proc/fs/nfsd/nfsv4leasetime, then restart nfsd, and the new lease time
will take effect on the restart.

> 2. I looked at ways to change the lease times, because grace_time relies
> on those.  In 2.6.22-rc3, in nfsctl.c line 591, it says:
> extern time_t nfs4_leasetime(void);
> 
> >From what I can tell, this is a typo,

Yes, looks like it.

> and should be nfs4_lease_time
> (underscore between "lease" and "time").  Correct?

I think that declaration shouldn't be there at all.

> 3. Also, the proc file doesn't seem to be functioning properly:
> [root <at> v4server]# echo 80 > /proc/fs/nfsd/nfsv4leasetime 
> [root <at> v4server]# cat /proc/fs/nfsd/nfsv4leasetime 
> 90
> In addition, nothing is printed in dmesg after the echo (probably
> related to that typo?).

It will show the new value after a reboot.  I agree that that's
confusing.

> 4. The comment in write_leasetime() says:
> /* if size > 10 seconds, call
>  * nfs4_reset_lease() then write out the new lease (seconds) as reply
>  */
> However, nfs4_reset_lease() changes the user_lease_time variable.  The
> print statement calls nfs4_lease_time() which prints the lease_time
> variable.  So it looks like you are changing one variable and then
> printing the other.  Is this intentional?

Yes, so it's the comment that's wrong.  But maybe we should be doing
this differently.

--b.
Permalink | Reply | 501 comments |
headers
J. Bruce Fields | 4 Jun 2007 19:01

Re: Changing the grace period

On Mon, Jun 04, 2007 at 12:27:08PM -0400, J. Bruce Fields wrote:
> On Mon, Jun 04, 2007 at 11:55:29AM -0400, Avishay Traeger wrote:
> > I have a few questions about changing the grace period (I want to make
> > it shorter for testing purposes since 90 seconds is annoying).
> > 
> > 1. Is there any way to do this without modifying the code?  From what I
> > can see, there isn't.
> 
> If I remember correctly, the way it's supposed to work is you write to
> /proc/fs/nfsd/nfsv4leasetime, then restart nfsd, and the new lease time
> will take effect on the restart.

(And what you probably actually want to do is put an

	echo 10 >/proc/fs/nfsd/nfsv4leasetime

right before the rpc.nfsd call in your nfs server init script.)

--b.
Permalink | Reply | 0 comments |

Gmane