mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Subject: Re: Drop cache has no effect?
Date: Tue, 29 Aug 2006 12:49:45 -0700	[thread overview]
Message-ID: <20060829124945.656dbaa1.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0608292117320.5502@yvahk01.tjqt.qr>

On Tue, 29 Aug 2006 21:21:25 +0200 (MEST)
Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:

> >> -rw-r--r--   1 jengelh users 37816633 2006-07-28 19:25 
> >> inkscape-0.44-2.guru.suse101.i686.rpm
> >> -rw-r--r--   1 jengelh users   297243 2006-08-15 01:13 
> >> vmware-any-any-update104.tar.gz
> >> 
> >> Remains 644.
> >
> >That would be a vfat problem - the changed permission bits weren't written
> >back to disk, so when you re-read them from disk (or, more likely, from
> >blockdev pagecache) they came back with the original values.
> 
> Yes, that's _intended_.
> 
> Fact:
> If you chmod 644 some files on vfat, then unmount and mount it again, they show
> up as 755 again. That is ok.
> 
> Observation:
> Dropping the cache does not imply the 644->755 change observed on unmount.
> 
> Conclusion:
> Caches not dropped.

Not all caches dropped.  It'd be silly to try that - see the implementation.

Running the same command a few more times might wring a couple more dentries
and inodes out of it.

  parent reply	other threads:[~2006-08-29 19:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-29 12:53 Jan Engelhardt
2006-08-29 18:00 ` Andrew Morton
2006-08-29 19:21   ` Jan Engelhardt
2006-08-29 19:36     ` /proc/net/tcp information drop Jörg Hoffmann
2006-08-29 19:49     ` Andrew Morton [this message]
2006-08-30  1:08   ` Drop cache has no effect? OGAWA Hirofumi
2006-08-30  1:39     ` Andrew Morton
2006-08-30  5:54       ` Jan Engelhardt
2006-08-30 16:31         ` OGAWA Hirofumi

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=20060829124945.656dbaa1.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@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

Powered by JetHome