Hi. I have an array of IDE disks connected to two Promise Ultra66 controllers as well as on one of the onboard IDE channels (VIA82CXXX). They make up md0 (raid-0) on a 2.4.17 kernel. Unfortunately, all the disks are not the same size, there are 2*60gb, 2*80gb and 1*100gb, for a total of 380gb. In a few weeks, I plan to add another controller and another 100 or 120gb drive, and at the same time, I want to relocate the disks so they are all connected to the Promise controllers, i.e. move hdd (60gb Maxtor) to one of the two new slots that will become available (I always try to keep one drive per channel). As for relocating the drives, someone told me that just moving them along the new ide slots so the initial device sequence (that I used in the raidtab when I mkraid'ed) is preserved would be enough for that matter. However, I'm afraid that's not right. This is the first question. After looking around, I came across the raidreconf utility at http://unthought.net/raidreconf/index.shtml First of all, that page as well as the HOWTO included in the package available there mentions that this tool was written by Jakob Østergaard but it is currently maintained by Danny Cox. The HOWTO also mentions that raidreconf can be obtained from http://oss.connex.com. However, that host seems to be down in the last few days. The version of raidreconf-latest.tgz available on the page above is dated November 1, 2001 (120092 bytes). Does anyone know if there is any more recent version, where it can be found and who is the current maintainer? So the last question is this. I know I do have to use raidreconf for adding a new disk to the array, but do I also have to use it if I just relocate the drives to different IDE slots? Does it make any difference if I maintain the initial sequence of the devices, as it was in raidtab at the time of mkraid'ing? Or is there any other similar trick one can do to do the relocation, avoiding the use of raidreconf? Apart from the possible problems one may come across with raidreconf, as warned by the authors, I also read that raidreconf will take a considerable amount of time to complete the conversion, so if there is a way to do the relocation without using raidreconf, I would prefer it, to stay on the safe side. I know these issues may have been already discussed in the past on this list, however, after searching through the mail archives, I didn't find any real answer to the questions in the last paragraph. Please accept my apologies if I'm wrong. Thanks in advance for any helpful hints you may have. Cajoline Leblanc Cajoline at chaosengine dot de PS: What is the maximum size disk most widely-available ata100 controllers can use without problems? 120 gb? Is there another barrier of some sort (like in the past) at 138gb? - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
