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

Re: ISSUE: "To many open files" not being logged by master server when sync fails.

From: Kenneth Miles <kmiles_at_voyagergaming.com>
Date: Fri, 04 May 2012 15:21:11 +1000

On 03/05/12 22:07, Philip Martin wrote:
> Ken Miles<kmiles_at_voyagergaming.com> writes:
>
>
>> We are syncing a branch of the repository and have 11068 revisions. I
>> tried excluding some revisions via path based authorization but got
>> the same result. I'm not sure what is required or where to look to
>> replicate in another repository. I have a copy of the repositories to
>> test in gdb and can give you a dump of any state information required
>> to solve issue if you need any more info.
>>
> I assume you know which revision is causing the problem. What does the
> failing revision look like? How many text modifications, property
> modifications, adds, deletes, revision properties? The commands
> "svn log -vqcrNNN URL" and "svn diff -crNNN URL" may help. Is the
> repository packed?
>
> Are you on Linux? Use "ls -l /proc/NNN/fd" where NNN is the process ID
> of the svnserve process to see which files are open. What files are
> they?
>
> If you set a breakpoint on replay_one_revision you should be able to
> determine whether the process is leaking a small number of files for
> each revision or whether the failing revision is simply opening too many
> files.
>
>

I'm not sure if a specific revision is causing the issue. But it always
fails replaying on a certain revision number as seen in the stack trace.

It is definitely opening multiple files more than once. It closes all
file handles once the abort-edit is sent.

Can i check anything else?

-- 
Kenneth Miles
(Software Engineer)
Voyager Gaming Technologies
Ph: +61 7 3482 9124
Mobile: 0407178204
20 Duntroon Street
Brendale Qld 4500
Received on 2012-05-04 07:21:29 CEST

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

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