From: Jesse Gibbons <jgibbons2357@gmail.com>
To: 37293@debbugs.gnu.org
Subject: bug#37293: image-size is meaningless when generating ext4 images
Date: Mon, 02 Sep 2019 20:48:27 -0600 [thread overview]
Message-ID: <46bad7b539bd9a7ce04e2dcbfad336a00fdc03f0.camel@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 785 bytes --]
The manual says in multiple places the --image-size option should set
the size of a generated ext4 disk image.
I start with a minimalist configuration (attached: minimal.scm) and run
build-minimal-os.sh (attached). I start virt-manager and make a new
virtual machine with the generated img as the disk image. virt-manager
says the disk image is 20G. So far so good...
I run "guix pull" and it fails because it runs out of disk space.
I run df -h and see the partition mounted on / has only 494M.
available.
I run cfdisk /dev/sda and see the first partition is 20G.
I have added quite a bit to the minimal os, but have not changed the
behavior. The attached minimal.scm is my most recent version.
Does anyone know of a way to expand the main partition's size?
Thanks,
--
-Jesse
[-- Attachment #2: build-minimal-os.sh --]
[-- Type: application/x-shellscript, Size: 210 bytes --]
[-- Attachment #3: minimal.scm --]
[-- Type: text/x-scheme, Size: 542 bytes --]
(use-modules (gnu)
(gnu services networking))
(operating-system
(bootloader
(bootloader-configuration
(bootloader grub-bootloader)))
(host-name "minimal-os")
(file-systems (cons*
(file-system
(type "ext4")
(mount-point "/")
(device "/dev/sda1")
(needed-for-boot? #t)
(create-mount-point? #t))
%base-file-systems))
(packages (cons*
%base-packages))
(services
(cons*
(service network-manager-service-type)
(service wpa-supplicant-service-type)
%base-services))
(timezone "America/Denver"))
next reply other threads:[~2019-09-03 2:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 2:48 Jesse Gibbons [this message]
2019-09-03 3:04 ` bug#37293: image-size is meaningless when generating ext4 images Jesse Gibbons
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=46bad7b539bd9a7ce04e2dcbfad336a00fdc03f0.camel@gmail.com \
--to=jgibbons2357@gmail.com \
--cc=37293@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.