On Thu, 3 Apr 2014, sf...@users.sourceforge.net wrote: >> Thank you for analysing the problem! Now we know, *WHY* aufs on the te top >> of OpenAFS can lock-up a linux system. Of course, I prefer to use the >> system as it was possible until these changes. Can you suggest a >> procedure, how I can achieve this? > > If I were you, I'll try these steps. > - revert the commit b0ed5a7f in openafs. > - rebuild openafs > - test openafs alone > - test openafs with aufs > - report the problem to the openafs maintainers and suggest reverting > > But this is from my point of view. The openafs maintainers may have > different opinions.
The OpenAFS maintainers asks, if it is possible to change the locking in AUFS: https://lists.openafs.org/pipermail/openafs-info/2014-September/040996.html Is this possible, and if not: what should I tell them? Erik ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
