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

Re: repos not accessible after log files removed (II)

From: John Peacock <jpeacock_at_rowman.com>
Date: 2003-10-01 15:55:31 CEST

Jan Hendrik wrote:
> The server is a P4 1.6GB box, 128 MB RAM, 10/100 LAN, W2K
> Pro SP2, FAT32, no AV, no firewall, Apache 2.0.47 as service (no
> problems since setup about 6-7 weeks ago). SVN was .27 for
> about the same time, problem began about a week ago and
> persisted after dump/load to a new .30 repos.
>
> My machine is a P200, 144 MB RAM, 10 Mbit LAN, W2K Pro
> SP2, FAT32, no AV, Kerio Firewall 2.1.5 with SVN/TSVN allowed
> on any ports with local network mask, Apache running with no
> problems since mid/end July. SVN started with .25, updated to .27,
> now updated together with the above machine to .30.

FAT32 seems to be the common element. Is there some reason you cannot use NTFS
on at least the server? FAT32 is not really not suitable for server processes;
it is fragile and lacking most features of modern (and not so modern) multiuser
file systems.

However, see the second paragraph of item 2 here:

        http://www.sleepycat.com/docs/ref/build_win/notes.html

which certainly sounds like what you are experiencing. Someone more familiar
with how Subversion and BerkeleyDB interact will have to weigh in as to whether
this could be the problem.

My advice is to convert the drive holding the repository files to NTFS and see
if the system remains stable.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 1 15:56:06 2003

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.