all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: "Léon Lain Delysid" <leon.lain.delysid@gmail.com>,
	41710-done@debbugs.gnu.org
Subject: bug#41710: Possibly found a bug while doing a "guix pull"
Date: Wed, 10 Jun 2020 15:25:30 +0200	[thread overview]
Message-ID: <87v9jzdpdh.fsf@gnu.org> (raw)
In-Reply-To: <20200608130257.66286fbd@scratchpost.org> (Danny Milosavljevic's message of "Mon, 8 Jun 2020 13:02:57 +0200")

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’.




  reply	other threads:[~2020-06-10 13:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 14:38 bug#41710: Possibly found a bug while doing a "guix pull" Léon Lain Delysid
2020-06-04 15:41 ` Julien Lepiller
2020-06-04 18:11   ` zimoun
2020-06-06 13:22     ` Ludovic Courtès
2020-06-07  1:12       ` Léon Lain Delysid
2020-06-07 20:06         ` Ludovic Courtès
2020-06-07 23:15           ` Léon Lain Delysid
2020-06-08 11:02             ` Danny Milosavljevic
2020-06-10 13:25               ` Ludovic Courtès [this message]
2020-06-12  9:55                 ` Léon Lain Delysid
2020-06-07  1:19     ` Léon Lain Delysid
2020-06-07  1:15   ` Léon Lain Delysid

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=87v9jzdpdh.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=41710-done@debbugs.gnu.org \
    --cc=dannym@scratchpost.org \
    --cc=leon.lain.delysid@gmail.com \
    /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.