From: Stefan Schantl <stefan.schantl@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Another Installer bug. xfs also not work...
Date: Wed, 05 Apr 2023 11:16:59 +0200 [thread overview]
Message-ID: <0dae858b93c454e519d1d08529739e42417f697e.camel@ipfire.org> (raw)
In-Reply-To: <29bf2fd3750394ae8199cfca0087e137@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1641 bytes --]
Hello Arne,
thanks for having a look on this and figuring out this limitation.
> At my tests about the grub install bug i found another that is there
> since core173.
>
> The install on xfs filesystem fails because xfsprogs refuse to create
> filesystems smaller than 300MB.
>
> https://bugzilla.ipfire.org/show_bug.cgi?id=13077
>
> there are three possible solutions:
> 1. add "-unsupported" flag to ignore this limit (not sure if this a
> good
> idea
> because we had strange out of space reports in the past also if
> no
> additional filles
> are installed.)
The will have their reasons, why the developers choosed 300 MB as
minimum file system size. Even there is this flag to bypass that, may
there as you already mentioned unexpected side effects.
>
> 2. enlarge boot partition
This would be a good idea, because the kernel size grows up from
release to release and if there are strange out of space problems in
the past would solve them too. Enlarge to for example 512MB would solve
both issues at once.
Are there any problems to expect for small installations on very
limited storage space (SD-cards etc.) ?
>
> 3. switch boot partition to ext4
This would bypass the XFS limitation but would result in a kind of
very fragmented filesystem types. EFI would be vfat, boot ext4 and if
selected the main file systemd XFS.
I would no expect any troubles when doing this but for me it tastes a
bit dizzy and unclean.
>
> Which is the best solution?
In theory there would be a fourth option:
4. Drop the option to select XFS during setup and force the usage of
ext4....
>
> Arne
Best regards,
-Stefan
next prev parent reply other threads:[~2023-04-05 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 6:48 Arne Fitzenreiter
2023-04-05 9:16 ` Stefan Schantl [this message]
2023-04-06 12:59 ` Michael Tremer
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=0dae858b93c454e519d1d08529739e42417f697e.camel@ipfire.org \
--to=stefan.schantl@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