[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: fsfs migration failure. File too large??

From: Georg Viehöver <viehoever_at_sigma-c.de>
Date: 2005-05-31 21:39:58 CEST

From what I read in the thread (and I have no idea which version of APR I am using since I am using precompiled binaries, and svn --version does not tell me), I would expect fsfs to have problems with commits that are larger than 2 GB. And this probably also depends on both the server and the svn client. While this is not very likely to happen during every day operation, it most certainly will happen when importing large projects from some other version control system. And how about all those other components that are involved access methods different from svn://?

If this is a real problem, I would suggest a warning in the release notes.


-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Tuesday, May 31, 2005 7:38 PM
To: Georg Viehöver
Cc: Holger Rauch; users@subversion.tigris.org
Subject: Re: fsfs migration failure. File too large??

On May 31, 2005, at 12:31 PM, Georg Viehöver wrote:

> I wonder if the SVN dev team ever checked that SVN is able to handle
> files larger than 2 GB or 4 GB. I know quite a number of programs
> (e.g. several ftp implementations) that fail because they use 32 bit
> position counters, even if the file system can handle larger files.

It's not Subversion that handles files, but APR. In particular, APR
0.9x uses a 32-bit position counter, and APR 1.X uses 64-bit ones.

See this thread:


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 31 21:44:00 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.