On 02/15/2011 03:03 AM, chambal wrote:
> chambal <2iow-l...@dea.spamcon.org> wrote:
>
>> chambal <2iow-l...@dea.spamcon.org> wrote:
>>
>>> "J. Ryan Earl" wrote:
>>>
On Sun, Nov 7, 2010 at 1:04 AM, chambal <2iow-l...@dea.spamcon.org> wrote:
>>> Then at the "drbadadm attach r0" step,
chambal <2iow-l...@dea.spamcon.org> wrote:
>chambal <2iow-l...@dea.spamcon.org> wrote:
>
>>"J. Ryan Earl" wrote:
>>
>>>On Sun, Nov 7, 2010 at 1:04 AM, chambal <2iow-l...@dea.spamcon.org> wrote:
>>>
>> Then at the "drbadadm attach r0" step, it crashed. Nothing
>>>[...]
>>>
>> showe
chambal <2iow-l...@dea.spamcon.org> wrote:
>"J. Ryan Earl" wrote:
>
>>On Sun, Nov 7, 2010 at 1:04 AM, chambal <2iow-l...@dea.spamcon.org> wrote:
>>
>>> >> Then at the "drbadadm attach r0" step, it crashed. Nothing
>>>
>>[...]
>>
>>> >> showed in the syslog or watch windows (it crashed instantly)
"J. Ryan Earl" wrote:
>On Sun, Nov 7, 2010 at 1:04 AM, chambal <2iow-l...@dea.spamcon.org> wrote:
>
>> >> Then at the "drbadadm attach r0" step, it crashed. Nothing
>>
>[...]
>
>> >> showed in the syslog or watch windows (it crashed instantly).
>> >> After reboot, nothing in syslog after the abo
On Sun, Nov 7, 2010 at 1:04 AM, chambal <2iow-l...@dea.spamcon.org> wrote:
> >> Then at the "drbadadm attach r0" step, it crashed. Nothing
>
[...]
> >> showed in the syslog or watch windows (it crashed instantly).
> >> After reboot, nothing in syslog after the above lines, until the
> >> new boo
Digimer wrote:
>On 10-11-07 12:46 AM, chambal wrote:
>> Thanks for the help. At the "modprobe drbd" step, the watch
>> window began showing:
>>
>> version: 8.3.7 (api:88/proto:86-92)
>> srcversion: 582E47DEE6FD9EC45926ECF
>>
>> And syslog showed:
>>
>> Nov 6 21:31:35 f13-1 kernel: drbd: init
On 10-11-07 12:46 AM, chambal wrote:
> Thanks for the help. At the "modprobe drbd" step, the watch
> window began showing:
>
> version: 8.3.7 (api:88/proto:86-92)
> srcversion: 582E47DEE6FD9EC45926ECF
>
> And syslog showed:
>
> Nov 6 21:31:35 f13-1 kernel: drbd: initialized. Version: 8.3.7
> (
Digimer wrote:
>On 10-11-06 10:32 PM, chambal wrote:
>> Not having much luck pursuing this - on a newer OS, I cannot even
>> run DRBD - I get an immediate kernel panic.
>>
>> I was hopeful that a newer OS on this VIA EPIA-M800 hardware
>> (with OCZ Vertex-Turbo SSD) might solve the intermittent
On 10-11-06 10:32 PM, chambal wrote:
> Not having much luck pursuing this - on a newer OS, I cannot even
> run DRBD - I get an immediate kernel panic.
>
> I was hopeful that a newer OS on this VIA EPIA-M800 hardware
> (with OCZ Vertex-Turbo SSD) might solve the intermittent lockup
> problem. I ch
rk with
>the disk and network to approximate how DRBD interacts with the
>system. If this were possible, and I could trigger the problem
>this way, it would at least let me demonstrate that the problem
>is not "something with DRBD".
>
>>
>>-Original Message--
Message-
>From: drbd-user-boun...@lists.linbit.com
>[mailto:drbd-user-boun...@lists.linbit.com] On Behalf Of chambal
>Sent: 29 October 2010 09:50
>To: drbd-user@lists.linbit.com
>Subject: Re: [DRBD-user] System lockup with DRBD
>
>chambal <2iow-l...@dea.spamcon.org> w
chambal
Sent: 29 October 2010 09:50
To: drbd-user@lists.linbit.com
Subject: Re: [DRBD-user] System lockup with DRBD
chambal <2iow-l...@dea.spamcon.org> wrote:
>I have a pair of VIA M800 Mini-ITX with SSD (one OCZ
>Vertex-Turbo, one Intel), and CentOS 5.5 with current patches.
>
&g
chambal <2iow-l...@dea.spamcon.org> wrote:
>I have a pair of VIA M800 Mini-ITX with SSD (one OCZ
>Vertex-Turbo, one Intel), and CentOS 5.5 with current patches.
>
>When I have DRBD active on both units, at some random point but
>always within one day, one of the units has completely locked up.
>In
I have a pair of VIA M800 Mini-ITX with SSD (one OCZ
Vertex-Turbo, one Intel), and CentOS 5.5 with current patches.
When I have DRBD active on both units, at some random point but
always within one day, one of the units has completely locked up.
In all but one case, it's the Primary unit.
When I
14 matches
Mail list logo
