On Thursday, Feb 12, 2004, at 06:16 Australia/Sydney, Manuel Bouyer 
wrote:

> On Wed, Feb 11, 2004 at 10:58:12AM +1100, Paul Ripke wrote:
>> Clue bat to spare, anybody?
>>
>> ksh$ raidctl -S raid4
>> raidctl: unable to open device file: raid4
>> ksh$ raidctl -S rraid4
>> Reconstruction is 100% complete.
>> Parity Re-write is 100% complete.
>> Copyback is 100% complete.
>
>
> Maybe you have a "raid4" file in the current directory ?

$ ktruss raidctl -S raid4
...
   7343 raidctl  open("raid4", 0, 0xbfbfe428)       Err#2 ENOENT
   7343 raidctl  open("raid4d", 0, 0xbfbfe428)      Err#2 ENOENT
   7343 raidctl  open("/dev/raid4", 0, 0xbfbfe428)  Err#2 ENOENT
   7343 raidctl  open("/dev/raid4d", 0, 0x64)       Err#16 EBUSY

I'm beat. Because of this, the auto-parity rebuilds don't happen
at startup. Ahh.... I think I've figured it out... on the
problem system, I've used the 'd' partition from each raid device.
On the "OK" system, I've more correctly used the 'a' partitions.
Now how am I going to fix this... Hmmm... Ah. Easy... good!

Cheers,
--
Paul Ripke
Unix/OpenVMS/TSM/DBA
I love deadlines. I like the whooshing sound they make as they fly by.
-- Douglas Adams