>Eric Schrock wrote: >> ZFS inode numbers are 64 bits. The current implemenation restricts this >> to a 48-bit usable range, but this is not an architectural restriction. >> Future enhancements plan to extend this to the full 64 bits. >> >> 32-bit apps that attempt to stat() a file whose inode number is greater >> than 32 bits will return EOVERFLOW. 64-bit apps and largefile aware >> apps will have no problems. > >So does this mean 32-bit apps that didn't need to be largefile aware in >the past because they only touched small files now need to become largefile >aware to avoid problems with ZFS if they call stat()? (Granted, they've >already had problems with stat() with out-of-range dates from NFS servers >and other places, but those aren't as common as ZFS will be.)
And xfs filesystems exported from SGI systems.... But as said, only when the number of inodes exceeds 75% of 2^32 or 3 billion which for current ufs sizes would be a 24TB filesystem But since the typical filesystem only allocates around 25% of inodes before it fills up, it would be more like a full 100TB before you get to such huge inode numbers, with filesizes staying what they are. Casper _______________________________________________ opensolaris-discuss mailing list [email protected]
