Skip to main content
6 of 8
wrong question said to be marked as duplicate

How to deal with a duplicate for which the flag aged away? Should the other question then become the duplicate?

I marked:

as a duplicate of:

  • Disk usage is always at 100%
    • +1
    • Asked 7 years, 10 months ago
    • Modified 5 days ago
    • Viewed 5k times
    • 1 answer: +2 (my answer from December 2022, thus answered only after almost 7 years)

And the flag aged away.

I marked it as a duplicate since I had the same question in December 2022, and then, the younger question was not yet asked. At that time, I did thorough research and found the question that was 7 years old. Even though I knew that this is very old, it was still the same that I had. Now in February 2023, someone did not make such a research and opened a highly active question. It stresses more the startup time, but I guess that this goes without saying since I had it also at startup, but not always just 15-20 minutes but also half an hour or two hours. Asking about this being always at 100 % is a shortened way of saying that this lagging begins with the startup and lasts a long time.

I would like to mark the younger and higher active question as the duplicate of the older one, and since the flag aged away, I wonder how the community sees this. Does the older question have the "right" to put a duplicate marker on a younger question, or is the higher activity of the younger question proof enough that the old question is not found well on the net and should become the duplicate of the younger question instead?

How does the community deal with a duplicate for which the flag aged away:

  • Should the older question then become the duplicate?
  • Should I try to flag the younger question as a duplicate again?