Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-22 Thread Christoph Hellwig
On Wed, May 16, 2007 at 09:55:41AM -0500, Steven French wrote: Any ideas what are the minimum export operation(s) that cifs would need to add to export under nfsd? It was not clear to me after reading the Exporting document in Documentation directory. (some users had wanted to export

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread Christoph Hellwig
On Tue, May 15, 2007 at 02:49:14PM -0700, [EMAIL PROTECTED] wrote: fs/cifs/export.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff -puN fs/cifs/export.c~knfsd-exportfs-add-exportfsh-header-fix fs/cifs/export.c --- a/fs/cifs/export.c~knfsd-exportfs-add-exportfsh-header-fix

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread Christoph Hellwig
On Wed, May 16, 2007 at 08:57:21AM +0200, Christoph Hellwig wrote: On Tue, May 15, 2007 at 02:49:14PM -0700, [EMAIL PROTECTED] wrote: fs/cifs/export.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff -puN fs/cifs/export.c~knfsd-exportfs-add-exportfsh-header-fix

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread Steven French
Any ideas what are the minimum export operation(s) that cifs would need to add to export under nfsd? It was not clear to me after reading the Exporting document in Documentation directory. (some users had wanted to export files from Windows servers to nfs clients files by putting an nfs

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread J. Bruce Fields
On Wed, May 16, 2007 at 09:55:41AM -0500, Steven French wrote: Any ideas what are the minimum export operation(s) that cifs would need to add to export under nfsd? It was not clear to me after reading the Exporting document in Documentation directory. (some users had wanted to export

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread Steven French
PROTECTED] Subject Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree On Wed, May 16, 2007 at 09:55:41AM -0500, Steven French wrote: Any ideas what are the minimum export operation(s) that cifs would need to add to export under nfsd? It was not clear to me after

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread J. Bruce Fields
On Wed, May 16, 2007 at 12:03:57PM -0500, Steven French wrote: I thought that until a few days ago, a sequence like the following (two nfs servers exporting the same clustered data) on client 1 lock range A through B of file1 (exported from nfs server 1) on client 2 lock range A through C

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread Neil Brown
On Wednesday May 16, [EMAIL PROTECTED] wrote: Any ideas what are the minimum export operation(s) that cifs would need to add to export under nfsd? It was not clear to me after reading the Exporting document in Documentation directory. You need to be able to map a dentry to a filehandle (you

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread Steven French
If CIFS provides some fix-length identifier for files, then you might be able to do it Most CIFS servers (Windows on NTFS, Samba etc.) can return a unique identifier (a 64 bit inode number), in conjunction with the volume id, that is probably good enough ... right? This can be returned on

Re: + knfsd-exportfs-add-exportfsh-header-fix.patch added to -mm tree

2007-05-16 Thread Neil Brown
On Wednesday May 16, [EMAIL PROTECTED] wrote: If CIFS provides some fix-length identifier for files, then you might be able to do it Most CIFS servers (Windows on NTFS, Samba etc.) can return a unique identifier (a 64 bit inode number), in conjunction with the volume id, that is