On Tue, Oct 16, 2012 at 10:58:49AM -0700, Dan Williams wrote:
> I think this may be a bug in __raid_run_ops that is only possible when
> raid offload and CONFIG_MULTICORE_RAID456 are enabled. I'm thinking
> the descriptor is completed and recycled to another requester in the
> space between these
On Tue, Oct 16, 2012 at 10:58:49AM -0700, Dan Williams wrote:
I think this may be a bug in __raid_run_ops that is only possible when
raid offload and CONFIG_MULTICORE_RAID456 are enabled. I'm thinking
the descriptor is completed and recycled to another requester in the
space between these two
On Tue, Oct 16, 2012 at 02:48:25PM +0200, Borislav Petkov wrote:
> On Tue, Oct 16, 2012 at 11:26:01AM +0200, Laurent CARON wrote:
> > On Tue, Oct 16, 2012 at 11:03:53AM +0200, Borislav Petkov wrote:
> > > That's:
> > >
> > > BUG_ON(async_tx_te
On Tue, Oct 16, 2012 at 11:03:53AM +0200, Borislav Petkov wrote:
> That's:
>
> BUG_ON(async_tx_test_ack(depend_tx) || txd_next(depend_tx) ||
> txd_parent(tx));
>
> but probably the b0rkage happens up the stack. And this __raid_run_ops
> is probably starting
On Tue, Oct 16, 2012 at 11:03:53AM +0200, Borislav Petkov wrote:
That's:
BUG_ON(async_tx_test_ack(depend_tx) || txd_next(depend_tx) ||
txd_parent(tx));
but probably the b0rkage happens up the stack. And this __raid_run_ops
is probably starting the
On Tue, Oct 16, 2012 at 02:48:25PM +0200, Borislav Petkov wrote:
On Tue, Oct 16, 2012 at 11:26:01AM +0200, Laurent CARON wrote:
On Tue, Oct 16, 2012 at 11:03:53AM +0200, Borislav Petkov wrote:
That's:
BUG_ON(async_tx_test_ack(depend_tx) ||
txd_next(depend_tx
Hi,
I'm currently replacing an old system (HP DL 380 G5) by new dell R720xd.
On those new boxes I did configure the H310 controler as plain JBOD.
Those boxes appear to crash more often than not (from 5 mins to a couple
of hours).
I have the impression those crashes appear under heavy IO.
The
Hi,
I'm currently replacing an old system (HP DL 380 G5) by new dell R720xd.
On those new boxes I did configure the H310 controler as plain JBOD.
Those boxes appear to crash more often than not (from 5 mins to a couple
of hours).
I have the impression those crashes appear under heavy IO.
The
Hi,
I'm back with my crash, oomkiller. problems on my DRBD cluster of 2
servers.
I compiled a 2.6.22 kernel with slab/slab debugging turned on.
Here is the last oom-killer message I got on that server.
I couldn't wait until a crash since a lot of users are working on it:
Hi,
I'm back with my crash, oomkiller. problems on my DRBD cluster of 2
servers.
I compiled a 2.6.22 kernel with slab/slab debugging turned on.
Here is the last oom-killer message I got on that server.
I couldn't wait until a crash since a lot of users are working on it:
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
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
Stefan Seifert wrote:
> The deadlock also occures with 0.7.x. A patch for that is floating around.
Here is a transcript from a mail I sent to Lars Ellenberg
It should 'normally' be fixed.
Am I wrong ?
Thanks
On Sun, Sep 16, 2007 at 05:34:01PM +0200, Laurent CARON wrote:
> > Lars
Hi,
I did experience a quite strange problem (at least for me) on the first
node of our 2 node cluster.
This is basically an imap/smtp/http proxy server.
One of the imapd processes started to use a lot of cpu, memory... this
morning.
Oomkiller showed up and killed slapd, imapd, amavisd
I
Hannes Dorbath wrote:
> On 28.09.2007 11:00, Laurent CARON wrote:
>> The $HOME directories are stored on a drbd (version: 0.7.24
>> (api:79/proto:74)) partition (with an XFS filesystem).
>
> Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with 2.6.22?
I only exper
Hannes Dorbath wrote:
On 28.09.2007 11:00, Laurent CARON wrote:
The $HOME directories are stored on a drbd (version: 0.7.24
(api:79/proto:74)) partition (with an XFS filesystem).
Was the deadlock with 2.6.22 only in 0.8.x? Is 0.7.x fine with 2.6.22?
I only experienced it with 2.6.22.
Since
Hi,
I did experience a quite strange problem (at least for me) on the first
node of our 2 node cluster.
This is basically an imap/smtp/http proxy server.
One of the imapd processes started to use a lot of cpu, memory... this
morning.
Oomkiller showed up and killed slapd, imapd, amavisd
I
Stefan Seifert wrote:
The deadlock also occures with 0.7.x. A patch for that is floating around.
Here is a transcript from a mail I sent to Lars Ellenberg
It should 'normally' be fixed.
Am I wrong ?
Thanks
On Sun, Sep 16, 2007 at 05:34:01PM +0200, Laurent CARON wrote:
Lars Ellenberg
Frederik Deweerdt wrote:
> On Thu, Aug 23, 2007 at 01:15:12PM +0200, Laurent CARON wrote:
>> Hi,
>>
>> One of my server crashes randomly.
>>
>> I suspect a filesystem corruption.
> What makes you think so? I'd check the memory with memtest.
I suspect the f
Hi,
One of my server crashes randomly.
I suspect a filesystem corruption.
Can you please confirm this ?
Thanks
Here is the relevant part from /var/log/syslog
Aug 23 12:10:55 berlin kernel: BUG: unable to handle kernel paging
request at virtual address 74c1803d
Aug 23 12:10:55 berlin
Hi,
One of my server crashes randomly.
I suspect a filesystem corruption.
Can you please confirm this ?
Thanks
Here is the relevant part from /var/log/syslog
Aug 23 12:10:55 berlin kernel: BUG: unable to handle kernel paging
request at virtual address 74c1803d
Aug 23 12:10:55 berlin
Frederik Deweerdt wrote:
On Thu, Aug 23, 2007 at 01:15:12PM +0200, Laurent CARON wrote:
Hi,
One of my server crashes randomly.
I suspect a filesystem corruption.
What makes you think so? I'd check the memory with memtest.
I suspect the filesystem, because it happened to me on 2 other
Christoph Hellwig wrote:
> On Tue, Aug 07, 2007 at 09:31:22AM +1000, David Chinner wrote:
>> On Mon, Aug 06, 2007 at 09:38:19AM +0200, Laurent Caron wrote:
>>> Hi,
>>>
>>> I'm using an XFS filesystem over DRBD for a few weeks on this machine
>>> and di
David Chinner wrote:
> On Mon, Aug 06, 2007 at 09:38:19AM +0200, Laurent Caron wrote:
>> Hi,
>>
>> I'm using an XFS filesystem over DRBD for a few weeks on this machine
>> and did experience an oops.
>
> ..
>> Aug 3 10:59:47 fileserv kernel: [] cache_f
David Chinner wrote:
On Mon, Aug 06, 2007 at 09:38:19AM +0200, Laurent Caron wrote:
Hi,
I'm using an XFS filesystem over DRBD for a few weeks on this machine
and did experience an oops.
..
Aug 3 10:59:47 fileserv kernel: [c0164be9] cache_flusharray+0x59/0xd0
Aug 3 10:59:47
Christoph Hellwig wrote:
On Tue, Aug 07, 2007 at 09:31:22AM +1000, David Chinner wrote:
On Mon, Aug 06, 2007 at 09:38:19AM +0200, Laurent Caron wrote:
Hi,
I'm using an XFS filesystem over DRBD for a few weeks on this machine
and did experience an oops.
..
Aug 3 10:59:47 fileserv
Hi,
I'm using an XFS filesystem over DRBD for a few weeks on this machine
and did experience an oops.
Aug 3 10:59:47 fileserv kernel: Oops: 0002 [#1]
Aug 3 10:59:47 fileserv kernel: SMP
Aug 3 10:59:47 fileserv kernel: CPU:
Hi,
I'm using an XFS filesystem over DRBD for a few weeks on this machine
and did experience an oops.
Aug 3 10:59:47 fileserv kernel: Oops: 0002 [#1]
Aug 3 10:59:47 fileserv kernel: SMP
Aug 3 10:59:47 fileserv kernel: CPU:
shafa.hidee wrote:
Hi All,
Where we can find specs for writing driver for Intel PRO 100 card.
Regards
Shafahidee
already supported.
isn't it?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
shafa.hidee wrote:
Hi All,
Where we can find specs for writing driver for Intel PRO 100 card.
Regards
Shafahidee
already supported.
isn't it?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
32 matches
Mail list logo
