This manifests itself in a corrupted registry.tdb after uprading from registry.tdb format version 1 to 3
Created attachment 6999 [details] patch for v3-6-test
Comment on attachment 6999 [details] patch for v3-6-test ack I did already review and test this. Metze please also review.
sorry, took back ack for now: this needs some update. there is something wrong here: the count is not handled correctly. And we should take and update from the master to the dbwrap_traverse wrapper that adds the count as an additional argument
Comment on attachment 6999 [details] patch for v3-6-test Incomplete
Created attachment 7003 [details] Patches for v3-6-test Michael, please check if this compiles
Comment on attachment 7003 [details] Patches for v3-6-test Metze: It compiles. :-) We also discussed that this is the right thing to do. ACK
Assigning to Karolin for inclusion into 3.6.X, whatever is fit. Note that this but can actually be pretty bad for people upgrading from earlier samba versions to 3.6, if they store data in registy, like configuration, since it will create a registry that is partly in old and partly in new format. As a workaround, the new "net registry check" tool can be used to repair the registry, but this is only in master since we unfortunately did not finish it early enough to get it into 3.6. Cheers - Michael
(In reply to comment #7) > Assigning to Karolin for inclusion into 3.6.X, whatever is fit. > > Note that this but can actually be pretty bad for people upgrading from earlier > samba versions to 3.6, if they store data in registy, like configuration, since > it will create a registry that is partly in old and partly in new format. As a > workaround, the new "net registry check" tool can be used to repair the > registry, but this is only in master since we unfortunately did not finish it > early enough to get it into 3.6. > > Cheers - Michael It's too late for 3.6.1, will be included in 3.6.2. I think we should mention that in the release notes. Do you agree? Maybe we should add the "net registry check" tool also. Is that cherry picking only?
(In reply to comment #8) > (In reply to comment #7) > > Assigning to Karolin for inclusion into 3.6.X, whatever is fit. > > > > Note that this but can actually be pretty bad for people upgrading from earlier > > samba versions to 3.6, if they store data in registy, like configuration, since > > it will create a registry that is partly in old and partly in new format. As a > > workaround, the new "net registry check" tool can be used to repair the > > registry, but this is only in master since we unfortunately did not finish it > > early enough to get it into 3.6. > > > > Cheers - Michael > > It's too late for 3.6.1, will be included in 3.6.2. That's what I assumed. > I think we should mention that in the release notes. Do you agree? Yes, definitely. You mean the release notes for 3.6.1? I can write something up if you like. > Maybe we should add the "net registry check" tool also. That would really be awesome. It has already proven very useful. > Is that cherry picking only? It should be. We also aready have a version in the v3-6-ctdb branch that we cherry-picked the master copy from. It will require a couple of preliminary patches, I think. I can check and propose a minimal patchset. Cheers - Michael
Hi Micha, (In reply to comment #9) > (In reply to comment #8) > > (In reply to comment #7) > > > Assigning to Karolin for inclusion into 3.6.X, whatever is fit. > > > > > > Note that this but can actually be pretty bad for people upgrading from earlier > > > samba versions to 3.6, if they store data in registy, like configuration, since > > > it will create a registry that is partly in old and partly in new format. As a > > > workaround, the new "net registry check" tool can be used to repair the > > > registry, but this is only in master since we unfortunately did not finish it > > > early enough to get it into 3.6. > > > > > > Cheers - Michael > > > > It's too late for 3.6.1, will be included in 3.6.2. > > That's what I assumed. > > > I think we should mention that in the release notes. Do you agree? > > Yes, definitely. You mean the release notes for 3.6.1? No, I meant for 3.6.2. If you think we should add it to the 3.6.1 release notes also, we could do that of course. > I can write something up if you like. Yes, please. > > Maybe we should add the "net registry check" tool also. > > That would really be awesome. > It has already proven very useful. > > > Is that cherry picking only? > > It should be. We also aready have a version in > the v3-6-ctdb branch that we cherry-picked the > master copy from. It will require a couple of > preliminary patches, I think. I can check and > propose a minimal patchset. Ok, thanks. Re-assigning to you as a reminder. Cheers, Karo
What's the status with attached patches? They're not in v3-6-test yet.
Michael, if you want other patches, please remove the review+.
Michael, any updates on this?
Gosh, this is still open! We need this in the next release. And the the fix for the actual traverse bug that caused the registry corruption in the upgrade is here. But we should definitely offer "net registry check" to be able to repair the registry that might have gotten corrupted in an upgrade to 3.6.X prior to these fixes. Working on providing the patch to add "net registry check". Michael
Ouch. I just realized that this is a) more embarassing but b) less severe than I thought: We do actually have registry version 2 in 3.6 and not registry version 3. But the upgrade code is only affected by this bug if going from version 1 to version 3, because in this case two traverses (changing keys) are run inside one transaction. The source of confusion must have been that the v3-6-ctdb branch sports version 3... So the good news is that we should not have broken registries by the upgrade from 3.(<6) to 3.6. The bad news is that we somehow have missed to get registry version 3 into samba 3.6. :-( So for now, I will just give the bug to Karolin in order to pick the traverse fixes for the next 3.6 release. And then we can later (in a separate bug, maybe) think about whether we should move to registry version 3 later and then also provide the "net registry check" tool along with it. Cheers - Michael
Pushed to v3-6-test. Closing out bug report. Thanks!