Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <3F0D52E9.5010409@t-online.de>
Date: Thu, 10 Jul 2003 13:50:01 +0200
From: =?ISO-8859-1?Q?Markus_Sch=F6nhaber?= <mks99 AT t-online DOT de>
Reply-To: cygwin AT cygwin DOT com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624
X-Accept-Language: de-de, de, en-us, en
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwin-1.5.0-1: Problem stat-ing big file
References: <3F0D4D6A DOT 30601 AT t-online DOT de> <20030710113537 DOT GV12368 AT cygbert DOT vinschen DOT de>
In-Reply-To: <20030710113537.GV12368@cygbert.vinschen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Corinna Vinschen wrote:

> 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.

Thanks for the quick reply, Corinna.
I was playing around a bit with the new cygwin as this occurred to me 
and I just reported it. Could have come to the conclusion that it has to 
be this way by myself.

In fact this is not bothering me much, since  I - at the moment - have 
no need for being able to create and handle files that large. But it's 
good to know what had to be done if I had the need.

Regards
   mks





--
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/