From: "Martin Bähr" <mbaehr@email.archlab.tuwien.ac.at>
To: Mark Alexander <marka@pobox.com>
Cc: supmua <supmua@googlegroups.com>
Subject: Re: [sup] offsets for mbox broken
Date: Wed, 20 Jan 2016 18:15:06 +0100 [thread overview]
Message-ID: <20160120171506.GM24197@email.archlab.tuwien.ac.at> (raw)
In-Reply-To: <1453299579-sup-1626@t60p>
On Wed, Jan 20, 2016 at 09:22:53AM -0500, Mark Alexander wrote:
> 1. Use sup-dump to make an ASCII dump of the message state and tags.
> 2. Move the Xapian index (~/.sup/xapian) to some other location.
> 3. Used sup-restore to read the dump created in step 1.
>
> I don't know if this going to work for you, but it might be worth
> a try since your index is broken.
wow, thank you!
i don't see how it could not work. sup-dump only stores the message-id
and the
labels, that means on restore sup-sync has to find that message and then
recreate
everything else from the original mbox data.
it is essentially doing a fresh import of everything, with the only
added
information of setting the labels. looks fool-proof to me.
the only downside is that at 6GB of emails, this is going to take a
loooong time. (and so i need to write this with mutt :-(
i am certainly going to complete this, but i wonder if there is a faster
way, something that doesn't rebuild the whole index, but just resyncs
the offsets.
greetings, martin.
--
eKita - the online platform for your entire academic life
--
chief engineer eKita.co
pike programmer pike.lysator.liu.se caudium.net societyserver.org
secretary beijinglug.org
mentor fossasia.org
foresight developer foresightlinux.org realss.com
unix sysadmin
Martin B�hr working in china http://societyserver.org/mbaehr/
prev parent reply other threads:[~2016-01-20 17:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-20 9:56 Martin Bähr
2016-01-20 14:22 ` [sup] " Mark Alexander
2016-01-20 14:25 ` Mark Alexander
2016-01-20 17:15 ` Martin Bähr [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160120171506.GM24197@email.archlab.tuwien.ac.at \
--to=mbaehr@email.archlab.tuwien.ac.at \
--cc=marka@pobox.com \
--cc=supmua@googlegroups.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox