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
> -Original Message-
> From: Thomas Rast
> Sent: Saturday, April 06, 2013 4:12
>
> Kenneth Ölwing 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
Kenneth Ölwing 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 to "impos
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,
Kenneth Ölwing 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 central repo bein
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 anyone
6 matches
Mail list logo
