On 09.10.2012 05:02, NeilBrown wrote: > Kernel sometimes knows. Some arrays have metadata handled by user-space so > the kernel wouldn't be able to report anything. > Userspace always knows.. Thanks for the hint. I didn't think about that. > In that case, how about using /run/mdadm/map ?? > When mdadm assembles an array it needs to know the uuid, and it records this > in that file for future reference. Will that do? Thanks for the hint. Our 3.2.5-Version didn't build it for an existing location. I made it do so but I don't like the UUID format in there. I assembled UUID 12345678:12345678:12345678:12345678 and the file contains the following: md0 1.2 78563412:78563412:78563412:78563412 /dev/md0 This would be a nice file if I could grep for the UUID in the same format as I've entered it upon creation/assembly. So, I guess we can live with a custom patch for now and close the discussion here. >> Btw.: We did an "Assemble-Resize-Stop, Assemble-Resize-Stop, ..."-Test >> with "--assume-clean" and the second resize doesn't work. With >> "Assemble-Resize-Detail-Stop" it works. > > More details? What exactly do you mean by "Resize"? What exactly do you > mean by "doesn't work"? Can you make a simple script that reproduces this? > If so, I'd love to see it. I'll open a new topic for this after analysing it in more detail today. I've only seen the issue on the PC of my boss and some automation guys reported it. Cheers, Sebastian -- 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
