Hi, >> >> 2) If there is a spare, it starts rebuilding the spare, and, as a >> >> result, persists sb->resync_offset==sb->size in the superblock > > I just looked into this and tested it and I don't agree. > ->resync_offset does not get set to sb->size. It gets set to the value that > curr_resync got up to which is correct .. or fairly close, it should really > be curr_resync_completed. > > So I don't think there is a big problem there. In the scenario I mentioned, I clearly end up having sb->resync_offset==sb->size (and it actually remains this way, until spare rebuild completes and "empty-resync" completes). But I am using 2.6.38-8; perhaps in your kernel this does not happen anymore. If you're interested to investigate this further, I can send you a repro script. Thanks for your help! -- 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
