You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Rob Brandt <br...@csd-bes.net> on 2006/09/15 00:35:32 UTC
errors on large commits
I am having exactly the same issue as Markus Fischer a few months ago
where the error message is:
svn: Commit failed (details follow):
svn: MERGE request failed on '/repos/web/project/trunk'
svn:
Cannot modify transaction named '1hv' in filesystem
'/data/subversion/repos/db'
See:
http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=47260
However his solution is not helping me. I tried both the --charset on
SVN::Notify and using a fresh checkout. The repository is exhibiting
the same symptoms; the commit is actually successful at the server end,
but my own working copy doesn't know that. My workaround is to revert
after the commit, delete the new files (at the moment I'm just trying to
load source files into a new repository) and update. That's not a long
term solution :(
My own personal observation is that the commit only fails on large
commits. Not once has it failed when the commit is less than 100k. So
far, I haven't seen success above 100k, but most of the one above 100k
are much larger than 100k, so I'm not sure where the dividing line is.
This does appear to be an SVN::Notify issue, as I disabled that in the
post_commit hook and it doesn't choke.
Ideas?
Rob
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/15/06, Rob Brandt <br...@csd-bes.net> wrote:
> Well, hmmm...
>
> I tried 2 tests with php disabled. A 1mb commit succeeded, and a 2.5mb
> commit failed. So either it improved things but didn't fully correct
> the issue, or my conclusions about always failing over 100k was wrong.
Is it the same error message? Can you include the exact error, and
also the Apache error logs?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by Rob Brandt <br...@csd-bes.net>.
Well, hmmm...
I tried 2 tests with php disabled. A 1mb commit succeeded, and a 2.5mb
commit failed. So either it improved things but didn't fully correct
the issue, or my conclusions about always failing over 100k was wrong.
Rob
Garrett Rooney wrote:
> On 9/15/06, Rob Brandt <br...@csd-bes.net> wrote:
>> Yes, as a matter of fact I am.
>
> Could you possibly turn it off and see if the problem goes away?
>
> We've had a number of reports of weird errors like this that all
> basically get tracked back to PHP changing some sort of global state
> (like the umask, or signal handlers, or other things like that) and
> then not setting it back, or if you're using a multithreaded MPM even
> setting it then setting it back, but just at the wrong time... It's
> quite possible that PHP is causing your issue.
>
> -garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/15/06, Rob Brandt <br...@csd-bes.net> wrote:
> Yes, as a matter of fact I am.
Could you possibly turn it off and see if the problem goes away?
We've had a number of reports of weird errors like this that all
basically get tracked back to PHP changing some sort of global state
(like the umask, or signal handlers, or other things like that) and
then not setting it back, or if you're using a multithreaded MPM even
setting it then setting it back, but just at the wrong time... It's
quite possible that PHP is causing your issue.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by Rob Brandt <br...@csd-bes.net>.
Yes, as a matter of fact I am.
Rob
Garrett Rooney wrote:
> On 9/14/06, Rob Brandt <br...@csd-bes.net> wrote:
>> I am having exactly the same issue as Markus Fischer a few months ago
>> where the error message is:
>>
>> svn: Commit failed (details follow):
>> svn: MERGE request failed on '/repos/web/project/trunk'
>> svn:
>> Cannot modify transaction named '1hv' in filesystem
>> '/data/subversion/repos/db'
>>
>> See:
>> http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=47260
>>
>> However his solution is not helping me. I tried both the --charset on
>> SVN::Notify and using a fresh checkout. The repository is exhibiting
>> the same symptoms; the commit is actually successful at the server end,
>> but my own working copy doesn't know that. My workaround is to revert
>> after the commit, delete the new files (at the moment I'm just trying to
>> load source files into a new repository) and update. That's not a long
>> term solution :(
>>
>> My own personal observation is that the commit only fails on large
>> commits. Not once has it failed when the commit is less than 100k. So
>> far, I haven't seen success above 100k, but most of the one above 100k
>> are much larger than 100k, so I'm not sure where the dividing line is.
>> This does appear to be an SVN::Notify issue, as I disabled that in the
>> post_commit hook and it doesn't choke.
>>
>> Ideas?
>
> Do you happen to be running mod_php on the same server?
>
> -garrett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by John Waycott <ja...@cox.net>.
Bronto wrote:
> Are you using SVN::Notify as well?
>
> John Waycott wrote:
>>>
>> One of our users got this message about two weeks ago. I ran svnadmin
>> verify and found a corrupted revision. This doesn't make sense, but
>> fsfsverify fixed the problem. I don't see how that error could be
>> caused by that, but the user could commit afterwards. She was
>> committing a very large 7MB file. Maybe this was just coincidence?
>>
>> We've hit the fsfs corruption bug five times in the last two months,
>> so it is fairly frequent. The error indication in other cases was the
>> "read length line" error.
>>
>> -- John
No, we use WebSVN to display just the repository list, then ViewCVS for
the repository browsing. We use SvnReporter for email notifications.
We do mix protocols, using http and svn. Most people are using http, but
sometimes we have to use svn to prevent timeouts.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by Bronto <br...@csd-bes.net>.
Are you using SVN::Notify as well?
John Waycott wrote:
> Garrett Rooney wrote:
>> On 9/14/06, Rob Brandt <br...@csd-bes.net> wrote:
>>> I am having exactly the same issue as Markus Fischer a few months ago
>>> where the error message is:
>>>
>>> svn: Commit failed (details follow):
>>> svn: MERGE request failed on '/repos/web/project/trunk'
>>> svn:
>>> Cannot modify transaction named '1hv' in filesystem
>>> '/data/subversion/repos/db'
>>>
>>> See:
>>> http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=47260
>>>
>>> However his solution is not helping me. I tried both the --charset on
>>> SVN::Notify and using a fresh checkout. The repository is exhibiting
>>> the same symptoms; the commit is actually successful at the server end,
>>> but my own working copy doesn't know that. My workaround is to revert
>>> after the commit, delete the new files (at the moment I'm just trying to
>>> load source files into a new repository) and update. That's not a long
>>> term solution :(
>>>
>>> My own personal observation is that the commit only fails on large
>>> commits. Not once has it failed when the commit is less than 100k. So
>>> far, I haven't seen success above 100k, but most of the one above 100k
>>> are much larger than 100k, so I'm not sure where the dividing line is.
>>> This does appear to be an SVN::Notify issue, as I disabled that in the
>>> post_commit hook and it doesn't choke.
>>>
>>> Ideas?
>>
>> Do you happen to be running mod_php on the same server?
>>
>> -garrett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>> For additional commands, e-mail: users-help@subversion.tigris.org
>>
>>
> One of our users got this message about two weeks ago. I ran svnadmin
> verify and found a corrupted revision. This doesn't make sense, but
> fsfsverify fixed the problem. I don't see how that error could be caused
> by that, but the user could commit afterwards. She was committing a very
> large 7MB file. Maybe this was just coincidence?
>
> We've hit the fsfs corruption bug five times in the last two months, so
> it is fairly frequent. The error indication in other cases was the "read
> length line" error.
>
> -- John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by John Waycott <ja...@cox.net>.
Garrett Rooney wrote:
> On 9/14/06, Rob Brandt <br...@csd-bes.net> wrote:
>> I am having exactly the same issue as Markus Fischer a few months ago
>> where the error message is:
>>
>> svn: Commit failed (details follow):
>> svn: MERGE request failed on '/repos/web/project/trunk'
>> svn:
>> Cannot modify transaction named '1hv' in filesystem
>> '/data/subversion/repos/db'
>>
>> See:
>> http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=47260
>>
>> However his solution is not helping me. I tried both the --charset on
>> SVN::Notify and using a fresh checkout. The repository is exhibiting
>> the same symptoms; the commit is actually successful at the server end,
>> but my own working copy doesn't know that. My workaround is to revert
>> after the commit, delete the new files (at the moment I'm just trying to
>> load source files into a new repository) and update. That's not a long
>> term solution :(
>>
>> My own personal observation is that the commit only fails on large
>> commits. Not once has it failed when the commit is less than 100k. So
>> far, I haven't seen success above 100k, but most of the one above 100k
>> are much larger than 100k, so I'm not sure where the dividing line is.
>> This does appear to be an SVN::Notify issue, as I disabled that in the
>> post_commit hook and it doesn't choke.
>>
>> Ideas?
>
> Do you happen to be running mod_php on the same server?
>
> -garrett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
One of our users got this message about two weeks ago. I ran svnadmin
verify and found a corrupted revision. This doesn't make sense, but
fsfsverify fixed the problem. I don't see how that error could be caused
by that, but the user could commit afterwards. She was committing a very
large 7MB file. Maybe this was just coincidence?
We've hit the fsfs corruption bug five times in the last two months, so
it is fairly frequent. The error indication in other cases was the "read
length line" error.
-- John
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: errors on large commits
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 9/14/06, Rob Brandt <br...@csd-bes.net> wrote:
> I am having exactly the same issue as Markus Fischer a few months ago
> where the error message is:
>
> svn: Commit failed (details follow):
> svn: MERGE request failed on '/repos/web/project/trunk'
> svn:
> Cannot modify transaction named '1hv' in filesystem
> '/data/subversion/repos/db'
>
> See:
> http://subversion.tigris.org/servlets/ReadMsg?listName=users&msgNo=47260
>
> However his solution is not helping me. I tried both the --charset on
> SVN::Notify and using a fresh checkout. The repository is exhibiting
> the same symptoms; the commit is actually successful at the server end,
> but my own working copy doesn't know that. My workaround is to revert
> after the commit, delete the new files (at the moment I'm just trying to
> load source files into a new repository) and update. That's not a long
> term solution :(
>
> My own personal observation is that the commit only fails on large
> commits. Not once has it failed when the commit is less than 100k. So
> far, I haven't seen success above 100k, but most of the one above 100k
> are much larger than 100k, so I'm not sure where the dividing line is.
> This does appear to be an SVN::Notify issue, as I disabled that in the
> post_commit hook and it doesn't choke.
>
> Ideas?
Do you happen to be running mod_php on the same server?
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org