Closed stevenjswanson closed 7 years ago
metadata_csum shouldn't be used without replica_metadata, as we rely on the tick-tock scheme to maintain consistency, since at least two fields are updated in some metadata structure: something + checksum. So some code may not handle this configuration well. I think we can fix it at mount time by setting replica_metadata = 1 when metadata_csum = 1.
That's true. I think we should just combine this two flags.
On Fri, Jul 7, 2017 at 5:03 PM, Lu Zhang notifications@github.com wrote:
metadata_csum shouldn't be used without replica_metadata, as we rely on the tick-tock scheme to maintain consistency, since at least two fields are updated in some metadata structure: something + checksum. So some code may not handle this configuration well. I think we can fix it at mount time by setting replica_metadata = 1 when metadata_csum = 1.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NVSL/linux-nova/issues/30#issuecomment-313819185, or mute the thread https://github.com/notifications/unsubscribe-auth/ABQcEM4YJ1MtQ1al9SmS-hczdG-vfHgGks5sLsczgaJpZM4ON8Tz .
I agree.
-steve
-- Composed on (and maybe dictated to) my phone.
On Jul 7, 2017, at 17:29, Andiry Xu notifications@github.com wrote:
That's true. I think we should just combine this two flags.
On Fri, Jul 7, 2017 at 5:03 PM, Lu Zhang notifications@github.com wrote:
metadata_csum shouldn't be used without replica_metadata, as we rely on the tick-tock scheme to maintain consistency, since at least two fields are updated in some metadata structure: something + checksum. So some code may not handle this configuration well. I think we can fix it at mount time by setting replica_metadata = 1 when metadata_csum = 1.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NVSL/linux-nova/issues/30#issuecomment-313819185, or mute the thread < https://github.com/notifications/unsubscribe-auth/ABQcEM4YJ1MtQ1al9SmS-hczdG-vfHgGks5sLsczgaJpZM4ON8Tz
.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NVSL/linux-nova/issues/30#issuecomment-313821370, or mute the thread https://github.com/notifications/unsubscribe-auth/AIpg3cS3K8ezrcCprA7DPvNd6fuik-blks5sLs1QgaJpZM4ON8Tz .
A quick fix just to make them equal: https://github.com/NVSL/linux-nova/commit/a5f89a2f3bd68c4adad30e53ad695995ca99599e
If we are going to fix, let’s fix it right and just have on flag. This just makes the code messier and its behavior harder to understand. -steve
On Jul 7, 2017, at 10:45 PM, Lu Zhang notifications@github.com wrote:
A quick fix just to make them equal: a5f89a2 https://github.com/NVSL/linux-nova/commit/a5f89a2f3bd68c4adad30e53ad695995ca99599e — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NVSL/linux-nova/issues/30#issuecomment-313835925, or mute the thread https://github.com/notifications/unsubscribe-auth/AIpg3XJt2YVoiPDps3OsIkAY9y3pQ72wks5sLxdqgaJpZM4ON8Tz.
With these configuration options, I get a whole system hang. Sometimes w/ and sometimes w/o a bunch of assertion failures on
dmesg
.on 84d3e6afa6effd389a0b8a0129dbf22c30c48d5c, but it it's been present since at least 10142f3f22403b031b2adde4afd7bd2a85d55086.
This happens with
but not