[OpenAFS] Supergroups enabled by default in openafs 1.6.1 rpm packages?

[Jeffrey Altman]

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig137EE6E4BC6AB1189D92168C
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/20/2012 11:46 AM, Russ Allbery wrote:
>
> He has an existing cell with supergroups enabled and a bunch of
> supergroups in use.  He accidentally upgraded to a ptserver without
> supergroup support.  He's since replaced that with one that does have
> supergroup support, but he's wondering if the ptserver without supergro=
up
> support could have corrupted the supergroup portions of his database wh=
ile
> it was running.
>=20
> I wasn't sure -- I'd heard in the past that people were worried about w=
hat
> the ptserver might do to the database, but I don't know that specifics
> were ever discussed.

Jeff Hutzelman and I discussed this situation earlier this week.  The
conclusion was that deletions of groups with groups as members or as
members of a group can produce dangling references which:

 a. can generate inconsistent results

 b. may confuse tools that manage memberships

If there were no deletions while the supergroup unaware ptserver was
master, there should be no problems.  If there were (or may have been)
deletions, someone should write a tool to restore consistency to
the supergroup relationships and recover unreferenced but used blocks.

Jeffrey Altman



--------------enig137EE6E4BC6AB1189D92168C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iQEcBAEBAgAGBQJQ00fZAAoJENxm1CNJffh41E4IAL64ByYimVAyOrKN6Zuso3/z
cleJVIlPZiXyePYQ8/0LXL//szzJ19Z9KAEPJnyF1Ux7osiYO9x4lKdeumimjHEs
0CtPExOiOrl7kVJZzctm0eFQ0NqH38ueuquKhAzZI2wpi4mAJKGxkbOMEEEtLILo
M1gnO8ByIJAzEM8Nroft3jyb8+2rBdEp1+J7SaL4bQFv4QMP+LNdMmLjdewi4iuA
ml6/QJn2l/iqzoxx3ovzHa70ooEI6DR1+L89PNzEVtVe+lkBhXNmVOeW59dpe3T3
o2Ge5OoEGbcDUKWQ9wQB0aHHC3breDbE4+4GkWHeN6SkaXQAjLdgW9yd8NypDGQ=
=ThDM
-----END PGP SIGNATURE-----

--------------enig137EE6E4BC6AB1189D92168C--