On Wed, 12 Oct 2011 09:10:52 +0200 (CEST) Alexander Swen <alex@xxxxxxx> wrote: > > > > > > > > > > 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). > > Hi Steve, it was that we had i/o timeouts on our cifs mounted volume while doing rsyncs to that volume. since we disabled oplock the timeouts vanished. however, I will suggest your idea to my colleague who had that problem and he might give it a go as well. > The 2.6.32 kernel you're using also doesn't support async writes, unless the debian maintainers backported that work, which they don't typically do. If you move to a newer kernel you may get better performance as well... -- Jeff Layton <jlayton@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-cifs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
