On 6/21/2016 2:36 AM, Jan Iven wrote: > > One way could be to serve all "readonly" content (i.e. those with rw+ro > volumes) from dedicated Samba servers that run with > > read only = yes > locking = no > and possibly > oplocks = False > (per > https://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/locking.html) > > you could also increase logging (-d, or "kill -SIGTSTP") on a test AFS > server to see what operation exactly is being attempted (and fails), see > "man dafileserver"). Works best if you isolate the volume in question to > a dedicated server.
On the AFS file servers I would recommend using audit logs instead of debug logging because they record every RPC and can be filtered by host IP address and Volume ID. Each OpCode is recorded plus the return code. On the Samba server recording "fs trace" output would show what the AFS cache manager thinks the Samba server is requesting. Samba logs will show what Samba is receiving from its clients. All of those sources will need to be correlated to identify the actual flow of requests and failures. Jeffrey Altman
<<attachment: jaltman.vcf>>
smime.p7s
Description: S/MIME Cryptographic Signature
