[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Corrupt .drv files

From: Ludovic Courtès
Subject: Re: Corrupt .drv files
Date: Tue, 12 Jul 2016 10:59:04 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)

Andreas Enge <address@hidden> skribis:

> On Mon, Jul 11, 2016 at 11:49:08PM +0200, Ludovic Courtès wrote:
>> > Andreas Enge <address@hidden> skribis:
>> >
>> >> guix archive: error: build failed: error parsing derivation 
>> >> `/gnu/store/k49lwfwgs8wcamys5qzn8c5n2zk0prc1-tcl8.6.4-src.tar.xz.drv': 
>> >> expected string `Derive(['
>> >
>> > It looks like the store on this machine is corrupt.
>> Indeed, the daemon doesn’t attempt to atomically write files coming from
>> an add-to-store RPC, which includes .drv files.
>> So I think that if you pull the plug before the .drv has been flushed to
>> disk but after the .drv has been marked as valid in the SQLite database
>> (which is likely to happen in a timely fashion because SQLite does the
>> ‘fdatasync’ dance appropriately), then you end up with a truncated .drv
>> file.
> I do not think that this was the problem. I opened the .drv files with vim,
> and they did not contain ASCII characters. Also, the file command marked
> them as binary data instead of text files.

So did they contain random bytes?

That could be a hard disk problem or something equally fishy.

Nevertheless I think the problem I described above really exists and is
worth mitigating.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]