Bug 500175 - Should be able to set the init_table=0 option
Summary: Should be able to set the init_table=0 option
Status: REPORTED
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-16 09:56 UTC by deco33000
Modified: 2025-02-18 05:27 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description deco33000 2025-02-16 09:56:17 UTC 
Hi,
Right now it's impossible to achieve the equivalent of mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 <partition> in the gui.

Could we add these options when creating the partition ? It avoids the ext4 lazy initialization of the disk.

Thanks
Comment 1 Andrius Štikonas 2025-02-16 11:29:14 UTC 
Hmm, right now kpmcore library supports optional "Features" and we have some of them https://invent.kde.org/system/kpmcore/-/blob/master/src/fs/ext2.cpp?ref_type=heads#L53

lazy_itable_init and lazy_journal_init are not there but we could easily add them.

The problem for now is that it " File system Features" not exposed in GUI in partitionmanager itself.
Comment 2 Andrius Štikonas 2025-02-18 00:02:40 UTC 
I've added those two features to ext2.cpp though for now that is not exposed yet in partition manager UI.
Comment 3 deco33000 2025-02-18 05:27:15 UTC 
(In reply to Andrius Štikonas from comment #2)
> I've added those two features to ext2.cpp though for now that is not exposed
> yet in partition manager UI.

That's great! Thanks 👍