On 6/20/2016 1:59 PM, Garrison, Christine wrote: > > I've been tasked with turning many volumes on our site read-only. What > I've come up with is, I would like to unmount existing read-write > volumes and mount their readonly .backup volume in their place.
The .backup volume is considered transient and should not be relied upon to exist. To create a read-only volume use vos addsite to create a replica site on the same service/partition on which the normal RW volume exists. Then execute "vos release" for each volume. The normal AFS mount points do not need to be altered. When a cache manager traverses a normal mount point, if there is a .readonly volume instance that will be preferred over the normal RW instance. AFS clients cache the volume group information for a couple of hours so you should not expect the .readonly to become visible immediately on a client that has already accessed the normal RW instance. > The trouble comes in (as always) with our Samba service. We sit Samba on > top of OpenAFS to serve our users, who have not wanted to install the > OpenAFS client. It works as well as you might hope, but not for readonly > volumes in OpenAFS -- if you map a drive in Windows or Mac OS X, you may > browse the files, but any operation at all that involves reading fails > with errors. What are the errors? Obviously, any access that expects write permission or the ability to obtain a lock is going to fail when the volume isn't writable. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
