From: Ferry Toth <ftoth@telfort.nl>
To: linux-btrfs@vger.kernel.org
Subject: Re: unsolvable technical issues?
Date: Sun, 24 Jun 2018 17:06 +0200 [thread overview]
Message-ID: <pgobsl$eh$1@blaine.gmane.org> (raw)
In-Reply-To: 7309fa6b-d892-cff9-dcdf-639070ea073e@dirtcellar.net
waxhead wrote:
> Jukka Larja wrote:
>> waxhead wrote 24.6.2018 klo 1.01:
>>> Nikolay Borisov wrote:
>>>>
>>>> On 22.06.2018 02:13, waxhead wrote:
>>>>> According to this:
>>>>>
>>>>> https://stratis-storage.github.io/StratisSoftwareDesign.pdf
>>>>> Page 4 , section 1.2
>>>>>
>>>>> It claims that BTRFS still have significant technical issues that may
>>>>> never be resolved.
>>>>> Could someone shed some light on exactly what these technical issues
>>>>> might be?! What are BTRFS biggest technical problems?
>>>>
>>>> That's a question that needs to be directed at the author of the
>>>> statement.
>>>>
>>> I think not, and here's why: I am asking the BTRFS developers a
>>> general question , with some basis as to why I became curious. The
>>> question is simply what (if any) are the biggest technical issues in
>>> BTRFS because one must expect that if anyone is going to give me a
>>> credible answer it must be the people that hack on BTRFS and
>>> understand what they are working on and not the stratis guys. It would
>>> surprise me if they knew better than the BTRFS devs.
>>
>> I think the problem with that question is that it is too general.
>> Duncan's post already highlights several things that could be a
>> significant problem for some user while being non-issue for most.
>> Without more specific problem description, best you can hope for is
>> speculation on things that Btrfs currently does badly.
>>
>> -Jukka Larja
>
> Well, I still don't agree (apparently I am starting to become
> difficult). There is a "roadmap" on the BTRFS wiki that describes
> features implemented and feature planned for example. Naturally people
> are working on improvements to existing features and prep-work for new
> features. If some of this work is not moving ahead due to design issues
> it sounds likely that someone would know about it by now.
This one doesn't seem to be moving ahead, while it seems like a very
promising one: Hot data tracking and moving to faster devices (or provided
on the generic VFS layer)
It would be really fantastic to just add a ssd to a pool of hdd's and have
fsync sensitive stuff run normally (dpkg on raid10 with 50 snapshots
currently can take hours to do a few minute job)
>
> --
> 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:[~2018-06-24 15:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 23:13 unsolvable technical issues? waxhead
2018-06-22 2:39 ` Chris Murphy
2018-06-27 18:50 ` waxhead
2018-06-28 14:46 ` Adam Borowski
2018-06-22 5:48 ` Nikolay Borisov
2018-06-23 22:01 ` waxhead
2018-06-24 3:55 ` Jukka Larja
2018-06-24 8:41 ` waxhead
2018-06-24 15:06 ` Ferry Toth [this message]
2018-06-23 5:11 ` Duncan
2018-06-24 20:22 ` Goffredo Baroncelli
2018-06-25 11:26 ` Austin S. Hemmelgarn
2018-06-30 3:22 ` Duncan
2018-06-30 5:32 ` Andrei Borzenkov
2018-07-02 11:49 ` Austin S. Hemmelgarn
2018-07-03 7:35 ` Duncan
2018-07-03 11:54 ` Austin S. Hemmelgarn
2018-07-02 11:44 ` Austin S. Hemmelgarn
2018-06-25 14:20 ` David Sterba
2018-06-25 13:36 ` David Sterba
2018-06-25 16:43 ` waxhead
2018-06-25 16:54 ` Hugo Mills
2018-06-30 3:59 ` 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='pgobsl$eh$1@blaine.gmane.org' \
--to=ftoth@telfort.nl \
--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.