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

RE: AW: SQLite locking for WCNG on NFS

From: Bert Huijben <bert_at_qqmail.nl>
Date: Wed, 22 Feb 2012 15:01:24 +0100

> -----Original Message-----
> From: Mark Phippard [mailto:markphip_at_gmail.com]
> Sent: woensdag 22 februari 2012 14:53
> To: Philip Martin
> Cc: Branko Čibej; dev_at_subversion.apache.org
> Subject: Re: AW: SQLite locking for WCNG on NFS
>
> On Wed, Feb 22, 2012 at 8:42 AM, Philip Martin
> <philip.martin_at_wandisco.com> wrote:
> > Mark Phippard <markphip_at_gmail.com> writes:
> >
> >> On Wed, Feb 22, 2012 at 4:25 AM, Philip Martin
> >> <philip.martin_at_wandisco.com> wrote:
> >>> The user has more information than the application can ever have.  If
> >>> the user wants to be able to run two subtree updates in parallel then
> >>> exlusive locking must not be enabled.  If the user wants to run status
> >>> during an update then exclusive locking must not be enabled.
> >>
> >> These scenarios are already changes that SQLite brings us.  You cannot
> >> update two subtrees in parallel today.  You cannot run status while an
> >> update or commit is running.  As noted in another thread this week,
> >> you cannot even run svn log when one of these processes is running.
> >
> > That's not correct.  Start and hold an update:
> >
> > $ gdb -arg subversion/svn/.libs/lt-svn up wc/A/B/C
> > (gdb) b update_editor.c:close_directory
> > (gdb) r
> > Breakpoint 2 at 0x7ffff78eee2f
> >
> > Run status:
> >
> > $ svn st wc
> >  L     wc/A/B
> > ! L     wc/A/B/C
> > ! L     wc/A/B/C/D
>
> When I do this on my OSX system, I see the the L status for every
> folder in my WC. That might technically mean the command is working,
> but it is not what I want to see.
>
> I will note that svn log worked fine for me. So I wonder why it did
> not for this user:
>
> http://mail-archives.apache.org/mod_mbox/subversion-
> users/201202.mbox/%3C135b01cceead%24cd1d1590%24675740b0%24%40w
> ebkr.de%3E
>
> Could it work differently on Windows?

Note that update operates on 'wc/A/B/C', but the lock is on 'wc/A/B'. If
something changes the list of children we lock one level higher than the
target.

I can confirm the behavior that Philip described. (I don't think there are
platform differences)

        Bert
Received on 2012-02-22 15:01:57 CET

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