All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Steigerwald <Martin@lichtvoll.de>
To: linux-btrfs@vger.kernel.org
Cc: Alexander Block <ablock84@googlemail.com>
Subject: Re: [PATCH 0/5] introduce btrfs filesystem property command
Date: Thu, 28 Jun 2012 15:08:05 +0200	[thread overview]
Message-ID: <201206281508.05594.Martin@lichtvoll.de> (raw)
In-Reply-To: <1340572808-30281-1-git-send-email-ablock84@googlemail.com>

Am Sonntag, 24. Juni 2012 schrieb Alexander Block:
> This patchset introduces the btrfs filesystem property command. It is
> the result of a discussion we had on IRC. I tried to make the
> properties interface as generic and extensible as possible. Comments
> are welcome.
> 
> Currently the command looks like this:
> btrfs fi prop /path/to/object [name[=value]]
> 
> Some people may prefer other forms. For example I got suggestions for
> these forms:
> btrfs set/get /path/to/object [name [value]]
> btrfs prop /pach/to/object [name[=value]] (and also without the =)
> 
> I'm open to more suggestions and a discussion on this. I'm definitely

I wonder about a way to find out directly

1) size of node and leaf metadata blocks

2) whether inode cache is active

3) whether space cache is active

Would also be nice to be able to set this. I do not know whether this is 
possible re 1 during a balance for example. Re 2 and 3 it would be nice to 
be able to skip the mount options in /etc/fstab. AFAIK space cache is 
permanent anyway, but inode cache isn´t or vice versa.

Either way I find the current way BTRFS handles options via mount options a 
bit confusion.

I´d like some way to set attributes / flags permanently like in Ext4 via 
tune2fs or xfs_admin.

Thanks,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7

      parent reply	other threads:[~2012-06-28 13:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-24 21:20 [PATCH 0/5] introduce btrfs filesystem property command Alexander Block
2012-06-24 21:20 ` [PATCH 1/5] Btrfs-progs: add BTRFS_IOC_SUBVOL_GET/SETFLAGS to ioctl.h Alexander Block
2012-06-24 21:20 ` [PATCH 2/5] Btrfs-progs: move skip_prefix and prefixcmp to utils.c Alexander Block
2012-06-24 21:20 ` [PATCH 3/5] Btrfs-progs: let get_label return the label instead of of printing it Alexander Block
2012-06-24 21:20 ` [PATCH 4/5] Btrfs-progs: make filesystem_cmd_group non const Alexander Block
2012-06-24 22:14   ` Alexander Block
2012-06-24 21:20 ` [PATCH 5/5] Btrfs-progs: introduce btrfs filesystem property command Alexander Block
2012-06-27  2:25 ` [PATCH 0/5] " Liu Bo
2012-06-27 11:08   ` Alexander Block
2012-06-28 13:08 ` Martin Steigerwald [this message]

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=201206281508.05594.Martin@lichtvoll.de \
    --to=martin@lichtvoll.de \
    --cc=ablock84@googlemail.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 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.