Should 13.0-U2 have an upgrade readiness checker?

[Samuel Tai]

There seems to be a significant number of 13.0-RELEASE users experiencing difficulties with SMB after upgrading the 13.0-U1, which seem to be due to incorrect pool layout (using root dataset for SMB) or non-standard permissions/ACLs in their shared datasets. Should 13.0-U2 include additional checks for these corner cases, and advise users with these conditions they need to remediate before upgrading?

 

[anodos]

There seems to be a significant number of 13.0-RELEASE users experiencing difficulties with SMB after upgrading the 13.0-U1, which seem to be due to incorrect pool layout (using root dataset for SMB) or non-standard permissions/ACLs in their shared datasets. Should 13.0-U2 include additional checks for these corner cases, and advise users with these conditions they need to remediate before upgrading?

I'm actively investigating the permissions issues people are seeing on U1. It looks like potentially a regression related to some refactoring when user's ACL entries lack the SYNCHRONIZE bit. We set this by default in our ACL editor, but there are other ways to set ACLs and apparently some cases have stripped it. There will probably be a few more minor fixes for U2, but in general case I don't think there should be anything that requires a readiness checker. Core -> SCALE will be a much bigger step that may benefit from this though.

 

[mistermanko]

Then maybe post a short quick-tips for the the unadvanced users, on how to check for the synchronized bit prior to the update?