Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 10 Jul 2003 13:35:37 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: cygwin-1.5.0-1: Problem stat-ing big file Message-ID: <20030710113537.GV12368@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <3F0D4D6A DOT 30601 AT t-online DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F0D4D6A.30601@t-online.de> User-Agent: Mutt/1.4.1i On Thu, Jul 10, 2003 at 01:26:34PM +0200, Markus Sch?nhaber wrote: > While trying if the new support for files larger than 2GB works, I > created a file with a size of 4.53 GB (4,869,120,000 Bytes) using a > simple write in python. No problems here. But when stat-ing the file > with python's os.stat or by calling stat from C as done in the little > program below, the size of the file gets reported as 574,152,704 Bytes. The changes to 64 bit file access are not propagated automatically to existing applications. E.g. the current `ls' from the fileutils package is compiled with the old (small) stat structure which only has 32 bit off_t for the file size. If you want to actually use the new struct stat and off_t with 64 bit, you have to recompile the application. Sorry, but there's no way around that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/