Hi ,
When i was checking lockd recovery ,
i noted that clients after getting
notification messages , use mon_id
as destination address and not notication
messages's source address as destination
address.(as just a reply)
Is there any issue in using notifcation
messages's source address as destination
address to reclaim lock. ?
If not , doing this may help clients to
recover locks faster as mon_id which is
generally virtual ip may come up later
but notification messages's source address
will definitely be up most of the time.
thanks,
--- kiran
__________________________________
Do you Yahoo!?
The all-new My Yahoo! - Get yours free!
http://my.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
thanks Trond.
What i could get from this statement is
that source address and mon_id in notification
message cannot be guaranteed to belong to same
machine.
But two different machines can have same
mon_id(nfs never pings mon_id , mon_ids can be faked)
but will have different source address.so doesn't
source address of notification message uniquely
isentify nfs server rather than mon_id and
hence safe to reclaim locks.
--thanks
kiran
--- Trond Myklebust <[email protected]>
wrote:
> ty den 25.01.2005 Klokka 01:16 (-0800) skreiv mehta
> kiran:
> > Hi ,
> > When i was checking lockd recovery ,
> > i noted that clients after getting
> > notification messages , use mon_id
> > as destination address and not notication
> > messages's source address as destination
> > address.(as just a reply)
> >
> > Is there any issue in using notifcation
> > messages's source address as destination
> > address to reclaim lock. ?
>
> If you have a multi-homed server, it does not follow
> that the source
> address used by rpc.statd hosts the same NFS server
> as the mon_name
> address.
>
> Cheers,
> Trond
> --
> Trond Myklebust <[email protected]>
>
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
I got your point.
Please ignore my previous mail.
thanks ,
--kiran
thanks,
kiran
--- Trond Myklebust <[email protected]>
wrote:
> ty den 25.01.2005 Klokka 01:16 (-0800) skreiv mehta
> kiran:
> > Hi ,
> > When i was checking lockd recovery ,
> > i noted that clients after getting
> > notification messages , use mon_id
> > as destination address and not notication
> > messages's source address as destination
> > address.(as just a reply)
> >
> > Is there any issue in using notifcation
> > messages's source address as destination
> > address to reclaim lock. ?
>
> If you have a multi-homed server, it does not follow
> that the source
> address used by rpc.statd hosts the same NFS server
> as the mon_name
> address.
>
> Cheers,
> Trond
> --
> Trond Myklebust <[email protected]>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
On Tue, 25 Jan 2005, Trond Myklebust wrote:
> ty den 25.01.2005 Klokka 01:16 (-0800) skreiv mehta kiran:
>> Hi ,
>> When i was checking lockd recovery ,
>> i noted that clients after getting
>> notification messages , use mon_id
>> as destination address and not notication
>> messages's source address as destination
>> address.(as just a reply)
>>
>> Is there any issue in using notifcation
>> messages's source address as destination
>> address to reclaim lock. ?
>
> If you have a multi-homed server, it does not follow that the source
> address used by rpc.statd hosts the same NFS server as the mon_name
> address.
>
> Cheers,
> Trond
> --
> Trond Myklebust <[email protected]>
we are still experiencing lockd recovery failure on our multi-homed
client/servers - even with no firewall in place. this thread makes me wonder,
is anything special required to make nfs work on a multi-homed setup?
cheers.
-a
--
===============================================================================
| EMAIL :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
| PHONE :: 303.497.6469
| When you do something, you should burn yourself completely, like a good
| bonfire, leaving no trace of yourself. --Shunryu Suzuki
===============================================================================
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
ty den 25.01.2005 Klokka 01:16 (-0800) skreiv mehta kiran:
> Hi ,
> When i was checking lockd recovery ,
> i noted that clients after getting
> notification messages , use mon_id
> as destination address and not notication
> messages's source address as destination
> address.(as just a reply)
>
> Is there any issue in using notifcation
> messages's source address as destination
> address to reclaim lock. ?
If you have a multi-homed server, it does not follow that the source
address used by rpc.statd hosts the same NFS server as the mon_name
address.
Cheers,
Trond
--
Trond Myklebust <[email protected]>
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
thanks Trond.
What i could get from this statement is
that source address and mon_id in notification
message cannot be guaranteed to belong to same
machine.
But two different machines can have same
mon_id(nfs never pings mon_id , mon_ids can be faked)
but will have different source address.so doesn't
source address of notification message uniquely
isentify nfs server rather than mon_id and
hence safe to reclaim locks.
--thanks
kiran
--- Trond Myklebust <[email protected]>
wrote:
> ty den 25.01.2005 Klokka 01:16 (-0800) skreiv mehta
> kiran:
> > Hi ,
> > When i was checking lockd recovery ,
> > i noted that clients after getting
> > notification messages , use mon_id
> > as destination address and not notication
> > messages's source address as destination
> > address.(as just a reply)
> >
> > Is there any issue in using notifcation
> > messages's source address as destination
> > address to reclaim lock. ?
>
> If you have a multi-homed server, it does not follow
> that the source
> address used by rpc.statd hosts the same NFS server
> as the mon_name
> address.
>
> Cheers,
> Trond
> --
> Trond Myklebust <[email protected]>
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs
ty den 25.01.2005 Klokka 22:26 (-0800) skreiv Trond Myklebust:
> > Is there any issue in using notifcation
> > messages's source address as destination
> > address to reclaim lock. ?
>
> If you have a multi-homed server, it does not follow that the source
> address used by rpc.statd hosts the same NFS server as the mon_name
> address.
The other common issue is that the two addresses may have different
firewalling rules.
Cheers,
Trond
--
Trond Myklebust <[email protected]>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist - [email protected]
https://lists.sourceforge.net/lists/listinfo/nfs