From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Fwd: [suggestion] Add verbose notification about inode-cache rebuild to kernel log
Date: Tue, 13 May 2014 04:55:32 +0000 (UTC) [thread overview]
Message-ID: <pan$32b2f$6c928539$a433bdd$26be4562@cox.net> (raw)
In-Reply-To: 5371105C.5030306@inwind.it
Goffredo Baroncelli posted on Mon, 12 May 2014 20:18:04 +0200 as
excerpted:
> Finally I have a question: it is possible to disable inode_cache ? what
> means the flag "noinode_cache" ? It means disable the inode cache at
> all, or only avoid to store on disk the inode cache ?
Unlike space_cache, which is enabled by default these days, inode_cache
must be specifically enabled every time it is to be used. So simply not
including the inode_cache mount option when doing the original mount
means it's disabled.
Meanwhile, the noinode_cache flag is simply one of the mount-option
negators, to allow turning off a mount option on an existing mount when
it is remounted, to avoid having to fully umount and do a fresh mount, to
deactivate the option.
So simply don't include inode_cache when doing the original mount to
disable it, or if for whatever reason it's enabled and you want to
disable it on a remount, use -o remount,noinode_cache for the remount,
and it'll disable inode_cache if the filesystem was already mounted with
it enabled.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2014-05-13 4:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACHxQ2tAU15z_pUEGBuGqYFR9n_fH9BeyA8=jYryRrb3H=zCYA@mail.gmail.com>
2014-05-08 14:22 ` Fwd: [suggestion] Add verbose notification about inode-cache rebuild to kernel log Tomáš Pružina
2014-05-09 14:51 ` David Sterba
2014-05-09 18:12 ` Goffredo Baroncelli
2014-05-12 14:39 ` David Sterba
2014-05-12 18:18 ` Goffredo Baroncelli
2014-05-13 4:55 ` Duncan [this message]
2014-05-13 14:22 ` David Sterba
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='pan$32b2f$6c928539$a433bdd$26be4562@cox.net' \
--to=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.