Skip to main content
3 of 8
clearer that the younger question was not yet alive when I answered

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

I marked:

  • Disk usage is always at 100%
    • 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)

as a duplicate of:

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 about the same matter. The latter question stresses more the startup time, but I had it also at startup, but I also had times when the lags did not go away even after hours, therefore I still saw the older question as the right one. And I think that it is likely that the younger question is not only about the first 15-20 minutes, but also about this lagging at startup, no matter how long it takes.

Now 10 months ago, someone did not make such a research and opened a highly active question.

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 other question then become the duplicate?
  • Should I try to flag the younger question as a duplicate again?