From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: strange 3.16.3 problem
Date: Tue, 21 Oct 2014 12:25:02 +0000 (UTC) [thread overview]
Message-ID: <pan$9526d$5656f77d$70922c1d$bcb849ce@cox.net> (raw)
In-Reply-To: 201410212113.30887.russell@coker.com.au
Russell Coker posted on Tue, 21 Oct 2014 21:13:29 +1100 as excerpted:
> I don't know what
> space_cache is about, is that something the kernel adds automatically?
Yes, space_cache is the default.
Apparently early in space_cache history you had to mount with space_cache
once, and the kernel would then detect the existence of the space-cache-
tree and always use the option after that.
But for quite some time now, over a year since I've not ever added that
to my mount options since I got the ssds and began using btrfs on them,
the kernel seems to enable it automatically from the first mount, unless
you specifically tell it not to.
Similarly for the ssd option, if the kernel detects that you are running
an ssd (I believe it checks the ata/scsi rotational media property, which
it should detect properly on raw hardware, but which can get lost if
btrfs is layered over top of lvm/mdraid/dmcrypt/etc), it'll automatically
enable the ssd mount option, which is exactly what it does here.
--
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-10-21 12:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-18 3:54 strange 3.16.3 problem Russell Coker
[not found] ` <CAHGunUkzXZ-ybUR_y3tHzGwtn_45gq8YQJyEqteBX3zqWzUakA@mail.gmail.com>
2014-10-18 10:29 ` Russell Coker
2014-10-18 13:33 ` Robert White
2014-10-18 23:41 ` Russell Coker
2014-10-19 5:37 ` Duncan
2014-10-19 10:19 ` Duncan
2014-10-20 17:37 ` Robert White
2014-10-20 20:21 ` Goffredo Baroncelli
2014-10-21 9:50 ` Duncan
2014-10-21 10:16 ` inode_cache " Roman Mamedov
2014-10-21 12:08 ` Duncan
2014-10-21 16:40 ` Goffredo Baroncelli
2014-10-22 7:12 ` Duncan
2014-10-19 10:46 ` Chris Samuel
2014-10-20 4:38 ` Duncan
2014-10-20 13:02 ` Zygo Blaxell
2014-10-20 13:19 ` Austin S Hemmelgarn
2014-10-21 10:13 ` Russell Coker
2014-10-21 10:42 ` Russell Coker
2014-10-21 15:23 ` strange 3.16.3 problem (er... never mind 8-) Robert White
2014-10-21 12:25 ` Duncan [this message]
2014-10-21 15:10 ` strange 3.16.3 problem Robert White
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$9526d$5656f77d$70922c1d$bcb849ce@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.