Followup to: <16764.39990.547866.885761@xxxxxxxxxxxxxxx> By author: Neil Brown <neilb@xxxxxxxxxxxxxxx> In newsgroup: linux.dev.raid > > On Monday October 25, jim@xxxxxxxx wrote: > > > Does this fix the problem? > > > It is definitely wrong as it is. > > > > > .. > > > case RECONSTRUCT_WRITE: > > > - case UPDATE_PARITY: /* Is this right? */ > > > > No, it does not. Same sort of corruption with that line removed. > > > > Thanks. I'll try harder... > > Looking at the script, the corruption happens while resync is still > going on. If you wait for resync to finish, do you still get > corruption? > The version of the script I posted does wait for the resync to finish before writing; it still exhibits the same problem. -hpa - 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
