| To: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] enable inode64 by default when possible |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Wed, 10 Feb 2010 14:15:21 -0600 |
| Cc: | xfs@xxxxxxxxxxx |
| In-reply-to: | <20100210210448.36f16aba@xxxxxxxxxxxxxx> |
| References: | <4B7309D7.5090800@xxxxxxxxxxx> <20100210210448.36f16aba@xxxxxxxxxxxxxx> |
| User-agent: | Thunderbird 2.0.0.23 (Macintosh/20090812) |
Emmanuel Florac wrote:
> Le Wed, 10 Feb 2010 13:32:39 -0600 vous écriviez:
>
>> As such, this patch changes the default to inode64 whenever
>> XFS_BIG_INUMS is set, which in turn depends on either
>> CONFIG_LBDAF or 64-bit longs.
>
> But doesn't it cause problems specially for NFS sharing ?
>
For some clients, yes - as do other NFS servers.
That's what noinode64 is for...
Also, newer nfs clients have an option:
nfs.enable_ino64=
[NFS] enable 64-bit inode numbers.
If zero, the NFS client will fake up a 32-bit inode
number for the readdir() and stat() syscalls instead
of returning the full 64-bit number.
The default is to return 64-bit inode numbers.
(see Documentation/kernel-parameters.txt)
At some point we have to drag people kicking and screaming
out of 1988, I think! :)
(I am mindful that this may manifest itself as "xfs is incompatible"
but if we document this and advertise it a bit, I hope we can avoid
that. At some point, apps just need to be fixed.)
-Eric
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [RFC PATCH 2/2] xfs_export_operations.commit_metadata, bpm |
|---|---|
| Next by Date: | Re: [PATCH] enable inode64 by default when possible, Emmanuel Florac |
| Previous by Thread: | Re: [PATCH] enable inode64 by default when possible, Emmanuel Florac |
| Next by Thread: | Re: [PATCH] enable inode64 by default when possible, Emmanuel Florac |
| Indexes: | [Date] [Thread] [Top] [All Lists] |