On Wednesday, December 12, 2001, at 09:52 AM, Chris Bednar wrote: On Tue, 11 Dec 2001, Umesh Vaishampayan wrote: ... Now that VM supports 64 bit data paths, the code above can be removed. But will it work... well, I went through this with Linux; maybe I'll try it again. Yes it will. The VM paths are well tested using HFS+. And UFS paths are tested in Rhapsody^W Mac OS X Server 1.0 and in early xnu. So I have reason to believe that "it should just work". It looks like something nasty may have crept into the code along the way. I attempted a patch, and the good news is that I seem (in at least the cases I've tried) to get the 'File too large' error now, but that is also the bad news. What does your patch look like? Well, it's bad news if it's coming from something like if (lbn < 0) return (EFBIG); You get this error when you do truncate(), right? at bsd/ufs/ffs/ffs_balloc.c:114, but maybe not so bad if it's coming from something like if (length > fs->fs_maxfilesize) return (EFBIG); in bsd/ufs/ffs/ffs_inode.c:209, if all that means is that the maxfilesize in the superblock is 4GB. I'll have to play with dumpfs later (I wonder why that doesn't work on a mounted FS?) Supply the characher device corresponding to your mounted file system to make it happy... Just a side note - I should have known Apple would deliver a system wherein it's EASY to build and install a kernel ;) You are welcome :-D :-D --Umesh -- Umesh Vaishampayan Apple Computer, Inc. Mac OS X Kernel Ph: (408) 974 0229