Re: [Evms-devel] EVMS and Drive Linking

[Steve D. <st...@us...>]

kevcorry wrote:
> On Thursday 05 June 2003 05:59, Stian B. Barmen wrote:
> >
> > EXT3 disk nr 2:
> > I first set up ext3 with three disks. I powered down, rmoved the nr.2
disk
> > and booted. Now my drive link (DL) was again reported broken and my
nr.2
> > disk was replaced with a placeholder like before. EVMS reported that it
was
> > going to put my DL in read only mode, but I used Kevin's patch so this
did
> > not happen. I mounted the DL and was able to run fix, read/write data
but
> > of course I got a lot of inode errors (missing as such), but it still
> > worked.
> >
> > Then I tried to shrink the DL in EVMS but this was not possible. It's
not
> > an option to shrink with the placeholder, you must shrink with a
physical
> > disk with no errors. Also the replace is a no go. From what I see I can
> > still extend the DL with another disk but I have not tried this.
>
> Don,
>
> Do you think DriveLinking can be updated to allow replacing a missing
child
> with another available object? It would basically be a replace without
> copying the data.

DriveLinking can be changed to allow a missing child to be replaced,
however, it is the Engine that does the actual the replace, i.e., does the
copy and swaps the objects around.  Either the Engine would have to be
changed to not do the copy, or DriveLinking would be changed to return
zeroes when the Engine reads from the missing child to do the copy.

Steve D.