On Fri, 26 Mar 2010 10:52:07 +0300
"Majed B." <majedb@gmail.com> wrote:

quoted text
> Why not treat this similar to how hardware RAID manages disks & spares?
> Disk has no metadata -> new -> use as spare.
> Disk has metadata -> array exists -> add to array.
> Disk has metadata -> array doesn't exist (disk came from another
> system) -> sit idle & wait for an admin to do the work.

That would certainly be a sensible configuration to support.

quoted text
> 
> As to identify disks and know which disks were removed and put back to
> an array, there's the metadata & there's the disk's serial number
> which can obtained using hdparm. I also think that all disks now
> include a World Wide Number (WWN) which is more suitable for use in
> this case than a disk's serial number.
> 
> Some people rant because they see things only from their own
> perspective and assume that there's no case or scenario but their own.
> So don't pay too much attention :p
> 
> Here's a scenario: What if I had an existing RAID1 array of 3 disks. I
> bought a new disk and I wanted to make a new array in the system. So I
> add the new disk, and I want to use one of the RAID1 array disks in
> this new array.
> 
> Being lazy, instead of failing the disk then removing it using the
> console, I just removed it from the port then added it again. I
> certainly don't want mdadm to start resyncing, forcing me to wait!

Lazy people often do cause themselves more work in the long run, there is
nothing much we can do about that.  Take it up with Murphy.

quoted text
> 
> As you can see in this scenario, it includes the situation where an
> admin is a lazy bum who is going to use the command line anyway to
> make the new array but didn't bother to properly remove the disk he
> wanted. And there's the case of the newly added disk.
> 
> Why assume things & guess when an admin should know what to do?
> I certainly don't want to risk my arrays in mdadm guessing for me. And
> keep one thing in mind: How often do people interact with storage
> systems?
> 
> If I configure mdadm today, the next I may want to add or replace a
> disk would be a year later. I certainly would have forgotten whatever
> configuration was there! And depending on the situation I have, I
> certainly wouldn't want mdadm to guess.

That is a point worth considering.  Where possible we should discourage
configurations that would be 'surprising'.
Unfortunately a thing that is surprising to one person in one situation may
be completely obvious to someone else in a different situation.

Thanks,
NeilBrown

--
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