renumber following crash is wrong in 2.3

[Karl Kleinpaste]

My RH6.2 Linux system crashed last night.  When it came back up and
restarted INN, in which I use traditional spool and overview, it used
-r on itself.  Fine so far, except that the renumbering is just plain
wrong.  Active file upper bounds represent nowhere near the upper
bound in a lot of groups, with the result that my server is soon
throttled:

Nov 18 02:02:08 cinnamon innd: SERVER cant store article: File exists
Nov 18 02:02:09 cinnamon innd: tradspool: could not open /home/news/spool/articles/misc/rural/91879 File exists
Nov 18 02:02:09 cinnamon innd: SERVER cant store article: File exists
Nov 18 02:02:09 cinnamon innd: tradspool: could not open /home/news/spool/articles/misc/rural/91880 File exists
Nov 18 02:02:09 cinnamon innd: SERVER cant store article: File exists
Nov 18 02:02:09 cinnamon innd: tradspool: could not open /home/news/spool/articles/misc/rural/91881 File exists

For example, /home/news/spool/articles/misc/rural has filenames up to
91924.  But the overview file only has articles up to 91878.  The
active file now shows an upper bound of 91881.

I would think that the renumbering process should unconditionally pick
the highest value between what it finds in overview and what it finds
in the spool area.  No?

--karl