From: "Bryn M. Reeves" <breeves@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Page cache corruption when creating a snapshot
Date: Fri, 29 Feb 2008 19:10:18 +0000 [thread overview]
Message-ID: <47C8589A.7000309@redhat.com> (raw)
In-Reply-To: <1204312265.5850.7.camel@error-messages.mit.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greg Hudson wrote:
> Nope, that never made it go away. I'm not sure in what situations
> flushing write buffers would have any effect. If I had a way to throw
> away the read-only page cache and force a file reload from disk, I would
> expect that to eliminate the visible effect of the corruption; at the
> moment the only reliable way I know how to do that is to reboot. (I
> could churn the page cache into oblivion with a bazillion reads of
> different files, but I'd have no way of knowing when I had succeeded in
> reusing the corrupted cache page.)
You should be able to achieve that via the /proc/sys/vm/drop_caches sysctl:
Documentation/filesystems/proc.txt:
drop_caches
- -----------
Writing to this will cause the kernel to drop clean caches, dentries and
inodes from memory, causing that memory to become free.
To free pagecache:
echo 1 > /proc/sys/vm/drop_caches
To free dentries and inodes:
echo 2 > /proc/sys/vm/drop_caches
To free pagecache, dentries and inodes:
echo 3 > /proc/sys/vm/drop_caches
I guess a 1 would be a good first try & if that doesn't clear it, a 3
should force the entire inode to be re-read from disk.
Regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHyFia6YSQoMYUY94RArInAJ9dRVLCGYXcllL4RDz4pei4qGnUVQCg4LL1
d22/7jgF5zxsGnFPeCfpkwA=
=v99d
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-02-29 19:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 17:32 [linux-lvm] Page cache corruption when creating a snapshot ghudson
2008-02-29 18:31 ` Alasdair G Kergon
2008-02-29 19:11 ` Greg Hudson
2008-02-29 19:10 ` Bryn M. Reeves [this message]
2008-02-29 19:35 ` Greg Hudson
2008-02-29 20:14 ` Alasdair G Kergon
2008-03-04 23:57 ` Greg Hudson
2008-02-29 19:29 ` malahal
2008-02-29 19:53 ` Stuart D. Gathman
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=47C8589A.7000309@redhat.com \
--to=breeves@redhat.com \
--cc=linux-lvm@redhat.com \
/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).