Re: [MooseFS-Users] Failures with "git svn"

[Piotr R. K. <pio...@mo...>]

Dear Steven,

we forgot to let you know, that the problem is resolved since MooseFS 2.0.84:


* MooseFS 2.0.84-1 (2016-01-19)

  - (mount) fixed setting file length in write module during truncate (fixes "git svn" case)


Best regards, 

--

  <https://moosefs.com/>
Piotr Robert Konopelko
MooseFS Technical Support Engineer
e-mail : pio...@mo... <mailto:pio...@mo...>
www : https://moosefs.com <https://moosefs.com/>
   <https://twitter.com/MooseFS>    <https://www.facebook.com/moosefs>    <https://www.linkedin.com/company/moosefs>   <https://github.com/moosefs>

This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received it by mistake, please let us know by e-mail reply and delete it from your system; you may not copy this message or disclose its contents to anyone. Finally, the recipient should check this email and any attachments for the presence of viruses. Core Technology accepts no liability for any damage caused by any virus transmitted by this email.


> On 15 Jan 2016, at 2:57 PM, Wilson, Steven M <st...@pu...> wrote:
> 
> Thanks, Aleksander.  I'm glad to hear that you were able to duplicate the problem and are working to fix it.
> 
> Best regards,
> Steve
> 
> On Fri, 2016-01-15 at 12:29 +0100, Aleksander Wieliczko wrote:
>> Hi,
>> 
>> First of all we would like to thanks for reporting this issue.
>> We can confirm that problem appears in mfsmount 2.0.72 and even in the latest release 2.0.83.
>> Problem not occurred in MooseFS mount 3.0.69.
>> 
>> Right now we are working to solve this problem.
>> We will inform you about progress of our work.
>> 
>> Best regards
>> Aleksander Wieliczko
>> Technical Support Engineer
>> MooseFS.com <x-msg://18/moosefs.com>
>> 
>> 
>> On 01/14/2016 11:37 PM, Wilson, Steven M wrote:
>> 
>>> Hi,
>>> 
>>> When I attempt to fetch an SVN repository using the "git svn fetch" command, it always fails when writing to a MooseFS volume.  At some point during the process I get a "checksum mismatch" error like the following:
>>>     Checksum mismatch: testmails/positive/348
>>>     expected: 42723d0ae0353368e9adb648da2eb6bc
>>>             got: 637d201f8f22d9d71ba12bf7f39f14c8
>>> 
>>> I've tried this on two different MooseFS volumes from different servers (running MooseFS v. 2.0.72) with the same results.  If I fetch to a local disk formatted in XFS, though, I don't get a checksum error.  These are the commands that initially demonstrated the problem for me:
>>>     git svn init http://emg.nysbc.org/svn/myami <http://emg.nysbc.org/svn/myami> -s
>>>     git svn fetch
>>> 
>>> But I've since tested it with Spamassassin and had the same results:
>>>     git svn init --prefix=origin/ -s https://svn.apache.org/repos/asf/spamassassin <https://svn.apache.org/repos/asf/spamassassin>
>>>     git svn fetch
>>> 
>>> Could someone try this out on their own MooseFS installation to see if it also gives checksum errors?  Is this a known bug?
>>> 
>>> Thanks!
>>> 
>>> Steve 
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140_________________________________________
> moosefs-users mailing list
> moo...@li...
> https://lists.sourceforge.net/lists/listinfo/moosefs-users