From: Kai Krakow <hurikhan77+btrfs@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: btrfs mount flags
Date: Sat, 14 Apr 2012 17:17:30 +0200 [thread overview]
Message-ID: <t0ho59-rjd.ln1@hurikhan.ath.cx> (raw)
In-Reply-To: pan.2012.04.13.17.42.32@cox.net
Duncan <1i5t5.duncan@cox.net> schrieb:
> Kai Krakow posted on Fri, 13 Apr 2012 17:50:45 +0200 as excerpted:
>
>> Is there any documentation about btrfs mount flags wrt:
>> [...]
>
> AFAIK the best documentation is the wiki, which you didn't mention, tho
> you mentioned google. It's also possible that you found the old/outdated
> (because it's read-only after the kernel.org breakin some months ago) wiki
> on btrfs.wiki.kernel.org, but not the current (but possibly temporary)
> one linked below.
>
> So the wiki is where I'd go first. Questions you have after that, ask
> here, and preferably update the wiki with the answers you get, as well.
>
> http://btrfs.ipv5.de/index.php?title=Main_Page
This looks good but I think there's room for improvement. Are there any
mount options which apply to a subvolume only?
And while I see space_cache having the "permanent" annotation in its
description, I see something similar missing for e.g. the inode_cache, ssd,
etc. descriptions. Something that says "not permanent, must be given each
time".
Anyone willing to eloberate on this? I'd offer to contribute this to the
wiki.
Thanks,
Kai
next prev parent reply other threads:[~2012-04-14 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 15:50 btrfs mount flags Kai Krakow
2012-04-13 17:42 ` Duncan
2012-04-14 15:17 ` Kai Krakow [this message]
2012-04-15 5:53 ` Duncan
2012-04-15 10:00 ` Martin Steigerwald
2012-04-16 3:20 ` Duncan
2012-04-13 22:05 ` Martin Steigerwald
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=t0ho59-rjd.ln1@hurikhan.ath.cx \
--to=hurikhan77+btrfs@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).