From: David Sterba <dsterba@suse.cz>
To: waxhead <waxhead@dirtcellar.net>
Cc: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: Why do we need these mount options?
Date: Fri, 15 Jan 2021 16:29:54 +0100 [thread overview]
Message-ID: <20210115152954.GH6430@twin.jikos.cz> (raw)
In-Reply-To: <e9257bae-b744-42a7-1fc3-39b3ea676898@dirtcellar.net>
On Fri, Jan 15, 2021 at 01:02:12AM +0100, waxhead wrote:
> > I don't think the per-subvolume storage options were ever tracked on
> > wiki, the closest match is per-subvolume mount options that's still
> > there
> >
> > https://btrfs.wiki.kernel.org/index.php/Project_ideas#Per-subvolume_mount_options
> >
> Well how about this from our friends archive.org ?
> http://web.archive.org/web/20200117205248/https://btrfs.wiki.kernel.org/index.php/Main_Page
>
> Here it clearly states that object level mirroring and striping is
> planned. Maybe I misinterpret this , but I understand this as (amongst
> other things) configurable storage profiles per subvolume.
I see. The list on the main page is supposed to list features that we could
promise to be implemented "soon". For all the ideas there's the specific
project page wher it does not matter too much when it will implemented, it's
kind of a pool.
In the wiki edit that removed the object-level storage I also removed
(https://btrfs.wiki.kernel.org/index.php?title=Main_Page&diff=prev&oldid=33190)
* Online filesystem check
* Object-level mirroring and striping
* In-band deduplication (happens during writes)
* Hot data tracking and moving to faster devices (or provided on the generic VFS layer)
For each of the task there's nobody working on that, to my knowledge,
though there was some interest and maybe RFC patches in the past.
The object-level storage idea/task can be added to the Project_ideas
page, so it's not lost.
next prev parent reply other threads:[~2021-01-15 15:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 2:12 Why do we need these mount options? waxhead
2021-01-14 16:37 ` David Sterba
2021-01-15 0:02 ` waxhead
2021-01-15 15:29 ` David Sterba [this message]
2021-01-16 1:47 ` waxhead
2021-01-15 3:54 ` Zygo Blaxell
2021-01-15 9:32 ` waxhead
2021-01-16 0:42 ` Zygo Blaxell
2021-01-16 1:57 ` waxhead
2021-01-16 3:51 ` Zygo Blaxell
2021-01-16 7:39 ` Andrei Borzenkov
2021-01-16 15:19 ` Adam Borowski
2021-01-16 17:21 ` Andrei Borzenkov
2021-01-16 20:01 ` Zygo Blaxell
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=20210115152954.GH6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=waxhead@dirtcellar.net \
/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