From: Mike Gerwitz <mtg@gnu.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: /var/guix/db/db.sqlite corruption
Date: Sat, 03 Aug 2019 09:05:17 -0400 [thread overview]
Message-ID: <87v9vetn5e.fsf@gnu.org> (raw)
In-Reply-To: <87pnlmiony.fsf@gmail.com> (Chris Marusich's message of "Sat, 03 Aug 2019 02:28:01 -0700")
[-- Attachment #1: Type: text/plain, Size: 923 bytes --]
On Sat, Aug 03, 2019 at 02:28:01 -0700, Chris Marusich wrote:
> I've also seen this happen. I opened a bug report about it recently:
>
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=36687
Ah, when I originally researched this issue, you hadn't yet reported
that bug. I should have checked again. I'll reply there with my
Message-Id. Thanks for pointing it out.
> Did you remember to stop the guix-daemon and verify that no processes
> were accessing the database file when you did all of this? If not, then
> I wouldn't be surprised to see bizarre behavior.
Yeah I had stopped the daemon and was running it manually to pass
`--debug'. The errors I was getting were not only from Guix---it was
also happening with the sqlite3 command.
--
Mike Gerwitz
Free Software Hacker+Activist | GNU Maintainer & Volunteer
GPG: D6E9 B930 028A 6C38 F43B 2388 FEF6 3574 5E6F 6D05
https://mikegerwitz.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2019-08-03 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 1:36 /var/guix/db/db.sqlite corruption Mike Gerwitz
2019-08-03 9:28 ` Chris Marusich
2019-08-03 13:05 ` Mike Gerwitz [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9vetn5e.fsf@gnu.org \
--to=mtg@gnu.org \
--cc=cmmarusich@gmail.com \
--cc=help-guix@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).