Date: Thu, 18 Apr 2002 01:20:05 -0700 (PDT) From: Bruce Evans <bde@zeta.org.au> To: freebsd-bugs@FreeBSD.org Subject: Re: misc/37161: ext2 linux file system, error handling large files Message-ID: <200204180820.g3I8K5f21966@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/37161; it has been noted by GNATS. From: Bruce Evans <bde@zeta.org.au> To: Ariel Florio <arielflorio@ciudad.com.ar> Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: misc/37161: ext2 linux file system, error handling large files Date: Thu, 18 Apr 2002 18:20:30 +1000 (EST) On Tue, 16 Apr 2002, Ariel Florio wrote: > >Description: > I've got a ext2 file system with a 30Gb tar file, I need untar this file but the system cut the operation in the first 2,9Gb aprox. > The tar file is being untared on FBSD File System on JBOD Mylex DAC960. > I tried to copy the tar file ( cp ) and the same problem is obtained, the operation cuts in the 10% aprox. I have planned to fix this for years but haven't done anything. read()s on ext2fs filesystems don't work for offsets larger than 2G, but the usual maxfilesize check is ifdefed out at the beginning of ext2_read(), so such reads blunder on for longer than they should instead of doing the usual (wrong) error handling very early (read() should return EOF, not EFBIG). Similarly in ext2 in ext2_write(), except blundering on may damage the filesystm and the usual error handling is correct. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204180820.g3I8K5f21966>