Thread: RE: [SSI-devel] Re: CFS and NFS
Brought to you by:
brucewalker,
rogertsang
From: Walker, B. J (HP-Labs) <bru...@hp...> - 2005-12-23 15:49:26
|
File record locking is better in CFS and allows processes to move while holding locks (not possible with NFS). =20 Coherency is not just w.r.t. file data but also w.r.t. creates and deleted (file directory operations). =20 -----Original Message----- From: ssi...@li... [mailto:ssi...@li...] On Behalf Of Watson, Brian J. (HP-Labs) Sent: Friday, December 23, 2005 7:01 AM To: Roger Tsang Cc: John Hughes; ssic-linux-devel Subject: [SSI-devel] Re: CFS and NFS In fact, almost all of CFS was derived from NFS. CFS is really just a copy of NFS with the following changes: - tight coherency (all clients immediately see changes made by any client), - client-at-server access (the filesystem server node can also be a client, with the same coherency), - and HA failover of the filesystem server node. I don't think there's anything more to CFS than that. If there was a version of NFS that had these three features, then it could replace CFS. Brian Roger Tsang wrote: > What Brian meant was that particular part of CFS code is based on NFS=20 > in 2.4. Since it works for you I think I'll check-in these changes. > :) >=20 > Roger >=20 >=20 > On 12/15/05, John Hughes <jo...@ca...> wrote: >=20 >>Roger Tsang wrote: >> >> >>>John, >>> >>>It looks encode_fh was skipped at the very beginning during the=20 >>>initial checkin against vanilla kernel 2.6.8.1 in October 2004, but=20 >>>they exist in SSI-1.2. So if you don't seem to be having a problem=20 >>>after some testing I'll re-enable these cfs_export_ops in CVS. It=20 >>>might resolve bug 1201723 which was filed in May 2005. We might have >>>missed the fact that these export ops were skipped. >>> >>>Anyone against this change? >>> >>> >> >>Well, putting the cfs_export_ops back in fixes my bug, but I don't use >>NFS so I don't know if it screws up NFS. >> >> >=20 >=20 >=20 > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that=20 > makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel >=20 >=20 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick _______________________________________________ ssic-linux-devel mailing list ssi...@li... https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel |
From: Walker, B. J (HP-Labs) <bru...@hp...> - 2005-12-23 17:19:46
|
Yes; but so does NFS. Problem is that NFS locking wants to know the host and when we migrate from one node to another, we can't update that (at a remote NFS server) so when we go to do the unlock, the server is quite confused (different host doing the unlock). We could make all locks look like they came from CVIP but then we have lots of failure problems. Bruce =20 -----Original Message----- From: Roger Tsang [mailto:rog...@gm...]=20 Sent: Friday, December 23, 2005 9:05 AM To: Watson, Brian J. (HP-Labs) Cc: Walker, Bruce J (HP-Labs); John Hughes; ssic-linux-devel Subject: Re: [SSI-devel] Re: CFS and NFS Looks like this is possible because CFS locks use cluster-wide pid's. Roger On 12/23/05, Brian J. Watson <Bri...@hp...> wrote: > I didn't know about the file record locking improvements. Sorry about that. > > Brian > > > Walker, Bruce J (HP-Labs) wrote: > > File record locking is better in CFS and allows processes to move=20 > > while holding locks (not possible with NFS). > > > > Coherency is not just w.r.t. file data but also w.r.t. creates and=20 > > deleted (file directory operations). > > > > > > -----Original Message----- > > From: ssi...@li... > > [mailto:ssi...@li...] On Behalf Of=20 > > Watson, Brian J. (HP-Labs) > > Sent: Friday, December 23, 2005 7:01 AM > > To: Roger Tsang > > Cc: John Hughes; ssic-linux-devel > > Subject: [SSI-devel] Re: CFS and NFS > > > > In fact, almost all of CFS was derived from NFS. CFS is really just=20 > > a copy of NFS with the following changes: > > > > - tight coherency (all clients immediately see changes made by any=20 > > client), > > > > - client-at-server access (the filesystem server node can also be a=20 > > client, with the same coherency), > > > > - and HA failover of the filesystem server node. > > > > I don't think there's anything more to CFS than that. If there was a > > version of NFS that had these three features, then it could replace CFS. > > > > Brian > > > > > > Roger Tsang wrote: > > > >>What Brian meant was that particular part of CFS code is based on=20 > >>NFS in 2.4. Since it works for you I think I'll check-in these changes. > >>:) > >> > >>Roger > >> > >> > >>On 12/15/05, John Hughes <jo...@ca...> wrote: > >> > >> > >>>Roger Tsang wrote: > >>> > >>> > >>> > >>>>John, > >>>> > >>>>It looks encode_fh was skipped at the very beginning during the=20 > >>>>initial checkin against vanilla kernel 2.6.8.1 in October 2004,=20 > >>>>but they exist in SSI-1.2. So if you don't seem to be having a=20 > >>>>problem after some testing I'll re-enable these cfs_export_ops in=20 > >>>>CVS. It might resolve bug 1201723 which was filed in May 2005. =20 > >>>>We might have > > > > > >>>>missed the fact that these export ops were skipped. > >>>> > >>>>Anyone against this change? > >>>> > >>>> > >>> > >>>Well, putting the cfs_export_ops back in fixes my bug, but I don't=20 > >>>use > > > > > >>>NFS so I don't know if it screws up NFS. > >>> > >>> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.net email is sponsored by: Splunk Inc. Do you grep through=20 > >>log > > > > > >>files for problems? Stop! Download the new AJAX search engine that > >>makes searching your log files as easy as surfing the web. =20 > >>DOWNLOAD > > > > SPLUNK! > > > >>http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > >>_______________________________________________ > >>ssic-linux-devel mailing list > >>ssi...@li... > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > >> > >> > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through=20 > > log files for problems? Stop! Download the new AJAX search engine=20 > > that makes searching your log files as easy as surfing the web. =20 > > DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > > _______________________________________________ > > ssic-linux-devel mailing list > > ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > > > > > > |
From: Roger T. <rog...@gm...> - 2005-12-23 17:47:49
|
Right that's because MAC address to CVIP (at the NFS server) is the LVS director node only. Roger On 12/23/05, Walker, Bruce J (HP-Labs) <bru...@hp...> wrote: > Yes; but so does NFS. Problem is that NFS locking wants to know the > host and when we migrate from one node to another, we can't update that > (at a remote NFS server) so when we go to do the unlock, the server is > quite confused (different host doing the unlock). We could make all > locks look like they came from CVIP but then we have lots of failure > problems. > > Bruce > > > -----Original Message----- > From: Roger Tsang [mailto:rog...@gm...] > Sent: Friday, December 23, 2005 9:05 AM > To: Watson, Brian J. (HP-Labs) > Cc: Walker, Bruce J (HP-Labs); John Hughes; ssic-linux-devel > Subject: Re: [SSI-devel] Re: CFS and NFS > > Looks like this is possible because CFS locks use cluster-wide pid's. > > Roger > > On 12/23/05, Brian J. Watson <Bri...@hp...> wrote: > > I didn't know about the file record locking improvements. Sorry about > that. > > > > Brian > > > > > > Walker, Bruce J (HP-Labs) wrote: > > > File record locking is better in CFS and allows processes to move > > > while holding locks (not possible with NFS). > > > > > > Coherency is not just w.r.t. file data but also w.r.t. creates and > > > deleted (file directory operations). > > > > > > > > > -----Original Message----- > > > From: ssi...@li... > > > [mailto:ssi...@li...] On Behalf Of > > > Watson, Brian J. (HP-Labs) > > > Sent: Friday, December 23, 2005 7:01 AM > > > To: Roger Tsang > > > Cc: John Hughes; ssic-linux-devel > > > Subject: [SSI-devel] Re: CFS and NFS > > > > > > In fact, almost all of CFS was derived from NFS. CFS is really just > > > a copy of NFS with the following changes: > > > > > > - tight coherency (all clients immediately see changes made by any > > > client), > > > > > > - client-at-server access (the filesystem server node can also be a > > > client, with the same coherency), > > > > > > - and HA failover of the filesystem server node. > > > > > > I don't think there's anything more to CFS than that. If there was a > > > > version of NFS that had these three features, then it could replace > CFS. > > > > > > Brian > > > > > > > > > Roger Tsang wrote: > > > > > >>What Brian meant was that particular part of CFS code is based on > > >>NFS in 2.4. Since it works for you I think I'll check-in these > changes. > > >>:) > > >> > > >>Roger > > >> > > >> > > >>On 12/15/05, John Hughes <jo...@ca...> wrote: > > >> > > >> > > >>>Roger Tsang wrote: > > >>> > > >>> > > >>> > > >>>>John, > > >>>> > > >>>>It looks encode_fh was skipped at the very beginning during the > > >>>>initial checkin against vanilla kernel 2.6.8.1 in October 2004, > > >>>>but they exist in SSI-1.2. So if you don't seem to be having a > > >>>>problem after some testing I'll re-enable these cfs_export_ops in > > >>>>CVS. It might resolve bug 1201723 which was filed in May 2005. > > >>>>We might have > > > > > > > > >>>>missed the fact that these export ops were skipped. > > >>>> > > >>>>Anyone against this change? > > >>>> > > >>>> > > >>> > > >>>Well, putting the cfs_export_ops back in fixes my bug, but I don't > > >>>use > > > > > > > > >>>NFS so I don't know if it screws up NFS. > > >>> > > >>> > > >> > > >> > > >> > > >>------------------------------------------------------- > > >>This SF.net email is sponsored by: Splunk Inc. Do you grep through > > >>log > > > > > > > > >>files for problems? Stop! Download the new AJAX search engine that > > > >>makes searching your log files as easy as surfing the web. > > >>DOWNLOAD > > > > > > SPLUNK! > > > > > >>http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > > >>_______________________________________________ > > >>ssic-linux-devel mailing list > > >>ssi...@li... > > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > > >> > > >> > > > > > > > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: Splunk Inc. Do you grep through > > > log files for problems? Stop! Download the new AJAX search engine > > > that makes searching your log files as easy as surfing the web. > > > DOWNLOAD SPLUNK! > > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > > > _______________________________________________ > > > ssic-linux-devel mailing list > > > ssi...@li... > > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > > > > > > > > > > > |
From: Brian J. W. <Bri...@hp...> - 2005-12-23 16:05:48
|
I didn't know about the file record locking improvements. Sorry about that. Brian Walker, Bruce J (HP-Labs) wrote: > File record locking is better in CFS and allows processes to move while > holding locks (not possible with NFS). > > Coherency is not just w.r.t. file data but also w.r.t. creates and > deleted (file directory operations). > > > -----Original Message----- > From: ssi...@li... > [mailto:ssi...@li...] On Behalf Of > Watson, Brian J. (HP-Labs) > Sent: Friday, December 23, 2005 7:01 AM > To: Roger Tsang > Cc: John Hughes; ssic-linux-devel > Subject: [SSI-devel] Re: CFS and NFS > > In fact, almost all of CFS was derived from NFS. CFS is really just a > copy of NFS with the following changes: > > - tight coherency (all clients immediately see changes made by any > client), > > - client-at-server access (the filesystem server node can also be a > client, with the same coherency), > > - and HA failover of the filesystem server node. > > I don't think there's anything more to CFS than that. If there was a > version of NFS that had these three features, then it could replace CFS. > > Brian > > > Roger Tsang wrote: > >>What Brian meant was that particular part of CFS code is based on NFS >>in 2.4. Since it works for you I think I'll check-in these changes. >>:) >> >>Roger >> >> >>On 12/15/05, John Hughes <jo...@ca...> wrote: >> >> >>>Roger Tsang wrote: >>> >>> >>> >>>>John, >>>> >>>>It looks encode_fh was skipped at the very beginning during the >>>>initial checkin against vanilla kernel 2.6.8.1 in October 2004, but >>>>they exist in SSI-1.2. So if you don't seem to be having a problem >>>>after some testing I'll re-enable these cfs_export_ops in CVS. It >>>>might resolve bug 1201723 which was filed in May 2005. We might have > > >>>>missed the fact that these export ops were skipped. >>>> >>>>Anyone against this change? >>>> >>>> >>> >>>Well, putting the cfs_export_ops back in fixes my bug, but I don't use > > >>>NFS so I don't know if it screws up NFS. >>> >>> >> >> >> >>------------------------------------------------------- >>This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > >>files for problems? Stop! Download the new AJAX search engine that >>makes searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! > >>http://ads.osdn.com/?ad_idv37&alloc_id865&op=click >>_______________________________________________ >>ssic-linux-devel mailing list >>ssi...@li... >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel >> >> > > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that > makes searching your log files as easy as surfing the web. DOWNLOAD > SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > ssic-linux-devel mailing list > ssi...@li... > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > > |
From: Roger T. <rog...@gm...> - 2005-12-23 17:04:33
|
Looks like this is possible because CFS locks use cluster-wide pid's. Roger On 12/23/05, Brian J. Watson <Bri...@hp...> wrote: > I didn't know about the file record locking improvements. Sorry about tha= t. > > Brian > > > Walker, Bruce J (HP-Labs) wrote: > > File record locking is better in CFS and allows processes to move while > > holding locks (not possible with NFS). > > > > Coherency is not just w.r.t. file data but also w.r.t. creates and > > deleted (file directory operations). > > > > > > -----Original Message----- > > From: ssi...@li... > > [mailto:ssi...@li...] On Behalf Of > > Watson, Brian J. (HP-Labs) > > Sent: Friday, December 23, 2005 7:01 AM > > To: Roger Tsang > > Cc: John Hughes; ssic-linux-devel > > Subject: [SSI-devel] Re: CFS and NFS > > > > In fact, almost all of CFS was derived from NFS. CFS is really just a > > copy of NFS with the following changes: > > > > - tight coherency (all clients immediately see changes made by any > > client), > > > > - client-at-server access (the filesystem server node can also be a > > client, with the same coherency), > > > > - and HA failover of the filesystem server node. > > > > I don't think there's anything more to CFS than that. If there was a > > version of NFS that had these three features, then it could replace CFS= . > > > > Brian > > > > > > Roger Tsang wrote: > > > >>What Brian meant was that particular part of CFS code is based on NFS > >>in 2.4. Since it works for you I think I'll check-in these changes. > >>:) > >> > >>Roger > >> > >> > >>On 12/15/05, John Hughes <jo...@ca...> wrote: > >> > >> > >>>Roger Tsang wrote: > >>> > >>> > >>> > >>>>John, > >>>> > >>>>It looks encode_fh was skipped at the very beginning during the > >>>>initial checkin against vanilla kernel 2.6.8.1 in October 2004, but > >>>>they exist in SSI-1.2. So if you don't seem to be having a problem > >>>>after some testing I'll re-enable these cfs_export_ops in CVS. It > >>>>might resolve bug 1201723 which was filed in May 2005. We might have > > > > > >>>>missed the fact that these export ops were skipped. > >>>> > >>>>Anyone against this change? > >>>> > >>>> > >>> > >>>Well, putting the cfs_export_ops back in fixes my bug, but I don't use > > > > > >>>NFS so I don't know if it screws up NFS. > >>> > >>> > >> > >> > >> > >>------------------------------------------------------- > >>This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > > > > >>files for problems? Stop! Download the new AJAX search engine that > >>makes searching your log files as easy as surfing the web. DOWNLOAD > > > > SPLUNK! > > > >>http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > >>_______________________________________________ > >>ssic-linux-devel mailing list > >>ssi...@li... > >>https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > >> > >> > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files for problems? Stop! Download the new AJAX search engine that > > makes searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > > _______________________________________________ > > ssic-linux-devel mailing list > > ssi...@li... > > https://lists.sourceforge.net/lists/listinfo/ssic-linux-devel > > > > > > |