Hello Andy, On Fri, 17 Dec 2004 13:06:56 EST AndyLiebman@xxxxxxx wrote: | | Phillipe | | >Still, this is the first time that such a thing happens to me. What could be | the reason that >UUID would be changed ? | | If I were a betting person, I would say that the mdadm.conf file was old, Yes it was, the filesystem was created last February. | and that you had created a new array since the time you made that conf file. And | you just didn't update the conf file. Nope, nothing has changed since, no new array was created nor deleted nor modified. | | As I'm sure you know, you don't need to use a conf file anyway to use mdadm. Yes, i used a straightforward mdadm command to create the array, | That's what makes it so beautiful! All kinds of things -- like device ids -- | can change on your system and mdadm just figures it out (provided you give it a | minimal amount of info, like the correct uuid!). Sure, but again, _nothing_ had changed between last February and today, at least regarding hardware and kernel. I regularly updated the Debian packages, including mdadm, but i don't think that was the problem The mdadm.conf is the one from when the array was created, and until today i have shutdown and powered on the box right fine, for weeks and months. Maybe someone will be able to explain how the UUID can change on the disks, so that what's on disk and what's in the conf can get out of sync. | | Glad to help :) You made my day :) Thanks, Philippe - 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
