I performed manual manipulation of a spool by deleting lots of articles from tradspool directories and deleted a CNFS buffer containing binaries and junk).
I removed the history files and overview directory contents, and have been running makehistory since 10/12/2023 and it is *still* running...
The previous overview directory was 67GB and the new one is at 107GB, which seems odd because I did not add articles
While watching lsof output against the makehistory PID, I am finding that it is scanning the same tradspool folders more than once, but I am not sure if that is expected?
I also have a couple of "Bad article handle" messages that don't make sense:
makehistory: tradspool: can't determine class of @0500000087B5000000000001390000000000@: Bad article handle
It seems okay though?
$ sm -c '@0500000087B5000000000001390000000000@' @0500000087B5000000000001390000000000@ method=tradspool class=0 ngnum=34741 artnum=0 file=/usr/local/news/spool/articles/misc/health/alternative/80128
When dealing with tradspool, it should indeed treat directories in order (tradspool_next() method). Maybe the behaviour you see comes from crossposted articles? makehistory opens the (hard-linked) file present
in each directory an article has been crossposted to, and looks at its
Xref header field to seek the first newsgroup mentioned (considered to
be the master, and only treats the article when dealing with that first newsgroup).
I am very unsure why it would happen during a rebuild of the history
file. Looking at a comment, a modification of the storage.conf file is mentioned. Would it happen that the article stored in tradspool
according to the rules of your initial storage.conf file has now a
different rule?
With lsof it is hard to catch individual open files/links, but what I am noticing is that it will open a directory, say /usr/local/news/spool/articles/uk/d-i-y, and appears to iterate through that directory building history and overview. Now that I'm several days into the process, I see that this morning it currently has /usr/local/news/spool/articles/uk/d-i-y open again and seems to be doing the same thing I noticed days ago.
makehistory: cannot write overview data
They seem like normal articles to me and nothing stands out at first glance:
$ cat /usr/local/news/spool/articles/de/alt/dateien/misc/35
Hi Jesse,
With lsof it is hard to catch individual open files/links, but what I am
noticing is that it will open a directory, say
/usr/local/news/spool/articles/uk/d-i-y, and appears to iterate through that >> directory building history and overview. Now that I'm several days into the >> process, I see that this morning it currently has
/usr/local/news/spool/articles/uk/d-i-y open again and seems to be doing the >> same thing I noticed days ago.
Strange. I don't understand why makehistory would re-process the same newsgroup twice.
Is it also listed several times in /usr/local/news/spool/tradspool.map?
makehistory: cannot write overview data
They seem like normal articles to me and nothing stands out at first glance: >>
$ cat /usr/local/news/spool/articles/de/alt/dateien/misc/35
The headers look normal. I also do not know what's happening :(
Looking at the possible reasons for this error, I assume you're not
using ovgrouppat (inn.conf) as it may cause that on some cases.
Otherwise, I don't see why the write could not be done. Is this error
only appearing now, after almost 20 days of makehistory run? (seems an eternity)
makehistory: cannot write overview data
They seem like normal articles to me and nothing stands out at first glance:
$ cat /usr/local/news/spool/articles/de/alt/dateien/misc/35
I have about 20 of these errors now. They are all from the same group, de.alt.dateien.misc, and a few are of the same thread but otherwise I see nothing out of place.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 72:36:39 |
Calls: | 6,714 |
Calls today: | 2 |
Files: | 12,246 |
Messages: | 5,357,083 |