From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jack Hill Subject: Re: Possible store corrumption Date: Tue, 21 May 2019 16:30:43 -0400 (EDT) Message-ID: References: <87y3308amj.fsf@roquette.mug.biscuolo.net> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=UTF-8 Content-Transfer-Encoding: 8BIT Return-path: Received: from eggs.gnu.org ([209.51.188.92]:34205) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hTBa4-0000p0-Rh for help-guix@gnu.org; Tue, 21 May 2019 16:41:53 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hTBPK-00086R-0I for help-guix@gnu.org; Tue, 21 May 2019 16:30:46 -0400 Received: from minsky.hcoop.net ([104.248.1.95]:53852) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hTBPJ-00085m-Sz for help-guix@gnu.org; Tue, 21 May 2019 16:30:45 -0400 In-Reply-To: <87y3308amj.fsf@roquette.mug.biscuolo.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Giovanni Biscuolo Cc: help-guix@gnu.org On Tue, 21 May 2019, Giovanni Biscuolo wrote: > Could be a full disk issue? In this case that was not true. It turned out to be bad memory. When I ran a memory test, it aborted do to too many errors, which is not a good sign ☺. Therefore, I expect what was happening was that data was being corrupted in memory, and the bad data was begin written to disk. Thanks for your help, Jack