On Tue, Oct 11, 2011 at 9:22 AM, Alexander Swen <[email protected]> wrote: > > > Met vriendelijke groet, > Alexander Swen > ________________________________ > > From: "Steve French" <[email protected]> > To: "Alexander Swen" <[email protected]> > Cc: "Jeff Layton" <[email protected]>, [email protected], "Suresh > Jayaraman" <[email protected]> > Sent: Tuesday, 11 October, 2011 4:20:17 PM > Subject: Re: cifs ignores sysct setting > > On Tue, Oct 11, 2011 at 9:14 AM, Alexander Swen <[email protected]> wrote: >> Hi Steve, >> >> thanks for your response. >> >> no, we do permanently turn off oplocks due to some performance issues >> (with >> some NAS device where our colleagues can't (don't want) configure nfs >> apparently ;-(. >> we do this on several (>20) servers and across reboots... > > Isn't it easier just to turn this (oplocks) off on the server? At > least with Linux cifs.ko > you can turn off oplocks at runtime, with some clients it is much harder. > > > ahhh. no, we are not the only users on the nas, our clientservers should > just turn off oplocks. it is, we make backups to the nas device and those > files grow quite big.
If you are trying to save RAM on the client, and don't want to cache, and are just using the linux cifs client for backup, you could mount with "forcedirectio" (which turns off caching a little more easily). -- Thanks, Steve -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
