From: akb+lists.ding@mirror.to (Andrew B)
To: ding@gnus.org
Subject: help with corrupted files; ticked articles missing
Date: Sun, 02 Jul 2023 06:13:43 -0400 [thread overview]
Message-ID: <0qr0pqzkmg.fsf@mirror.to> (raw)
The partition containing my home directory filled up, and I cleared
space and exited gnus, though I am not sure in what order.
At present, when I start gnus, the group that I was reading
when the disk filled up has a Group buffer line like this:
3: 2 / 1! 124410: nnimap+machinename:INBOX
but it should look more like this:
3: 80 / 997! 124410: nnimap+machinename:INBOX
When I enter the group, no matter how many articles I tell gnus to
fetch, it only shows those two unread articles. The read articles
are still on the server, gnus just won't fetch and display them.
Other groups behave normally; I can hit C-u RET and it will fetch
as many articles as I ask for.
I have a backup from a few days ago that includes
-rw-r--r-- 1 username username 250036 Jun 25 18:53 #.newsrc-dribble#
-rw-r--r-- 1 username username 241532 May 19 14:45 #.newsrc-dribble#~
-rw-r--r-- 1 username username 216738 Jan 5 04:08 .newsrc-dribble
-rw-r--r-- 1 username username 201734 Jul 6 2022 .newsrc-dribble~
-rw-r--r-- 1 username username 393157 Feb 8 2022 .newsrc.eld
-rw-r--r-- 1 username username 392927 Feb 7 2022 .newsrc.eld~
-rw-r--r-- 1 username username 0 Dec 6 2019 .newsrc
What can I do to recover my unread and ticked articles?
Are there any files besides .newsrc ones that I need to recover gnus state?
I'm fine with having to re-read a few days of mail to get the state back
to what it was before the disk filled up.
Thanks very much for any assistance!
I will probably be offline for the next 3-4 days but will respond
to any questions as soon as I return.
--akb
next reply other threads:[~2023-07-02 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-02 10:13 Andrew B [this message]
2023-07-03 4:08 ` Eric Abrahamsen
2023-07-13 19:44 ` Andrew B
2023-07-14 21:36 ` RL
2023-08-03 22:21 ` Andrew B
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=0qr0pqzkmg.fsf@mirror.to \
--to=akb+lists.ding@mirror.to \
--cc=ding@gnus.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 NNTP newsgroup(s).