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

Re: Linux svn clients > 1.7 have issues operating on WC which physically lives on Windows shares

From: Les Mikesell <lesmikesell_at_gmail.com>
Date: Wed, 4 Dec 2013 16:25:46 -0600

On Wed, Dec 4, 2013 at 4:05 PM, Ben Reser <ben_at_reser.org> wrote:
> On 12/4/13 12:59 PM, Adam Daughterson wrote:
>> Prior to upgrading to WanDisco svn client 1.7.x I was able to operate on
>> working copies which physically live on Windows shares. After the upgrade, I
>> get the following error when trying to do a fresh checkout:
>>
>> me@here:tmp$ svn co http://myThing/trunk myThing
>> *svn: E200030: sqlite[S22]: large file support is disabled*
>>
>> I've verified that I can perform this same operation on a Linux samba share
>> with the new clients, and nothing has changed on the Windows side of things.
>>
>> Anyone have any idea as to WTH this is all about?
>
> Subversion 1.7 moved from having .svn directories in each directory and flat
> file entries files to maintain the state of the working copy to using a single
> .svn directory at the root of the working copy and a sqlite database.
>
> The error you're getting is because the working copy database file
> (myThing/.svn/wc.db in your case) is larger than 2GB. Your Windows server may
> not support files over 2GB.

Or if the filesystem is on VFAT, you might be hitting the the 4GB file
size limit.
>
> All that said, if you have that large of a working copy database, I doubt
> you're going to have very good performance using the working copy over a
> network share.

Not to mention what happens if you have linux filenames that differ
only in case.

-- 
   Les Mikesell
     lesmikesell_at_gmail.com
Received on 2013-12-04 23:26:18 CET

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.