some ATLAS AFS admin accidentally set the p.atlas.pro.tzsoft to read-only (after the nagmails) , caused confusion on the T0 people. Also some weird client thing, one of the ATLAS P1 machines did not realize the volume was now read-only (same vol id, so went to read-write - no data lost, but invisible to other clients since no "vos release"). Reverted.
CEPH will have machines on critical power in the barn, so should start to set up AFS filesservers using this. Discussion: Have 2 separate (root and AFS) blockdevices? or just put them together (would mean data+config+IP travel toegther, less risk of mixup)?
Note: need 'AlwaysAttach' unless on a separate partition
There are minutes attached to this event.
Show them.