From: Aleksander W. <ale...@mo...> - 2016-01-15 11:29:09
|
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 <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 -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 > 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 > |