From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: question regarding caching
Date: Tue, 31 Dec 2013 04:15:18 +0100 [thread overview]
Message-ID: <6fp9pa-9un.ln1@hurikhan77.spdns.de> (raw)
In-Reply-To: CAEx9m44ZiJLqTO1_G_rVfn+csD7_pOguEdiAjsvr3uPzna+mFA@mail.gmail.com
Aastha Mehta <aasthakm@gmail.com> schrieb:
> Rather than a local disk, I have a remote device to which my IO
> requests are sent and from which the data is fetched. I need certain
> data to be fetched from the remote device after a remount. But somehow
> I do not see any request appearing at the device. I even tried to do
> drop_caches after remounting the file system, but that does not seem
> to help.
Maybe you or your distribution deployed cachefilesd and uses it for the
remote fs?
HTH
Kai
next prev parent reply other threads:[~2013-12-31 3:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 2:24 question regarding caching Aastha Mehta
2013-12-31 3:15 ` Kai Krakow [this message]
2013-12-31 17:02 ` Alex Elsayed
2013-12-31 18:27 ` Austin S Hemmelgarn
2014-01-03 8:39 ` Sander
2014-01-03 12:12 ` Austin S Hemmelgarn
2014-01-07 14:50 ` Aastha Mehta
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fp9pa-9un.ln1@hurikhan77.spdns.de \
--to=hurikhan77+btrfs@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).