bug#41710: closed (Possibly found a bug while doing a "guix pull")

[GNU bug Tracking System]

Your message dated Wed, 10 Jun 2020 15:25:30 +0200
with message-id <87v9jzdpdh.fsf@gnu.org>
and subject line Re: bug#41710: Possibly found a bug while doing a "guix pull"
has caused the debbugs.gnu.org bug report #41710,
regarding Possibly found a bug while doing a "guix pull"
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
41710: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=41710
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: Possibly found a bug while doing a "guix pull" Date: Thu, 4 Jun 2020 16:38:09 +0200

Hello!

I just tried to "guix pull" on my Debian Buster GNU/Linux system. Twice it made the system completely freeze for a few seconds and then reboot. And that third time it didn't crash the system but the guix pull failed and returned this error:

https://pastebin.com/vhDR8gDC

Can somebody help me please?

(Before doing the third "pull", I did an "apt update" and "upgrade", but I wasn't that much behind in updates, I had done it less than a week ago last. My last "guix pull" was made at the same time as the "apt update", a few days ago.)

Hoping I can resolve this soon or that my feedback was positive for the development of Guix. =)

I can provide log debug info (if there is any) upon request.

Best regards!

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#41710: Possibly found a bug while doing a "guix pull"
>
>
>
>
> Date: 
>
> Wed, 10 Jun 2020 15:25:30 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)
>
>
>
>
> Hello,
>
> Danny Milosavljevic <dannym@scratchpost.org> skribis:
>
> > On Mon, 8 Jun 2020 01:15:46 +0200
> > Léon Lain Delysid <leon.lain.delysid@gmail.com> wrote:
> >
> >>or
> >> if my system crashing twice during a pull command somehow broke it, 
> >
> > Probably.
> >
> >>but I
> >> hope this feedback helped. 
> >
> > It sure helped.  It's good to know that that can happen.
> >
> > I remember the first time I used Guix, I picked some file system that would
> > keep doing that: leave empty files if the system crashed (among lots of other
> > things).  And that system crashed a lot.  I had the same result as you,
> > and a lot of additional problems.
> >
> > Back then we already improved a lot of places that were really really
> > important (added fsync calls), so the remaining places should be quite
> > harmless--like this one.  Because of Guix, you can always rebuild
> > /gnu/store just as it was--after a long build time maybe, but it's possible
> > (could be made a LOT more usable, though).
> >
> > (fsync degrades performance, so it makes no sense to fsync for /gnu/store)
> >
> > I think we can't really do more without imposing undue mainentance burden on
> > us (for something the file system shouldn't be doing in the first place),
> > or we could recommend another file system or different file system options
> > in the manual.  What would the latter be?
> >
> > Also, how it the world didn't the file system checker fsck
> >
> > (1) automatically run and
> > (2) fix this
> >
> > in your case?
>
> Yeah, that’s really weird.  I never experienced it first-hand, but it’s
> not the first time we have such a report.
>
> Ext4 & co. reportedly can leave empty files upon crashes; perhaps that’s
> a problem with those file systems (though I’ve always used ext2/3/4 and
> never had this problem myself, but that’s not statically significant).
>
> Anyway, closing.
>
> Thank you, Léon!
>
> Ludo’.
>
>
> --- End Message ---