Hello,
I've updated the Fedora pNFS development repository to include the
Fedora 13, 14 and Devel kernels that have the latest pNFS bits:
Tag: pnfs-all-2.6.35-2010-08-24 for Fedora 13 and 14 kernels
Tag: pnfs-all-2.6.36-rc3-2010-08-30 for Devel/f15 kernels
(Note: there are also kernel-debuginfo and kernel-devel rpms for people who
use things like systemtap probes and crash).
I've also updated the pNFS-enabled nfs-utils in all three releases.
Instructions on how to install and use these kernels are at:
http://wiki.linux-nfs.org/wiki/index.php/Fedora_pNFS_Client_Setup
If/when bugs are found with these rpms please enter them
in to the NFS Bugzilla Main Page at:
https://bugzilla.linux-nfs.org/index.cgi
Please use the "pNFS" keyword..
Any question or issues please feel free to contact me...
steved.
Steve Dickson wrote:
On 10/01/2010 09:51 AM, Tigran Mkrtchyan wrote:
>
> Hi Steve,
>
> thanks for the builds. What I am missing is modprobe configuration file
> which I have to add myself.
Unfortunately yes... I have not figured out a good way to have
the mobprobe done on the client since, in general, init scripts
don't run on the client (with the exception of rpc.statd and rpc.gssd).
I guess I could come up with an pnfs init script..but that
seems like a bit overkill just to do a modprobe...
I've already got an init script for the block layout client that does the
modprobe and starts the daemon. How about we generalize it to modprobe the
other modules too, and call it the pnfs init script?
Steve Dickson wrote:
Hello,
I've updated the Fedora pNFS development repository to include the
Fedora 13, 14 and Devel kernels that have the latest pNFS bits:
Tag: pnfs-all-2.6.35-2010-09-14 for Fedora 13 and 14 kernels
Tag: pnfs-all-latest for Devel/f15 kernels
(Note: there are also kernel-debuginfo and kernel-devel rpms for people who
use things like systemtap probes and crash).
I would be very interested in hearing from anyone using the block layout
client, either positive or negative experiences.
On 10/01/2010 09:57 PM, Steve Dickson wrote:
>
> On 10/01/2010 09:51 AM, Tigran Mkrtchyan wrote:
>
>> Hi Steve,
>>
>> thanks for the builds. What I am missing is modprobe configuration file
>> which I have to add myself.
>>
> Unfortunately yes... I have not figured out a good way to have
> the mobprobe done on the client since, in general, init scripts
> don't run on the client (with the exception of rpc.statd and rpc.gssd).
>
> I guess I could come up with an pnfs init script..but that
> seems like a bit overkill just to do a modprobe...
>
>
I include /etc/modprobe.d/nfsv41 into rpms which I build for our
systems (RHEL5) with following content:
alias nfs-layouttype4-1 nfs_layout_nfsv41_files
alias nfs-layouttype4-2 off
alias nfs-layouttype4-3 off
and following into the spec file:
%config(noreplace) /etc/modprobe.d/nfsv41
I made it part of kernel rpm, but may be nfs-utils is more appropriate
place.
Regards,
Tigran.
> steved.
>
>
>> thanks,
>> Tigran.
>>
>> On 10/01/2010 01:04 PM, Steve Dickson wrote:
>>
>>> Hello,
>>>
>>> I've updated the Fedora pNFS development repository to include the
>>> Fedora 13, 14 and Devel kernels that have the latest pNFS bits:
>>>
>>> Tag: pnfs-all-2.6.35-2010-09-14 for Fedora 13 and 14 kernels
>>> Tag: pnfs-all-latest for Devel/f15 kernels
>>>
>>> (Note: there are also kernel-debuginfo and kernel-devel rpms for people who
>>> use things like systemtap probes and crash).
>>>
>>> I have not updated the nfs-utils rpms because I'm waiting
>>> for a fix to a problem in rpc.mountd. Once the problem is resolve
>>> I'll update those rpms as well...
>>>
>>> Instructions on how to install and use these kernels are at:
>>> http://wiki.linux-nfs.org/wiki/index.php/Fedora_pNFS_Client_Setup
>>>
>>> If/when bugs are found with these rpms please enter them
>>> in to the NFS Bugzilla Main Page at:
>>> https://bugzilla.linux-nfs.org/index.cgi
>>>
>>> Please use the "pNFS" keyword..
>>>
>>> Any question or issues please feel free to contact me...
>>>
>>> steved.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to [email protected]
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
With recent code, you don't need a modprobe on the client. All you
need to do is set up an alias.
In some /etc/modprobe.d file put:
alias nfs-layouttype4-1 nfs_layout_nfsv41_files
Fred
On Fri, Oct 1, 2010 at 3:57 PM, Steve Dickson <[email protected]> wrote:
>
>
> On 10/01/2010 09:51 AM, Tigran Mkrtchyan wrote:
>>
>> Hi Steve,
>>
>> thanks for the builds. What I am missing is modprobe configuration file
>> which I have to add myself.
> Unfortunately yes... I have not figured out a good way to have
> the mobprobe done on the client since, in general, init scripts
> don't run on the client (with the exception of rpc.statd and rpc.gssd).
>
> I guess I could come up with an pnfs init script..but that
> seems like a bit overkill just to do a modprobe...
>
> steved.
>
>>
>> thanks,
>> ? ?Tigran.
>>
>> On 10/01/2010 01:04 PM, Steve Dickson wrote:
>>> Hello,
>>>
>>> I've updated the Fedora pNFS development repository to include the
>>> Fedora 13, 14 and Devel kernels that have the latest pNFS bits:
>>>
>>> ? ? ?Tag: pnfs-all-2.6.35-2010-09-14 ? ? for Fedora 13 and 14 kernels
>>> ? ? ?Tag: pnfs-all-latest ? ? ? ? ? ? ? ?for Devel/f15 kernels
>>>
>>> (Note: there are also kernel-debuginfo and kernel-devel rpms for people who
>>> use things like systemtap probes and crash).
>>>
>>> I have not updated the nfs-utils rpms because I'm waiting
>>> for a fix to a problem in rpc.mountd. Once the problem is resolve
>>> I'll update those rpms as well...
>>>
>>> Instructions on how to install and use these kernels are at:
>>> http://wiki.linux-nfs.org/wiki/index.php/Fedora_pNFS_Client_Setup
>>>
>>> ? If/when bugs are found with these rpms please enter them
>>> in to the NFS Bugzilla Main Page at:
>>> ? ? ?https://bugzilla.linux-nfs.org/index.cgi
>>>
>>> Please use the "pNFS" keyword..
>>>
>>> Any question or issues please feel free to contact me...
>>>
>>> steved.
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>>> the body of a message to [email protected]
>>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to [email protected]
>> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
On 10/02/2010 08:45 AM, Tigran Mkrtchyan wrote:
> On 10/01/2010 09:57 PM, Steve Dickson wrote:
>>
>> On 10/01/2010 09:51 AM, Tigran Mkrtchyan wrote:
>>
>>> Hi Steve,
>>>
>>> thanks for the builds. What I am missing is modprobe configuration file
>>> which I have to add myself.
>>>
>> Unfortunately yes... I have not figured out a good way to have
>> the mobprobe done on the client since, in general, init scripts
>> don't run on the client (with the exception of rpc.statd and rpc.gssd).
>>
>> I guess I could come up with an pnfs init script..but that
>> seems like a bit overkill just to do a modprobe...
>>
>>
> I include /etc/modprobe.d/nfsv41 into rpms which I build for our
> systems (RHEL5) with following content:
>
> alias nfs-layouttype4-1 nfs_layout_nfsv41_files
> alias nfs-layouttype4-2 off
> alias nfs-layouttype4-3 off
>
>
> and following into the spec file:
>
> %config(noreplace) /etc/modprobe.d/nfsv41
>
> I made it part of kernel rpm, but may be nfs-utils is more appropriate
> place.
Very cool... I try to incorporate this into the upcoming nfs-utils...
Because at the end of day, the distro "powers to be" are really
against more init scripts... more init script means a longer time
to boot... and it seems fast reboots are the new in thing to have...
(which is a good thing.. :-) )
steved.
On Fri, Oct 1, 2010 at 4:07 PM, Jim Rees <[email protected]> wrote:
> Steve Dickson wrote:
>
> ?On 10/01/2010 09:51 AM, Tigran Mkrtchyan wrote:
> ?>
> ?> Hi Steve,
> ?>
> ?> thanks for the builds. What I am missing is modprobe configuration file
> ?> which I have to add myself.
> ?Unfortunately yes... I have not figured out a good way to have
> ?the mobprobe done on the client since, in general, init scripts
> ?don't run on the client (with the exception of rpc.statd and rpc.gssd).
>
> ?I guess I could come up with an pnfs init script..but that
> ?seems like a bit overkill just to do a modprobe...
>
> I've already got an init script for the block layout client that does the
> modprobe and starts the daemon. ?How about we generalize it to modprobe the
> other modules too, and call it the pnfs init script?
The current code is designed to request the loading of the module as
needed. All that is needed is an alias, of the type
alias nfs-layouttype4-[INTEGER_ID] ACTUAL_MODULE_NAME
Fred
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to [email protected]
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>