GNU logs - #48462, boring messages

Message sent to bug-guix@HIDDEN:

Subject: bug#48462: Corrupt, un-repairable store after power cut during upgrade
Resent-From: elaexuotee@HIDDEN
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Sun, 16 May 2021 08:59:01 +0000
Resent-Message-ID: <handler.48462.B.16211555309158 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: 48462 <at> debbugs.gnu.org
Date: Sun, 16 May 2021 17:59:57 +0900
From: elaexuotee@HIDDEN
Message-Id: <3OE5JSDGIIX2D.3SOQ0QIKI7XZR@HIDDEN>
User-Agent: mblaze/1.1
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=69.72.42.5;
 envelope-from=bounce+7434c3.08547a-bug-guix=gnu.org@HIDDEN;
 helo=m42-5.mailgun.net
X-Spam_score_int: -20
X-Spam_score: -2.1
X-Spam_bar: --
X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1,
 DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
 RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_PASS=-0.001 autolearn=ham autolearn_force=no
X-Spam_action: no action
X-Spam-Score: -1.3 (-)
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -2.3 (--)

Hey Guix,

Recently, during in the middle of a `guix package -m .guix/manifest.scm`, m=
y
machine had power failure. After rebotting, I simply reran the above and
it completed without error.

However, it appears that some of files in the store items are corrupt:

    $ vim
    vim: error while loading shared libraries: /gnu/store/6z2g9ybl3fkx6bdfg=
226mz8rpc0g53jx-gtk+-2.24.32/lib/libgdk-x11-2.0.so.0: file too short

    $ file -L /gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0g53jx-gtk+-2.24.32/lib/=
libgdk-x11-2.0.so.0
    /gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0g53jx-gtk+-2.24.32/lib/libgdk-x11=
-2.0.so.0: empty

As an extra bit of annoyance, the handy verify and repair tools fail to see=
 a
problem:

    $ command -v vim | xargs readlink -f
    /gnu/store/h9q2fik60axj9sai5b66cjk2sfl37ij1-vim-full-8.2.2689/bin/vim

    $ sudo guix build --repair vim-full
    /gnu/store/h9q2fik60axj9sai5b66cjk2sfl37ij1-vim-full-8.2.2689

    $ sudo guix build --repair --no-grafts vim-full
    path `/gnu/store/73p5rzka1cb9dx9fy059lmkf1jg6sv95-gtk+-2.24.32' is corr=
upted or missing!
    found corrupted or missing path `/gnu/store/73p5rzka1cb9dx9fy059lmkf1jg=
6sv95-gtk+-2.24.32' in the output closure of `/gnu/store/qyp10sss1ascp70ysh=
s87zdzr1lg71f8-vim-full-8.2.2689.drv'
    substituting /gnu/store/73p5rzka1cb9dx9fy059lmkf1jg6sv95-gtk+-2.24.32..=
=2E
    downloading from https://mirror.brielmaier.net/nar/lzip/73p5rzka1cb9dx9=
fy059lmkf1jg6sv95-gtk%2B-2.24.32 ...
     gtk%2B-2.24.32  6.4MiB          152KiB/s 00:43 [##################] 10=
0.0%

    /gnu/store/d21m63am0pxw77883h0y1jmy9iiazvvx-vim-full-8.2.2689

    $ sudo guix gc --verify=3Drepair,contents
    ...

    $ vim
    vim: error while loading shared libraries: /gnu/store/6z2g9ybl3fkx6bdfg=
226mz8rpc0g53jx-gtk+-2.24.32/lib/libgdk-x11-2.0.so.0: file too short

Even going in with a crude hammer doesn't fix things:

    $ sudo mount -o rw,remount /gnu/store

    $ sudo mv /gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0g53jx-gtk+-2.24.32 .

    $ sudo guix build --repair vim-full
    path `/gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0g53jx-gtk+-2.24.32' is corr=
upted or missing!
    found corrupted or missing path `/gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0=
g53jx-gtk+-2.24.32' in the output closure of `/gnu/store/z2q3zna20cn32if3v2=
71x4xavd70ml5z-vim-full-8.2.2689.drv'
    path `/gnu/store/73p5rzka1cb9dx9fy059lmkf1jg6sv95-gtk+-2.24.32' is corr=
upted or missing!
    substituting /gnu/store/73p5rzka1cb9dx9fy059lmkf1jg6sv95-gtk+-2.24.32..=
=2E
    downloading from https://mirror.brielmaier.net/nar/lzip/73p5rzka1cb9dx9=
fy059lmkf1jg6sv95-gtk%2B-2.24.32 ...
     gtk%2B-2.24.32  6.4MiB          134KiB/s 00:49 [##################] 10=
0.0%

    applying 17 grafts for /gnu/store/lm9xqz82q4cwlqs79i0pq77z6cfsx3rw-gtk+=
-2.24.32.drv ...
    grafting '/gnu/store/73p5rzka1cb9dx9fy059lmkf1jg6sv95-gtk+-2.24.32' -> =
'/gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0g53jx-gtk+-2.24.32'...
    successfully built /gnu/store/lm9xqz82q4cwlqs79i0pq77z6cfsx3rw-gtk+-2.2=
4.32.drv
    gnu/store/h9q2fik60axj9sai5b66cjk2sfl37ij1-vim-full-8.2.2689

    $ vim
    vim: error while loading shared libraries: /gnu/store/6z2g9ybl3fkx6bdfg=
226mz8rpc0g53jx-gtk+-2.24.32/lib/libgdk-x11-2.0.so.0: file too short

It seems like the above graft is going badly:

    $ file -L /gnu/store/73p5rzka1cb9dx9fy059lmkf1jg6sv95-gtk+-2.24.32/lib/=
libgtk-x11-2.0.so.0
    /gnu/store/73p5rzka1cb9dx9fy059lmkf1jg6sv95-gtk+-2.24.32/lib/libgtk-x11=
-2.0.so.0: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), statical=
ly linked, not stripped

    $ file -L /gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0g53jx-gtk+-2.24.32/lib/=
libgdk-x11-2.0.so.0
    /gnu/store/6z2g9ybl3fkx6bdfg226mz8rpc0g53jx-gtk+-2.24.32/lib/libgdk-x11=
-2.0.so.0: empty

Some questions:

  1) Am I just missing something obvious?
  2) How could grafting end up producing empty files in the output?
  3) Is the store supposed to be robust against power failures?

Message sent:

Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Type: text/plain; charset=utf-8
X-Loop: help-debbugs@HIDDEN
From: help-debbugs@HIDDEN (GNU bug Tracking System)
To: elaexuotee@HIDDEN
Subject: bug#48462: Acknowledgement (Corrupt, un-repairable store after
 power cut during upgrade)
Message-ID: <handler.48462.B.16211555309158.ack <at> debbugs.gnu.org>
References: <3OE5JSDGIIX2D.3SOQ0QIKI7XZR@HIDDEN>
X-Gnu-PR-Message: ack 48462
X-Gnu-PR-Package: guix
Reply-To: 48462 <at> debbugs.gnu.org
Date: Sun, 16 May 2021 08:59:02 +0000

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-guix@HIDDEN

If you wish to submit further information on this problem, please
send it to 48462 <at> debbugs.gnu.org.

Please do not send mail to help-debbugs@HIDDEN unless you wish
to report a problem with the Bug-tracking system.

--=20
48462: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3D48462
GNU Bug Tracking System
Contact help-debbugs@HIDDEN with problems

Message sent to bug-guix@HIDDEN:

Subject: bug#48462: Corrupt, un-repairable store after power cut during upgrade
Resent-From: Liliana Marie Prikler <liliana.prikler@HIDDEN>
Original-Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
Resent-CC: bug-guix@HIDDEN
Resent-Date: Sat, 23 Oct 2021 07:50:02 +0000
Resent-Message-ID: <handler.48462.B48462.163497536719595 <at> debbugs.gnu.org>
Resent-Sender: help-debbugs@HIDDEN
To: elaexuotee@HIDDEN, 48462 <at> debbugs.gnu.org
Message-ID: <182fe7e6dbcdfedce51c77efc56e35e45da817a6.camel@HIDDEN>
From: Liliana Marie Prikler <liliana.prikler@HIDDEN>
Date: Sat, 23 Oct 2021 09:49:16 +0200
In-Reply-To: <3OE5JSDGIIX2D.3SOQ0QIKI7XZR@HIDDEN>
References: <3OE5JSDGIIX2D.3SOQ0QIKI7XZR@HIDDEN>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.2 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: list
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>

Hi Guix,

Am Sonntag, den 16.05.2021, 17:59 +0900 schrieb elaexuotee@HIDDEN:
> Hey Guix,
> 
> Recently, during in the middle of a `guix package -m
> .guix/manifest.scm`, my
> machine had power failure. After rebotting, I simply reran the above
> and it completed without error.
> 
> However, it appears that some of files in the store items are
> corrupt:
> 
> [...]
> As an extra bit of annoyance, the handy verify and repair tools fail
> to see a problem:
> 
> [...]
> 
> Some questions:
> 
>   1) Am I just missing something obvious?
>   2) How could grafting end up producing empty files in the output?
>   3) Is the store supposed to be robust against power failures?
After dealing with some softer issues related to power outage during
`guix package', I think I'm now able to say that Guix does not process
grafts correctly during repair.

What happened for me, was that certain store files were empty and when
they were later grafted, those empty files were carried over.  Guix,
upon repairing the store, did then not regraft those, but rather kept
them as-is.  I have since fixed said issue by manually deleting the
graft and rebuilding (this was possible, because nothing referred to it
– I'm not sure why `guix gc' didn't pick it up as dead earlier,
though).  Stuff in my profiles seem to also have been rebuilt after
roll-back+gc.

So I think content repair needs to have at least two steps:
1. checking and repairing all "normal" derivations.
2. fixing grafts of packages that were repaired in step 1.

WDYT?

Last modified: Sat, 23 Oct 2021 08:00:01 UTC

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997 nCipher Corporation Ltd, 1994-97 Ian Jackson.