Messages in this thread |  | | Date | Sun, 7 Jan 2001 05:07:18 +1300 | From | Chris Wedgwood <> | Subject | Re: ramfs problem... (unlink of sparse file in "D" state) |
| |
On Sat, Jan 06, 2001 at 03:58:20PM +0000, Alan Cox wrote:
Ext2 handles large files almost properly. (properly on 2.2 + patches) NFSv3 handles large files but might be missing the O_LARGEFILE check. I believe reiserfs went to at least 4Gig.
reiserfs 3.6.x under 2.4.x should go much higher unless i am reading something wrong
<pause>
yup, it does.
as for NFS, I'm not sure how to pass O_LARGEFILE via the protocol and since NFS isn't really POSIX like anyhow decided we might as well just ingore it and have all sys_open calls for NFS look like O_LARGEFILE was specified
move this check and also write/seek check into the VFS would make sense; right now you can
f = open("blah",O_RDWR & ~O_LARGEFILE); lseek(f,1024*1024*1024,SEEK_CUR); lseek(f,1024*1024*1024,SEEK_CUR); lseek(f,1024*1024*1024,SEEK_CUR); write(f,"alan's beard",12); close(f);
and create a file you cannot open again with the same application
--cw - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/
|  |