Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Satoru Takeuchi <takeuchi_satoru@jp.fujitsu.com>
To: Brendan Hide <brendan@swiftspirit.co.za>,
	MegaBrutal <megabrutal@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: BTRFS equivalent for tune2fs?
Date: Tue, 2 Dec 2014 17:11:40 +0900	[thread overview]
Message-ID: <547D743C.7010905@jp.fujitsu.com> (raw)
In-Reply-To: <547D6CA3.7070808@swiftspirit.co.za>

Hi,

(2014/12/02 16:39), Brendan Hide wrote:
> On 2014/12/02 09:31, Brendan Hide wrote:
>> On 2014/12/02 07:54, MegaBrutal wrote:
>>> Hi all,
>>>
>>> I know there is a btrfstune, but it doesn't provide all the
>>> functionality I'm thinking of.
>>>
>>> For ext2/3/4 file systems I can get a bunch of useful data with
>>> "tune2fs -l". How can I retrieve the same type of information about a
>>> BTRFS file system? (E.g., last mount time, last checked time, blocks
>>> reserved for superuser*, etc.)
>>>
>>> * Anyway, does BTRFS even have an option to reserve X% for the superuser?
>> Btrfs does not yet have this option. I'm certain that specific feature is in mind for the future however.
>>
>> As regards other equivalents, the same/similar answer applies. There simply aren't a lot of tuneables available "right now".
>>
> Almost forgot about this: btrfs property (get|set)
>
> Again, there are a lot of features still to be added.
>

Just FYI. There are some description about this topic.

https://btrfs.wiki.kernel.org/index.php/Project_ideas#Set_mount_options_permanently
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Extend_btrfstune_to_be_able_to_tune_more_parameters
https://btrfs.wiki.kernel.org/index.php/Project_ideas#Filesystem_object_properties

Thanks,
Satoru


  reply	other threads:[~2014-12-02  8:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02  5:54 BTRFS equivalent for tune2fs? MegaBrutal
2014-12-02  7:31 ` Brendan Hide
2014-12-02  7:39   ` Brendan Hide
2014-12-02  8:11     ` Satoru Takeuchi [this message]
2014-12-02  8:20 ` Duncan

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=547D743C.7010905@jp.fujitsu.com \
    --to=takeuchi_satoru@jp.fujitsu.com \
    --cc=brendan@swiftspirit.co.za \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=megabrutal@gmail.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