[Top][All Lists]

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

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

From: James Youngman
Subject: Re: [bug #17877] Invalid "No such file or directory" error on filesystem without stable inode numbers
Date: Fri, 6 Oct 2006 09:50:27 +0100

On 10/6/06, Miklos Szeredi <address@hidden> 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 in
32 bits.  This is irrespective of whether the app actually
would use st_ino or not.

The problem already exists for NFS.  There are NFS implementations
with 64-bit inodes that either
(a) just don't return names of files whose inode number is >int32_max
(b) Return the inode number modulo int32_max+1.

Some systems (for example IRIX I think) can be switched between the
two behaviours.  See also comments about CIFS at


reply via email to

[Prev in Thread] Current Thread [Next in Thread]