linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sander <sander@humilis.net>
To: Austin S Hemmelgarn <ahferroin7@gmail.com>
Cc: Aastha Mehta <aasthakm@gmail.com>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: question regarding caching
Date: Fri, 3 Jan 2014 09:39:50 +0100	[thread overview]
Message-ID: <20140103083950.GB29349@panda> (raw)
In-Reply-To: <52C30C8E.9020103@gmail.com>

Austin S Hemmelgarn wrote (ao):
> The data is probably still cached in the block layer, so after
> unmounting, you could try 'echo 1 > /proc/sys/vm/drop_caches' before
> mounting again, but make sure to run sync right before doing that,
> otherwise you might lose data.

Lose data? Where you get this from?

	Sander

  reply	other threads:[~2014-01-03  8:39 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
2013-12-31 17:02   ` Alex Elsayed
2013-12-31 18:27 ` Austin S Hemmelgarn
2014-01-03  8:39   ` Sander [this message]
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=20140103083950.GB29349@panda \
    --to=sander@humilis.net \
    --cc=aasthakm@gmail.com \
    --cc=ahferroin7@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).