Date: 12 Aug 1999 11:49:13 +0300 From: Ville-Pertti Keinonen <will@iki.fi> To: Matthew.Alton@anheuser-busch.com (Alton, Matthew) Cc: hackers@freebsd.org Subject: Re: BSD-XFS Update Message-ID: <86btcdmliu.fsf@not.demophon.com> In-Reply-To: Matthew.Alton@anheuser-busch.com's message of "12 Aug 1999 00:49:21 %2B0300" References: <0740CBD1D149D31193EB0008C7C56836EB8B05@STLABCEXG012>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew.Alton@anheuser-busch.com (Alton, Matthew) writes: > I am currently researching methods for implementing the 64-bit > syscalls stat64(), fstat64(), lseek64() &etc. delineated in the > SGI design doc _64 Bit File Access_ by Adam Sweeney. Do the design docs indicate how inode numbers should interact with userland APIs? IIRC, inode numbers are 64-bit numbers in XFS. Since ino_t, st_ino of struct stat and d_fileno of struct dirent are only 32 bits, inode numbers may be truncated and not appear unique to userland. This would break the assumptions of some code (e.g. getcwd(3), when not using the kernel extension). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86btcdmliu.fsf>