From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Overfull Filesystems how to solve?
Date: Sun, 19 Jan 2020 18:14:21 +0000 [thread overview]
Message-ID: <3F56072B-E8DF-47F1-AF01-ABB69C08946B@ipfire.org> (raw)
In-Reply-To: <70bd4343d85cf136b677fc6d23370316a071e22d.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1700 bytes --]
Hello,
> On 18 Jan 2020, at 09:57, Jonatan Schlag <jonatan.schlag(a)ipfire.org> wrote:
>
> Hi,
>
> Daniel encountered the problem that his root partition was written full
> because of the qemu addon being too big (200 MB). See bug #12268 for
> details.
>
> So he suggested moving the path /usr/share/qemu to /var. I do not
> really like this solution as there are standards how the filesystem
> hierarchy works under Linux.
That was my suggestion for a quick fix.
However, looking at the files in /usr/share/qemu, I am not sure what we actually need. Can we not just delete some and we are fine again?
https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=config/rootfiles/packages/qemu;h=e5c0cd18953c3de3121b43f40af277f29016b7f7;hb=HEAD
The current root file lists things like EFI ROMs for ARM which we probably do not support or need. BIOS ROMs for SPARC which we 100% do not support. If we just do not ship those files, this problem can be solved without moving the files.
> Furthermore, as the systems become bigger (eg. moving python3 to the
> core) this problem will become more relevant to us. So I would like to
> start a discussion on how to solve this. Moving things to /var can only
> be a temporary solution. Should we force a reinstallation, which solves
> the root of the problem?
Yes, we have a script to cleanup what we can. We still need to make sure that the distribution is as small as possible and we have not been spending too much time on this recently. Everything becomes bigger and bigger, but I would suggest that we try to support the systems with the 2GB root partition for as long as we can.
Best,
-Michael
>
> Jonatan
>
prev parent reply other threads:[~2020-01-19 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 9:57 Jonatan Schlag
2020-01-18 10:30 ` Tapani Tarvainen
2020-01-19 18:16 ` Michael Tremer
2020-01-20 4:17 ` Tapani Tarvainen
2020-01-20 10:38 ` Michael Tremer
2020-01-20 11:39 ` Tapani Tarvainen
2020-01-20 11:49 ` Michael Tremer
2020-01-19 18:14 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3F56072B-E8DF-47F1-AF01-ABB69C08946B@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox