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

Subversion 1.4.3 "Resource Device" error on Windows platform.

From: Jim Barber <jim.barber_at_ddihealth.com>
Date: 2007-05-08 03:52:00 CEST

Well it's been about a week and no response to my issue, so I'm guessing that it's not something that any of you have seen or heard about before.

I've done more monitoring with the SysInternals tools and the windows 'System' process does access the BSB strings file on numerous occasions.
So at least I know that is normal, I just don't know why it sometimes ends up stuck holding a lock on this file for an hour or so.

Is this a question that I should pose to the developers list instead perhaps?


Jim Barber
DDI Health

Hi all.

I have a problem that I have encountered in both Subversion 1.3.2 and now 1.4.3

We have a repository called HcnProducts and occasionally any access to it results in the following error:

     Berkeley DB error for filesystem 'HcnProducts/db' while opening 'strings' table:
     Resource device

All tools including the svnadmin.exe tool get the same 'Resource device' error.

When we were using version 1.3.2 the repository used to be in FSFS format but we seemed to be hitting some sort of race condition where it was trying to delete transaction directories before they were empty.
So at that stage I converted to the Berkeley DB (BDB) format which seemed to resolve that problem (so I never posted about it).
But eventually the above error started occurring, so I upgraded to 1.4.3
This version also has the same problem.

The server is running 'Windows Server 2003 R2 SP1'
Subversion is only accessed via the svnserve.exe service.

When the problem occurs I've been using some tools from SysInternals to look at the situation.
It appears that the top level Windows process called 'System' has a file handle referencing the D:\SvnRepository\HcnProducts\db\strings BDB file.
After what seems like at least an hour or so, this handle finally disappears and then all access to the repository is restored to normal.

I've used Process Monitor from SysInternals to monitor file handles on the strings file under normal operations, and I see references to it from the svnserve.exe service but they only last for less than a second as they are needed.
The 'System' process doesn't seem to reference it under normal operations.
However I am yet to do this monitoring while a build is in progress to see if the 'System' process ever needs to reference the BDB file.

The problem seems to be triggered when our automatic builds happen.
However running an automatic build doesn't guarantee that the problem will occur (ie it's an intermittent problem).
I believe that part of the build process is to create a number of tags marking the build point.
I'm not in charge of the build scripts so I don't know the full details, but if you need more info I'm sure I could sort it out.
I've CC:ed the build script maintainer on this email.

I'm not sure what other information you might need...
Currently the BDB strings file is around 8 GB in size.
Developers are using TortoiseSVN on their PCs for access to the repository.
I'm guessing the build computer uses the tools as supplied by the subversion install.

So does anyone know how I can avoid the 'System' process from grabbing a handle on the strings file that it won't release?
Could it possibly be a bug in how Subversion handles a BDB database on a Windows system?


Jim Barber
DDI Health
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue May 8 03:53:04 2007

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.