On Mon, Mar 11, 2013 at 07:23:45AM -0400, Jesus Climent wrote:
> On Mon, Mar 11, 2013 at 5:52 AM, Lars Ellenberg
> wrote:
> > On Mon, Mar 04, 2013 at 04:44:37PM -0500, Jesus Climent wrote:
> >> Any luck with this?
> >
> > Not enough context to be able to debug this.
> > Stack traces look normal,
>
On Mon, Mar 11, 2013 at 5:52 AM, Lars Ellenberg
wrote:
> On Mon, Mar 04, 2013 at 04:44:37PM -0500, Jesus Climent wrote:
>> Any luck with this?
>
> Not enough context to be able to debug this.
> Stack traces look normal,
> and even the "(stalled)" thingy in /proc/drbd
> does not need to be a cause
On Mon, Mar 04, 2013 at 04:44:37PM -0500, Jesus Climent wrote:
> Any luck with this?
Not enough context to be able to debug this.
Stack traces look normal,
and even the "(stalled)" thingy in /proc/drbd
does not need to be a cause of concern on a busy server.
Maybe it helps if you correlate the lo
Any luck with this?
On Wed, Feb 27, 2013 at 2:26 PM, Jesus Climent wrote:
> Hi
>
> As promised, I am posting as much information about this case, as I
> managed to reproduce it consistently. In the traces there is a udevd
> line that looks like it has something to do with the problem, but I am
>
Hi
As promised, I am posting as much information about this case, as I
managed to reproduce it consistently. In the traces there is a udevd
line that looks like it has something to do with the problem, but I am
still posting to see if someone has some more info:
return code = 0
--
