unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Roel Janssen <roel@gnu.org>
Cc: help-guix@gnu.org
Subject: Re: Guix System ext4 index full
Date: Thu, 04 Jun 2020 15:05:14 +0200	[thread overview]
Message-ID: <87d06fc779.fsf@nckx> (raw)
In-Reply-To: <4f936a3561734d83665246592a54b21d9b612243.camel@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]

Roel,

Roel Janssen 写道:
> Thanks for the suggestion.  So I did:
> $ tune2fs -O large_dir /dev/sdd3
>
> .. and after a reboot I get booted into a GRUB resque shell.

Shart.  It seems that GRUB still[0] can't read ext4 file systems 
with features newer than 2017 :-/  I'll never recommend this again 
(I use it myself…).

The flag can't be cleared once set:

  $ sudo tune2fs -O ^large_dir img
  tune2fs 1.45.6 (20-Mar-2020)
  Clearing filesystem feature 'large_dir' not supported.

Your data's perfectly safe.  This is just a GRUB limitation.

> So.. do you have a suggestion for how I could boot into the Guix 
> system
> again?

I think realistic options are:

- Migrate to any other file system like btrfs, then use the live 
  USB's GRUB to bootstrap it using ‘configfile 
  (hdX,Y)/your/grub.cfg’ so you don't have to reinstall anything, 
  just copy.  This can even be done-in place[1], assuming you have 
  back-ups.

- Use a separate /boot partition if you want to keep using ext4 
  for large /gnus.  You'll have to manually copy each kernel & 
  friends to /boot but this can be automated in your system .scm.

> After booting from a live USB, I chrooted into the Guix system 
> and when
> running the following command, I get the following error:
> $ guix system reconfigure /etc/config.scm
> ...
> guix system: error: while setting up the build environment: 
> cannot
> pivot old root directory onto
> '/gnu/store/4q1vpidsawmfhmqdwy4mxvjc720jxcjm-slim-
> 1.3.6.drv.chroot/real-root': Invalid argument

I think your in-chroot guix is talking to the live system's 
guix-daemon.  Perhaps stopping the out-of-chroot daemon and 
starting a ‘guix-daemon --disable-chroot’ inside the chroot will 
work.

Kind regards,

T G-R

[0]: https://savannah.gnu.org/bugs/?56897
[1]: https://btrfs.wiki.kernel.org/index.php/Manpage/btrfs-convert

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2020-06-04 13:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 20:21 Guix System ext4 index full Roel Janssen
2020-06-03 20:35 ` Tobias Geerinckx-Rice
2020-06-04  9:33   ` Roel Janssen
2020-06-04 13:05     ` Tobias Geerinckx-Rice [this message]
2020-06-04 13:27       ` Tobias Geerinckx-Rice
2020-06-04 18:55       ` Roel Janssen
2020-06-04 19:00         ` Vincent Legoll
2020-06-03 20:43 ` Vincent Legoll
2020-06-03 21:14   ` Tobias Geerinckx-Rice
2020-06-03 23:06     ` Leo Famulari
2020-06-04  9:27       ` Pierre Neidhardt

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d06fc779.fsf@nckx \
    --to=me@tobias.gr \
    --cc=help-guix@gnu.org \
    --cc=roel@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).