David Chinner wrote:
> Can you turn on slab debug and poisoning and see where
> the kernel fails with that? e.g. set:
>
> CONFIG_DEBUG_SLAB=y
> CONFIG_DEBUG_SLAB_LEAK=y
I was a little worried about letting those servers in such a bad state,
and went the "easy" way.
I did upgrade from drbd
David Chinner wrote:
Can you turn on slab debug and poisoning and see where
the kernel fails with that? e.g. set:
CONFIG_DEBUG_SLAB=y
CONFIG_DEBUG_SLAB_LEAK=y
I was a little worried about letting those servers in such a bad state,
and went the easy way.
I did upgrade from drbd 0.7.X to
On Thu, Oct 04, 2007 at 09:29:40AM +0200, Laurent Caron wrote:
>
> Hi,
>
> I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch,
> ), and latest svn (3062) 0.7.X drbd.
>
> After just 2 days of uptime, I did experience another crash.
>
> I wonder if it is an XFS related
On Thu, Oct 04, 2007 at 09:29:40AM +0200, Laurent Caron wrote:
Hi,
I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch,
), and latest svn (3062) 0.7.X drbd.
After just 2 days of uptime, I did experience another crash.
I wonder if it is an XFS related bug, a
Hi,
I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch, ),
and latest svn (3062) 0.7.X drbd.
After just 2 days of uptime, I did experience another crash.
I wonder if it is an XFS related bug, a DRBD one, or related to XFS on top of
DRBD.
This bug seems to occur with
Hi,
I did compile a fresh 2.6.21.7 kernel from kernel.org (no distro patch, ),
and latest svn (3062) 0.7.X drbd.
After just 2 days of uptime, I did experience another crash.
I wonder if it is an XFS related bug, a DRBD one, or related to XFS on top of
DRBD.
This bug seems to occur with
6 matches
Mail list logo
