From: Jani Nikula <jani@nikula.org>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Cc: tomi.ollila@iki.fi
Subject: Re: [PATCH v2 5/5] compact: provide user more information on after-compaction failures
Date: Thu, 14 Nov 2013 15:13:25 +0100 [thread overview]
Message-ID: <871u2jnkai.fsf@nikula.org> (raw)
In-Reply-To: <1384362167-12740-6-git-send-email-tomi.ollila@iki.fi>
On Wed, 13 Nov 2013, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> After database has been compacted, there are steps to put the new
> database into place -- and these steps may fail. In case such
> failure happens, provide better information how to resolve it.
I disagree with having a library spew all this information out. For each
case, I think it should be sufficient to just say what happened
(e.g. "rename a -> b failed" + strerror). I don't think a library's
error messages should be a tutorial on how to fix things.
We may need to amend notmuch compact man page though.
BR,
Jani.
>
> Thanks to Ben Gamari for most of the information content.
> ---
> lib/database.cc | 39 +++++++++++++++++++++++++++++++++++----
> 1 file changed, 35 insertions(+), 4 deletions(-)
>
> diff --git a/lib/database.cc b/lib/database.cc
> index 4b5ac64..a6daac6 100644
> --- a/lib/database.cc
> +++ b/lib/database.cc
> @@ -939,19 +939,50 @@ notmuch_database_compact (const char *path,
> }
>
> if (rename (xapian_path, backup_path)) {
> - fprintf (stderr, "Error moving old database out of the way\n");
> + fprintf (stderr, "Error moving old database out of the way:\n"
> + "Old database: %s\n"
> + "Backup database: %s\n"
> + "Error: %s\n", xapian_path, backup_path, strerror (errno));
> ret = NOTMUCH_STATUS_FILE_ERROR;
> goto DONE;
> }
>
> if (rename (compact_xapian_path, xapian_path)) {
> - fprintf (stderr, "Error moving compacted database\n");
> + fprintf (stderr, "Error moving compacted database into place: %s\n",
> + strerror (errno));
> + fprintf (stderr, "\n"
> + "Encountered error while moving the compacted database\n"
> + "\n"
> + " %s\n"
> + "\n"
> + "to\n"
> + "\n"
> + " %s\n"
> + "\n"
> + "Please identify the reason for this and move the compacted database\n"
> + "into place manually.\n"
> + "\n"
> + "Alternatively you can revert to the uncompacted database with\n"
> + "\n"
> + " mv '%s' '%s'\n"
> + "\n", compact_xapian_path, xapian_path,
> + backup_path, xapian_path);
> ret = NOTMUCH_STATUS_FILE_ERROR;
> goto DONE;
> }
>
> - if (! keep_backup)
> - rmtree (backup_path);
> + if (! keep_backup) {
> + if (rmtree (backup_path)) {
> + fprintf (stderr, "Error removing backup database: %s\n",
> + strerror (errno));
> + fprintf (stderr, "\n"
> + "Please remove the backup database with\n"
> + "\n"
> + " rm -rf '%s'\n" "\n", backup_path);
> + ret = NOTMUCH_STATUS_FILE_ERROR;
> + goto DONE;
> + }
> + }
>
> DONE:
> if (notmuch)
> --
> 1.8.3.1
>
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> http://notmuchmail.org/mailman/listinfo/notmuch
next prev parent reply other threads:[~2013-11-14 14:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 17:02 compactor adjustments v2 Tomi Ollila
2013-11-13 17:02 ` [PATCH v2 1/5] compact: tidy formatting Tomi Ollila
2013-11-13 17:02 ` [PATCH v2 2/5] compact: catch Xapian::Error consistently Tomi Ollila
2013-11-14 14:13 ` Jani Nikula
2013-11-18 0:33 ` David Bremner
2013-11-13 17:02 ` [PATCH v2 3/5] compact: preserve backup database until compacted database is in place Tomi Ollila
2013-11-14 14:08 ` Jani Nikula
2013-11-13 17:02 ` [PATCH v2 4/5] compact: unconditionally attempt to remove old wip database compact directory Tomi Ollila
2013-11-14 14:02 ` Jani Nikula
2013-11-13 17:02 ` [PATCH v2 5/5] compact: provide user more information on after-compaction failures Tomi Ollila
2013-11-14 14:13 ` Jani Nikula [this message]
2013-11-14 16:11 ` David Bremner
2013-11-14 17:23 ` Tomi Ollila
2013-11-17 11:34 ` David Bremner
2013-11-17 15:28 ` Tomi Ollila
2013-11-18 0:53 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871u2jnkai.fsf@nikula.org \
--to=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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 public inbox
https://yhetil.org/notmuch.git/
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).