[OpenAFS] Read-only volume issues
Garrison, Christine
ecgarris@iu.edu
Mon, 20 Jun 2016 17:59:24 +0000
--_000_146644556439787915iuedu_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
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 m=
ount their readonly .backup volume in their place.
This appears to work well from an OpenAFS standpoint, and when exported via=
sftp or our web service, everything works as you might expect, you may bro=
wse and read and copy files out of a given volume, but not write, delete, i=
nsert or modify anything.
The trouble comes in (as always) with our Samba service. We sit Samba on to=
p 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 i=
n 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.
This linkage between OpenAFS and Samba has always been the main problem wit=
h our service, and while I recognize that this is a Samba problem, I hoped =
that someone else here might have had experience with a similar setup and c=
ould help me find a way to tell Samba to work properly with those readonly =
volumes. Unfortunately, it's not practical to tell our users to use the Ope=
nAFS client once their volume is readonly, and there isn't much motivation =
for them to do so because once this happens, they will really just have tha=
t access to get data off the service anyway.
Thanks for any help!
Chris
--
E. Christine Garrison
Indiana University
Research Technologies
Research Storage
--_000_146644556439787915iuedu_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none"><!--P{margin-top:0;margin-b=
ottom:0;} p=0A=
{margin-top:0;=0A=
margin-bottom:0}--></style>
</head>
<body dir=3D"ltr" style=3D"font-size:12pt;color:#000000;background-color:#F=
FFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<br>
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 m=
ount their readonly .backup volume in their place.<br>
<br>
This appears to work well from an OpenAFS standpoint, and when exported via=
sftp or our web service, everything works as you might expect, you may bro=
wse and read and copy files out of a given volume, but not write, delete, i=
nsert or modify anything.<br>
<br>
The trouble comes in (as always) with our Samba service. We sit Samba on to=
p 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 i=
n OpenAFS -- if you map a drive
in Windows or Mac OS X, you may browse the files, but any operation a=
t all that involves reading fails with errors. <br>
<br>
This linkage between OpenAFS and Samba has always been the main problem wit=
h our service, and while I recognize that this is a Samba problem, I hoped =
that someone else here might have had experience with a similar setup and c=
ould help me find a way to tell
Samba to work properly with those readonly volumes. Unfortunately, it's no=
t practical to tell our users to use the OpenAFS client once their volume i=
s readonly, and there isn't much motivation for them to do so because once =
this happens, they will really just
have that access to get data off the service anyway.<br>
<br>
Thanks for any help!<br>
<br>
Chris<br>
<div id=3D"Signature">
<div name=3D"divtagdefaultwrapper" style=3D"font-family:Calibri,Arial,Helve=
tica,sans-serif; font-size:; margin:0">
--<br>
E. Christine Garrison<br>
Indiana University<br>
Research Technologies<br>
Research Storage</div>
</div>
</body>
</html>
--_000_146644556439787915iuedu_--