>>> One thing is sure : ext4 online defragmentation can break lilo (in case
>>> the /boot directory is defragmented, which is unlikely to ha, but could
>>> theoretically happen) ...
>>>
>>> Lilo access the kernel by block, not by extent :)
>>>
>> I know what you are talking about, but is there any evidence for this? I mean:
>> Was it discussed before? AFAIK Slackware uses ext4 as default and Lilo?
>>
> Because the online defrag code is not yet in the kernel (was expected
> in 2.6.29, so should come soon), and maybe because Pat Volkerding
> can't think about everything :)
And because LILO is considered deprecated , so devs have more to say
about backporting ext4 support from grub2 to grub1 than caring about LILO ;)
Doesn't seem like a huge issue to me. If you're going to defrag a
partition with your kernel, run LILO afterwards (and hope the power
doesn't fail during defrag). Better yet, don't defrag a partition with
/boot.
I don't think it's a huge issue either. But maybe we should make xfs the default filesystem anyway? I'm still using it everywhere and in every new installation I make.
If you're going to defrag a
partition with your kernel
I guess I have to run a program to defrag the partition? So it should be no problem to use ext4. i'm using ext4 on my root partition (convertet from ext3) since some time now.