On Thu, Feb 14, 2013 at 05:01:10PM -0500, J. Bruce Fields wrote:
> On Thu, Feb 14, 2013 at 05:10:02PM +1100, Dave Chinner wrote:
> > On Wed, Feb 13, 2013 at 05:20:52PM -0500, Theodore Ts'o wrote:
> > > Telldir() and seekdir() are basically implementation horrors for any
&g
e other contains a freespace
index for tracking free space in the data segment.
IOWs persistent, deterministic, low cost telldir/seekdir behaviour
was a problem solved in the 1990s. :)
Cheers,
Dave.
--
Dave Chinner
da...@fromorbit.com
7;s exactly what XFS directory cookies are - a direct encoding of
the dirent offset into the directory file. Which means a overflow
would occur at 16GB of directory data for XFS. That is in the realm
of several hundreds of millions of files in a single directory,
which I have seen done before
he offset into the directory block can have
3 bits compressed out and hence we end up with only 32 bits being
needed to address the entire 32GB directory data segment.
So, there are no collisions or 32/64 bit issues with XFS directory
cookies regardless of the workload.
Cheers,
Dave.
--
Dave
