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

Re: Suggestion: preventing inode crowding with FSFS

From: Ph. Marek <philipp.marek_at_bmlv.gv.at>
Date: 2005-10-10 08:04:06 CEST

On Friday 07 October 2005 21:04, Greg Hudson wrote:
> On Fri, 2005-10-07 at 12:47 -0500, kfogel@collab.net wrote:
> > Greg Hudson <ghudson@MIT.EDU> writes:
> > > The new layout cannot be on by default until 2.0.
> >
> > I'm not advocating that we implement a new layout, but if we do, why
> > would it have to wait till 2.0 to be the default? I thought such a
> > change could happen in a new minor release. From hacking.html:
> Because one of the usage modes of FSFS is to put it in a shared
> filesystem and access it from multiple clients, which might not be in
> version-sync, it's adviseable to avoid backward-incompatible layout
> changes when we can.
> But you're right that it's not a hard requirement.

If such a change is made, I'd like to ask that the transactions are treated

In fsvs I'm checking whole machine installations in at once (eg. 150 000
files), and that results in 300000 files in the transaction-subdirectories
(one for file-data, and another for the properties per file).

Thank you!



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Oct 10 08:04:51 2005

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.