Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

2006-10-06 Thread Paul Eggert
Miklos Szeredi <[EMAIL PROTECTED]> writes: > The legacy app will break regardless of how many files there are on > the filesystem, or even wheter it needs to use the inode number or > not. It will break because the stat() family of syscalls will return > with an error. I don't see why. The kern

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

2006-10-06 Thread Miklos Szeredi
> >> If it's for legacy apps, tell people to recompile with largefile > >> support. > > > > Paul, please! It is ridiculous to require end users to recompile > > their applications or kernels or anything. > > A small-file legacy app, one that cannot handle files larger than 2 > GiB, is already qui

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

2006-10-06 Thread Paul Eggert
Miklos Szeredi <[EMAIL PROTECTED]> writes: >> If it's for legacy apps, tell people to recompile with largefile >> support. > > Paul, please! It is ridiculous to require end users to recompile > their applications or kernels or anything. A small-file legacy app, one that cannot handle files large

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

2006-10-06 Thread Miklos Szeredi
> >> If files are identified by the path, then you can hash the > >> path. If you use a good 64-bit hash the chance of collision > >> is practically zero. That's good enough. > > > > Yes. And this solution is actually practical on pure 64bit > > archs only. On 32bit and dual archs it's not practi

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

2006-10-06 Thread Paul Eggert
Miklos Szeredi <[EMAIL PROTECTED]> writes: >> If files are identified by the path, then you can hash the >> path. If you use a good 64-bit hash the chance of collision >> is practically zero. That's good enough. > > Yes. And this solution is actually practical on pure 64bit > archs only. On 32bi

Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

2006-10-06 Thread James Youngman
On 10/6/06, Miklos Szeredi <[EMAIL PROTECTED]> wrote: Yes. And this solution is actually practical on pure 64bit archs only. On 32bit and dual archs it's not practial, because legacy apps (those compiled without largefile support) will get an EOVERFLOW for stat if the inode number doesn't fit

[bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers

2006-10-06 Thread Miklos Szeredi
Follow-up Comment #12, bug #17877 (project findutils): > If files are identified by the path, then you can hash the > path. If you use a good 64-bit hash the chance of collision > is practically zero. That's good enough. Yes. And this solution is actually practical on pure 64bit archs only. On