Oh yes, it's really only to play with... I only trust data to alpha
software once I've figured out how to break it...... GRINS!
Well, the problem is that I have simulated a failure of half of the
mirror, then put the disk back in (hot) and done "raidhotadd" the device
was added again but with a different disk number and it would then not
sync....
Is there a way to force a device to be a particular disk number, or is
there another reason why it's not working?
mabe I've missed somthing important?
Also, I tried creating a raid1 with one disk (So as to reserve the space
for the superblock and allow mirroring later)... it tried to resync and
got itself stuck in a loop.
James
On Fri, 29 Jan 1999, D. Lance Robinson wrote:
> James,
>
> First of all, you probably want to reboot. This will rename your devices
> to their typical values. To add a device into a failed raid slot, you
> can use the raidhotadd command. do something like:
>
> raidhotadd /dev/md0 /dev/hdc2
>
> This will add the device to the raid set and start a resync operation.
>
> BTW: I hope you are only trying raid out with the setup you have shown
> below. Using the same device more than once in a raid set is: 1)slow,
> and 2)does not protect your data.
>
> I hope this helps some. I may be off target in what you have done and
> what you want to do.
>
> <>< Lance.
>
>
> A James Lewis wrote:
>
> > After testing various failure conditions, I seem to be stuck because the
> > system allocated new disk numbers to the disks....
> >
> > RAID1 conf printout:
> > --- wd:1 rd:2 nd:3
> > disk 0, s:0, o:1, n:0 rd:0 us:1 dev:hdb1
> > disk 1, s:0, o:0, n:1 rd:1 us:1 dev:[dev 00:00]
> > disk 2, s:1, o:0, n:2 rd:2 us:1 dev:hdb3
> > disk 3, s:1, o:0, n:3 rd:3 us:1 dev:hdb2
> > disk 4, s:0, o:0, n:0 rd:0 us:0 dev:[dev 00:00]
> >
> > I need to get "disk 1" back to the correct device.... is there a way to do
> > this? Perhaps there is a FAQ, but I guess not since this is so new....
> >
>
James ([EMAIL PROTECTED])
My operating system unders~1 long filena~1, and yours?
