Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

opk update issues slowdowns #6

Open
jutleys opened this issue Dec 3, 2019 · 4 comments
Open

opk update issues slowdowns #6

jutleys opened this issue Dec 3, 2019 · 4 comments
Assignees

Comments

@jutleys
Copy link
Collaborator

jutleys commented Dec 3, 2019

okay so i just flashed v1.5 base again on a 32gb card for internal but did not do no update and picodrive is working fine and no slowdows so its the opk file that is doing something
I will stick to v1.5 for now

@rxbrad
Copy link

rxbrad commented Dec 3, 2019

Hey, @Ninoh-FOX... passing this on from Discord. Not sure if it's related or not...

podulatorToday at 8:07 AM
i think it's really unlikely to be the external sdcard, tbh
i think it's more lilely to be lazy initialization of ext4
or something like that
hence it dissapears after a while
are you creating ext4 with the disable lazy init flags???
When an ext4 file system is created, it will by default use lazy inode table initialisation and lazy journal initialisation. While this feature significantly speeds up file system creation, the kernel will be forced to perform full initialisation afterwards, in the background. As a result, the disk that holds the file system will appear to be constantly busy, even when you do not use it, until its initialisation gets completed.

To disable this behaviour, you can turn lazy initialisation off when you create the file system, by specifying the extended options lazy_itable_init and lazy_journal_init, and setting them to 0:

mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0 DEVICE
it's why it formats so fast, but you pay later this price

@npaladin2000
Copy link
Contributor

Ok, let's update the next build to turn off lazy initialization. people will have to wait longer for that first boot, but they won't see slowdowns.

@Ninoh-FOX
Copy link
Contributor

Then, you are saiding that we need format the ext4 in the first boot?

@npaladin2000
Copy link
Contributor

When we do the format, we need to change the command to be this:

mkfs.ext4 -E lazy_itable_init=0,lazy_journal_init=0

@rxbrad rxbrad removed their assignment Oct 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants