Bill Davidsen wrote:
Dan Williams wrote:
On Fri, 2007-10-19 at 01:04 -0700, BERTRAND Joël wrote:
I run for 12 hours some dd's (read and write in nullio)
between
initiator and target without any disconnection. Thus iSCSI code seems
to
be robust. Both initiator and target are alone on
Dan Williams wrote:
On Fri, 2007-10-19 at 01:04 -0700, BERTRAND Joël wrote:
I never see any oops with this patch. But I cannot create a
RAID1 array
with a local RAID5 volume and a foreign RAID5 array exported by iSCSI.
iSCSI seems to works fine, but RAID1 creation randomly aborts due to
On Fri, 2007-10-19 at 01:04 -0700, BERTRAND Joël wrote:
> I never see any oops with this patch. But I cannot create a
> RAID1 array
> with a local RAID5 volume and a foreign RAID5 array exported by iSCSI.
> iSCSI seems to works fine, but RAID1 creation randomly aborts due to a
> unknown SCS
Bill Davidsen wrote:
Dan Williams wrote:
I found a problem which may lead to the operations count dropping
below zero. If ops_complete_biofill() gets preempted in between the
following calls:
raid5.c:554> clear_bit(STRIPE_OP_BIOFILL, &sh->ops.ack);
raid5.c:555> clear_bit(STRIPE_OP_BIOFILL, &sh
Dan Williams wrote:
I found a problem which may lead to the operations count dropping
below zero. If ops_complete_biofill() gets preempted in between the
following calls:
raid5.c:554> clear_bit(STRIPE_OP_BIOFILL, &sh->ops.ack);
raid5.c:555> clear_bit(STRIPE_OP_BIOFILL, &sh->ops.pending);
...th
Dan,
I'm testing your last patch (fix-biofill-clear2.patch). It seems to
work:
Every 1.0s: cat /proc/mdstatThu Oct 18
10:28:55 2007
Personalities : [raid1] [raid6] [raid5] [raid4]
md7 : active raid1 sdi1[1] md_d0p1[0]
1464725632 blocks [2/2]
On Wed, 2007-10-17 at 09:44 -0700, BERTRAND Joël wrote:
> Dan,
>
> I have modified get_stripe_work like this :
>
> static unsigned long get_stripe_work(struct stripe_head *sh)
> {
> unsigned long pending;
> int ack = 0;
> int a,b,c,d,e,f,g;
>
>
Dan Williams wrote:
On 10/17/07, Dan Williams <[EMAIL PROTECTED]> wrote:
On 10/17/07, BERTRAND Joël <[EMAIL PROTECTED]> wrote:
BERTRAND Joël wrote:
Hello,
I run 2.6.23 linux kernel on two T1000 (sparc64) servers. Each
server has a partitionable raid5 array (/dev/md/d0) and I have to
s
Dan Williams wrote:
On 10/17/07, BERTRAND Joël <[EMAIL PROTECTED]> wrote:
BERTRAND Joël wrote:
Hello,
I run 2.6.23 linux kernel on two T1000 (sparc64) servers. Each
server has a partitionable raid5 array (/dev/md/d0) and I have to
synchronize both raid5 volumes by raid1. Thus, I have t
On 10/17/07, Dan Williams <[EMAIL PROTECTED]> wrote:
> On 10/17/07, BERTRAND Joël <[EMAIL PROTECTED]> wrote:
> > BERTRAND Joël wrote:
> > > Hello,
> > >
> > > I run 2.6.23 linux kernel on two T1000 (sparc64) servers. Each
> > > server has a partitionable raid5 array (/dev/md/d0) and I have
On 10/17/07, BERTRAND Joël <[EMAIL PROTECTED]> wrote:
> BERTRAND Joël wrote:
> > Hello,
> >
> > I run 2.6.23 linux kernel on two T1000 (sparc64) servers. Each
> > server has a partitionable raid5 array (/dev/md/d0) and I have to
> > synchronize both raid5 volumes by raid1. Thus, I have trie
BERTRAND Joël wrote:
Hello,
I run 2.6.23 linux kernel on two T1000 (sparc64) servers. Each
server has a partitionable raid5 array (/dev/md/d0) and I have to
synchronize both raid5 volumes by raid1. Thus, I have tried to build a
raid1 volume between /dev/md/d0p1 and /dev/sdi1 (exported
Hello,
I run 2.6.23 linux kernel on two T1000 (sparc64) servers. Each server
has a partitionable raid5 array (/dev/md/d0) and I have to synchronize
both raid5 volumes by raid1. Thus, I have tried to build a raid1 volume
between /dev/md/d0p1 and /dev/sdi1 (exported by iscsi from the se
13 matches
Mail list logo