Re: 64-bit inode number issues

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Oct 07, 2006 at 10:01:32PM +0100, Christoph Hellwig wrote:
> Al commented he doesn't like that.  He also think we should give the
> 64bit inode numbers a try, so I'd say:
> 
>  o add an inode32 option for nfs that mirrors the XFS option
>  o turn it off by default in -mm and see what goes boom

Unfortunately, that technique will not find any problems -- the people 
running systems with 64 bit inode numbers do not overlap with those 
running the -mm tree.  The only real way to get any exercising of the 
relevant code paths would be to fake 64 bit inode numbers in a commonly 
used filesystem like ext3.  The biggest difficultly with LFS has been 
that the API breakage is relatively silent; old applications work fine 
unless they encounter a large file, resulting in many lax applications.

		-ben
-- 
"Time is of no importance, Mr. President, only life is important."
Don't Email: <dont@xxxxxxxxx>.
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux