RAID0 problems with 2.4.21-BK current

RAID0 problems with 2.4.21-BK current

[Marc-Christian Petersen]

Hi Neil,

this:

http://linux.bkbits.net:8080/linux-2.4/patch@1.884.1.69?nav=index.html|ChangeSet@-2w|cset@1.884.1.69

patch breaks at least RAID 0 recognition at boottime (infinite loop) and also 
breaks mkraid /dev/md0. Never stops, State D.

Ripping the patch out helps.

ciao, Marc

Re: RAID0 problems with 2.4.21-BK current

[Neil Brown]

On Sunday December 29, m.c.p@wolk-project.de wrote:
> Hi Neil,
> 
> this:
> 
> http://linux.bkbits.net:8080/linux-2.4/patch@1.884.1.69?nav=index.html|ChangeSet@-2w|cset@1.884.1.69
> 
> patch breaks at least RAID 0 recognition at boottime (infinite loop) and also 
> breaks mkraid /dev/md0. Never stops, State D.

Odd. It works for me.  
Can you find out more about the 'D' state the it is stuck in?
alt-sysrq-T
should provide a stack trace which should get caught in some log
file. 

 ps axgl
could list something vaguely useful in the 'wchan' column.

NeilBrown

Re: RAID0 problems with 2.4.21-BK current

[Neil Brown]

On Sunday December 29, m.c.p@wolk-project.de wrote:
> Hi Neil,
> 
> this:
> 
> http://linux.bkbits.net:8080/linux-2.4/patch@1.884.1.69?nav=index.html|ChangeSet@-2w|cset@1.884.1.69
> 
> patch breaks at least RAID 0 recognition at boottime (infinite loop) and also 
> breaks mkraid /dev/md0. Never stops, State D.
> 
> Ripping the patch out helps.

Is your raid0 ontop of a raid1 ???
If so, this patch is needed.

NeilBrown

--------------------------------------------------------
Set BH_Locked when accessing MD superblocks

Some silly drivers (like raid1 !!) want  BH_Locked to be set on all IO,
so we humour them by setting the bit when doing superblock IO.

 ----------- Diffstat output ------------
 ./drivers/md/md.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff ./drivers/md/md.c~current~ ./drivers/md/md.c
--- ./drivers/md/md.c~current~	2002-12-17 15:20:57.000000000 +1100
+++ ./drivers/md/md.c	2003-01-02 11:05:20.000000000 +1100
@@ -489,7 +489,7 @@ static int sync_page_io(kdev_t dev, unsi
 	init_buffer(&bh, bh_complete, &event);
 	bh.b_rdev = dev;
 	bh.b_rsector = sector;
-	bh.b_state	= (1 << BH_Req) | (1 << BH_Mapped);
+	bh.b_state	= (1 << BH_Req) | (1 << BH_Mapped) | (1 << BH_Locked);
 	bh.b_size = size;
 	bh.b_page = page;
 	bh.b_reqnext = NULL;

Re: RAID0 problems with 2.4.21-BK current

[Marc-Christian Petersen]

On Thursday 02 January 2003 01:09, Neil Brown wrote:

Hi Neil,

> Is your raid0 ontop of a raid1 ???
> If so, this patch is needed.
nope, surely not ;) ... Plain raid0.

ciao, Marc

Re: RAID0 problems with 2.4.21-BK current

[Neil Brown]

On Thursday January 2, m.c.p@wolk-project.de wrote:
> On Thursday 02 January 2003 01:09, Neil Brown wrote:
> 
> Hi Neil,
> 
> > Is your raid0 ontop of a raid1 ???
> > If so, this patch is needed.
> nope, surely not ;) ... Plain raid0.

Hmmm...  Can you tell me anything else about your set up that might be
different to mine?
What drives are you using? Which driver do they use?  i386? anything
else?

NeilBrown

Re: RAID0 problems with 2.4.21-BK current

[Marc-Christian Petersen]

On Thursday 02 January 2003 22:32, Neil Brown wrote:

Hi Neil,

> Hmmm...  Can you tell me anything else about your set up that might be
> different to mine?
> What drives are you using? Which driver do they use?  i386? anything
> else?

Data captured while 2.4.20 running (I cannot boot into .21-BK now)

1. root@codeman:[/] # hdparm -i /dev/hde
/dev/hde:
 Model=FUJITSU MPG3409AT E, FwRev=82B5, SerialNo=VH46T1702WRC
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=DualPortCache, BuffSize=2048kB, MaxMultSect=16, MultSect=16
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=80063424
 IORDY=yes, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4 
 DMA modes:  mdma0 mdma1 mdma2 
 UDMA modes: udma0 udma1 udma2 udma3 udma4 *udma5 
 AdvancedPM=yes: disabled (255) WriteCache=enabled
 Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1:  1 2 3 4 5

2. Quantum Fireball 40GB (no more info because drive died yesterday)

... connected to:

01:01.0 RAID bus controller: Promise Technology, Inc. 20268R (rev 02) (prog-if 
85)
        Subsystem: Promise Technology, Inc.: Unknown device 4d68
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B-
        Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- 
<TAbort- <MAbort- >SERR- <PERR-
        Latency: 32 (1000ns min, 4500ns max), cache line size 08
        Interrupt: pin A routed to IRQ 11
        Region 0: I/O ports at a400 [size=8]
        Region 1: I/O ports at a000 [size=4]
        Region 2: I/O ports at 9c00 [size=8]
        Region 3: I/O ports at 9800 [size=4]
        Region 4: I/O ports at 9400 [size=16]
        Region 5: Memory at efc00000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at efdd0000 [disabled] [size=64K]
        Capabilities: [60] Power Management version 1
                Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-



root@codeman:[/] # cat /proc/cpuinfo 
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 11
model name      : Intel(R) Celeron(TM) CPU                1300MHz
stepping        : 1
cpu MHz         : 1295.709
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 mmx fxsr sse
bogomips        : 2588.67




Kernel Config:
--------------
[*] Multiple devices driver support (RAID and LVM)
<M>  RAID support
<M>   RAID-0 (striping) mode

- everything else from that submenu disabled!



/etc/raidtab:
-------------
raiddev /dev/md0
       raid-level              0
       nr-raid-disks           2
       nr-spare-disks          0
       chunk-size              4
       persistent-superblock   1
       device                  /dev/hde2
       raid-disk               0
       device                  /dev/hdf2
       raid-disk               1

hde2 and hdf2 are type fd. Made with mkraid /dev/md0.

mkraid /dev/md0 hangs with the mentioned patch some time ago.
RAID detection hangs at boot with the mentioned patch ... bla ^ ;)

w/o all works. Anything else you need?

ciao, Marc