From: Steve D. <st...@us...> - 2003-03-27 19:52:56
|
Mike Tran wrote: > Jeremy Jackson wrote: > > > > Right now, I'm having trouble deleting a RAID1 region. I get Device or > > resource busy. It also happens when I use raidtools2 raidstop. To > > reproduce: > > > > Create a raid1 region. Make it into an EVMS volume. Save. Delete > > volume. Save - works ok. Now delete raid1 region. Save. -> EBUSY. > > > > With the current CVS source, I could not reproduce the problem using the > steps as described above. However, I ran into the same problem when trying > delete EVMS raid1 volume "recursively". That is to remove all segments > consumed by the raid1 region. I will investigate the problem and will keep > you posted. Jeremy, One would think that 1.9.2 would be fairly recent code. However, on 2003/03/26 I dropped significant fixes to the way volumes are handled using device-mapper, especially in the area of EVMS volumes made from non-EVMS objects. I would bet this is why Mike was unable to reproduce your problem as he is running with the latest CVS code. If you want, you can try the CVS code. The EVMS CVS tree is busy these days as we feverishly run tests and drop fixes to prepare for 2.0. We did find a problem with the following scenario: Create an MD region (used RAID1) from two DOS segments, hdd24 and hdd25. Make md0 into an EVMS volume, Carl. Save. Do a recursive delete on Carl. device-mapper coughs on removing the map for hdd24. What happens is that during the recursive delete hdd24 is marked to be deleted, hdd25 is renamed to hdd24, then the formerly hdd25 object (now hdd24) is marked to be deleted. When the changes are saved, the Engine first calls device-mapper to remove the map for hdd24. That succeeds. It then proceeds to the next object which is now also named hdd24. The Engine calls device-mapper to delete hdd24. device-mapper complains because it has no map with the name hdd24. This is a side effect of DOS partitioning renaming partitions when intermediate ones are deleted. The way to delete DOS partitions is from highest number to lowest. In this case, the RAID 1 should be made of hdd25 and hdd24, not hdd24 and hdd25. Order is important. With hdd25 coming first, the volume can be recursive deleted successfully. Steve D. |