On Mon, 30 Oct 2006, Neil Brown wrote: > > root@stoneburner:~# mdadm --assemble /dev/md0 /dev/hde /dev/hdi > > mdadm: cannot open device /dev/hde: Device or resource busy > > This is telling you that /dev/hde - or one of it's partitions - is > "Busy". This means more than just 'open'. It means mounted or > included in an md or dm array, or used for swap. > You need to find out what is keeping it busy. > Most likely dm or md. it's probably evms+ubuntu+new kernel stupidity. as far as i've determined, older (dapper) ubuntu had evms as part of the base package requirements. evms was set up in some promiscuous manner where it goes and sets up dm linear maps for every damn partition and device. nobody cared before because older kernels don't seem to stop people from using the underlying /dev/foo for md or mount or whatever. but newer kernels don't allow that any more. it looks like they dropped the evms requirement in edgy -- probably because it has the newer kernel... but people who upgraded from dapper will run into this because they'll still have evms from before. > I don't know much about dm - is there some 'pvlist' command or similar > that will show all the phys volumes it is holding on to.. "dmsetup ls" does that... for example on an ubuntu box i haven't fixed yet: # dmsetup ls --tree hda5 (253:1) `- (3:0) hda1 (253:0) `- (3:0) you can "dmsetup remove hda1" or whatever to get back the real device (but it's better to just remove or disable evms and reboot). -dean - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
