From: Mike Fedyk <mfedyk@mikefedyk.com>
To: Goffredo Baroncelli <kreijack@gmail.com>
Cc: Chris Mason <chris.mason@oracle.com>,
linux-btrfs@vger.kernel.org, Thomas Kupper <thomas@kupper.org>,
"Dipl.-Ing. Michael Niederle" <mniederle@gmx.at>,
rk <rkasl@computer.org>
Subject: Re: [PATCH 0/2 V2] btrfs: a new tool to manage a btrfs filesystem
Date: Thu, 18 Feb 2010 12:46:56 -0800 [thread overview]
Message-ID: <93cdabd21002181246g7a46a767m8170859ce85eb0ab@mail.gmail.com> (raw)
In-Reply-To: <201002182100.00624.kreijack@libero.it>
On Thu, Feb 18, 2010 at 11:59 AM, Goffredo Baroncelli
<kreijack@gmail.com> wrote:
> On Thursday 18 February 2010, Chris Mason wrote:
>> I do like the subcommand method, more details below.
>>
>
> I try to summarise your suggestions. But there are some cases not to =
clear for
> me.
> I grouped the commands in three categories: subvolume, devices, and
> filesystem.
>
>
> devices =C2=A0 =C2=A0 =C2=A0 =C2=A0 scan
> devices =C2=A0 =C2=A0 =C2=A0 =C2=A0 show
> devices =C2=A0 =C2=A0 =C2=A0 =C2=A0 balance
> devices =C2=A0 =C2=A0 =C2=A0 =C2=A0 add
> devices =C2=A0 =C2=A0 =C2=A0 =C2=A0 remove
>
> subvolume =C2=A0 =C2=A0 =C2=A0 snapshot
> subvolume =C2=A0 =C2=A0 =C2=A0 delete
> subvolume =C2=A0 =C2=A0 =C2=A0 create
> [subvolume =C2=A0 =C2=A0 =C2=A0list]
>
> filesystem =C2=A0 =C2=A0 =C2=A0resize
> [filesystem =C2=A0 =C2=A0 label]
>
> ??? =C2=A0 =C2=A0 defrag
> ??? =C2=A0 =C2=A0 sync
>
>
>
> For the first two categories both Chris and Mike agreed; but IMHO the=
re are
> some commands that don't fit nor in devices, nor subvolume, like resi=
ze (we
> resize a filesystem) and label (not available now).
>
A btrfs filesystem can span multiple devices. Resize resizes how big
of a chunk of one device btrfs uses. This would be used by
partitioning programs for instance. zfs uses the term "pool" instead
of filesystem to solve this ambiguous use of the term "filesystem"
since btrfs and zfs break people's existing definition of the word
"filesystem".
> I don't know how classify defrag (per file / directory level ?) and s=
ync
> (filesystem ?)
It turns out that defrag is per file, which seems most cumbersome.
Maybe since it will probably eventually work against several types of
objects we could have:
btrfs defrag file <file>
btrfs defrag directory <directory>
btrfs defrag subvol <subvol>
btrfs defrag pool <pool>
>
> An option is to consider commands without classification. For example=
s:
>
> $ btrfs subvolume create [path/]<subvolname>
> $ btrfs sync <path>
> $ btrfs defrag <file>
Maybe if the btrfs developers are agreeable, we could do this as well:
btrfs sync file <file>
btrfs sync directory <directory>
btrfs sync subvol <subvol>
btrfs sync pool <pool>
I'm not sure how useful syncing the pool or a directory tree would be,
but I'll include it here for further discussion.
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-02-18 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 20:02 [PATCH 0/2 V2] btrfs: a new tool to manage a btrfs filesystem Goffredo Baroncelli
2010-02-17 20:48 ` Andreas Philipp
2010-02-17 21:00 ` Goffredo Baroncelli
2010-02-17 23:35 ` Mike Fedyk
2010-02-18 9:45 ` Piavlo
2010-02-18 16:58 ` Chris Mason
2010-02-18 17:58 ` Mike Fedyk
2010-02-18 18:20 ` Thomas Kupper
2010-02-18 19:59 ` Goffredo Baroncelli
2010-02-18 20:46 ` Mike Fedyk [this message]
2010-02-18 20:58 ` Chris Mason
2010-02-18 21:04 ` Goffredo Baroncelli
2010-02-18 21:39 ` Mike Fedyk
2010-02-18 21:25 ` Tomasz Torcz
2010-02-18 21:00 ` Goffredo Baroncelli
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=93cdabd21002181246g7a46a767m8170859ce85eb0ab@mail.gmail.com \
--to=mfedyk@mikefedyk.com \
--cc=chris.mason@oracle.com \
--cc=kreijack@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=mniederle@gmx.at \
--cc=rkasl@computer.org \
--cc=thomas@kupper.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