[systemd-devel] [PATCH 2/2] fsck: Add support for EFI variable based fsck indication

"Jóhann B. Guðmundsson" johannbg at gmail.com
Thu Apr 9 06:02:06 PDT 2015



On 04/09/2015 11:04 AM, Lennart Poettering wrote:
> On Thu, 09.04.15 10:51, Jóhann B. Guðmundsson (johannbg at gmail.com) wrote:
>
>> My above questions where directed directly at Lennart since you cannot know
>> if Lennart's assumption which he bases his decisions on are
>> premature,correct, wrong or misguided until you know what those assumptions
>> are.
>>
>> Once those assumptions are known one can compare it with ones own as well as
>> facts and have a higher level discussion about what makes suitable upstreams
>> defaults and why.
> We generally follow the rule: we develop for the future, not for the
> past. A file system like ext234 is clearly not the future,

A filesystem like ext is being actively developed,maintained and new 
features being added to it.

While filesystems are being supported and actively developed,maintained 
and new features added to them you hardly can consider them not part of 
the future now can you despite their "shortcomings" compared to eachother.

>   the concept
> of requiring fsck on dirty is just broken with today's large
> disks. Now, of course we will continue to support ext234, and fsck and
> stuff. However, we will not add *new* features to this scheme, since
> the whole idea of having something like this at all is yesterday's
> idea.
>
> Sure, btrfs is not particularly stable yet, but that hardly matters,
> as not even xfs requires such an fsck scheme anymore!

BTRFS relevance matters no more or less then the rest of them ( despite 
it being new or feature rich ) since it will become obsolete at the same 
time as the rest of the existing filesystem since they will all be 
replaced by a filesystem that will be tailored to a new technology like 
pervasive persistent memory or memristors or something else.

That new technology can be expected to emerge in the next 5 - 10 years ( 
which is around the same amount of time BTRFS becomes widely accepted 
and industry wide default that is if it ever manage to become that ) 
with another 10 years of obsolete/deprecation time for existing 
technology and their filesystems

>
> We will not add completely new features to the old stuff,

How can you come to that conclusion when our largest consumer base 
across the three categories uses ext4 and undoubtedly will want systemd 
native features around for example [1] implemented?

>   if we
> already know *now* that the old stuff is a dead end,

How do you know that when a) existing filesystem will be very much alive 
for atleast 10 - 20 years more and b) the entire IT industry has 
absolutely no idea where it is heading, the technology evolution or even 
the market will take it?

>   and things are
> already good enough in the area, and the future will make the whole
> problem go away.

Since we are on the subject of future problems and predictions could you 
give me 5 random numbers between 1 and 40, 6 numbers between 1 and 48 
and finally 5 numbers from 1 - 50 with two numbers from 1 - 10?

Thanks

JBG


More information about the systemd-devel mailing list