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

Live USB filesystem is too small #406

Open
samsheff opened this issue Oct 12, 2024 · 9 comments
Open

Live USB filesystem is too small #406

samsheff opened this issue Oct 12, 2024 · 9 comments

Comments

@samsheff
Copy link

I have been using penguins eggs to make a live usb stick for several months, and recently after updating, when I boot the usb, the os only has about 150mb of free space on the in-memory filesystem. It makes it impossible to use the live OS because not everything can be moved to a mount point, and some things will still write to the ramdisk. And once it runs out of space I need to reboot.

Did something update that made the live disk smaller? I havent been able to figure out what it is if I broke something on my end, but this looks like some configuration change in eggs.

Any idea what this could be?

@samsheff
Copy link
Author

One more piece of info - The OS im building on is Arch.

@pieroproietti
Copy link
Owner

pieroproietti commented Oct 12, 2024

The time you tell is long enought to try to imagine the problem...

  • first passing from 9 to 10 I started to use nodejs from the distro in Debian, Arch remain more or less the same, but share the same codebase;
  • lately, becouse I saw with openSuSE syslinux 6.04 original work - for me - better than the original, I investigate for the others distro. This end to put syslinux inside eggs and remove the syslinux dependecies:
  • another idea, the way actually we compress the disk, using zstd in the place of xz. You can try to set the option --max, to work in the old style;
  • in same places there is a parameter to decide the size of the in memory system... I must to look don't remember where I saw, but perhaps on archiso disk.

@samsheff
Copy link
Author

Let me try --max and see if that helps. If not, maybe I can help with the memory size parameter. Im sure its configurable, just need to find where.

If its the solution and I can find it I will open a PR.

@samsheff
Copy link
Author

samsheff commented Oct 12, 2024

Just checked my build command, it already uses --max. So thats not the solution.

What part of the code creates the RAM disk? I can look into it

@pieroproietti
Copy link
Owner

case 'archlinux': {

@yonacwy
Copy link

yonacwy commented Oct 15, 2024

A possible work around is to use Ventoy with Persistence Plugin

https://ventoy.net/en/plugin_persistence.html

@samsheff
Copy link
Author

samsheff commented Oct 18, 2024

Ventoy looks interesting, but I would much rather use this project if I can. Ive been using it for almost a year, and this bug was only added recently, in the last month or so. What version can I roll back to where Arch would be better supported?

@samsheff
Copy link
Author

Hey @pieroproietti

What is the name of the command that creates the ramdisk? Tried Ventoy with the persistence plugin, still only shows 150mb of space. How can I help you get this fixed?

@samsheff
Copy link
Author

samsheff commented Nov 9, 2024

@pieroproietti The suggestion in the stack overflow solved it: https://superuser.com/q/753134

By adding cow_spacesize=2G to the grub boot options it will increase the size. How can we add this to the build? I will submit a PR.

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

3 participants