Thanks for suggestions,
I don't think there's any internal debugging that helps at this
point. Usually errors pointing to corruption are caused by a chain of
syscalls failing in some way, and the final error shows only the last
one, so strace() output is very interesting.
Right - a problem
Kenneth Ölwing kenn...@olwing.se writes:
On 2013-04-05 15:42, Thomas Rast wrote:
Can you run the same tests under strace or similar, and gather the
relevant outputs? Otherwise it's probably very hard to say what is
going wrong. In particular we've had some reports on lustre that
boiled down
-Original Message-
From: Thomas Rast
Sent: Saturday, April 06, 2013 4:12
Kenneth Ölwing kenn...@olwing.se writes:
On 2013-04-05 15:42, Thomas Rast wrote:
Can you run the same tests under strace or similar, and gather the
relevant outputs? Otherwise it's probably very hard to
Hi
Basically, I'm at a place where I'm considering giving up getting this
to work reliably. In general, my setup work really fine, except for the
itty-bitty detail that when I put pressure on things I tend to get into
various kinds of trouble with the central repo being corrupted.
Can
Kenneth Ölwing kenn...@olwing.se writes:
Basically, I'm at a place where I'm considering giving up getting this
to work reliably. In general, my setup work really fine, except for
the itty-bitty detail that when I put pressure on things I tend to get
into various kinds of trouble with the
On 2013-04-05 15:42, Thomas Rast wrote:
Can you run the same tests under strace or similar, and gather the
relevant outputs? Otherwise it's probably very hard to say what is
going wrong. In particular we've had some reports on lustre that
boiled down to impossible returns from libc functions,
Hi,
I'm hoping to hear some wisdom on the subject so I can decide if I'm
chasing a pipe dream or if it should be expected to work and I just need
to work out the kinks.
Finding things like this makes it sound possible:
http://permalink.gmane.org/gmane.comp.version-control.git/122670
but
7 matches
Mail list logo
