![](https://seccdn.libravatar.org/avatar/5a94d2f8a5845d5f1c1ea1556fc0cb72.jpg?s=120&d=mm&r=g)
Chris Roubekas wrote:
Well it turns out that md0 is in state:dirty,no-errors for about 19 days!!
Any good ideas anyone?? Is there something that I can do to change the "dirty" state??
Other than reboot, I don't know. It would need to be fscked to be marked as clean AFAIK, but with Linux uptimes, I suspect this is just saying at the next reboot it will be checked. IIUC, there is both a max mount count and max days for a partition to be 'clean'. If you reboot often, or otherwise mount and unmount often, your drives will be fscked often. Likewise, if you seldom reboot, your drive may need checked after a certain amount of uptime (due to power glitches, etc.), which IIUC is accomplished by marking the partition as dirty allowing it to be sure to be checked next opportunity, such as a reboot. I suppose you could remount it ro to fsck, but since there are so many programs and processes running which need to write to the drives, it seems safer to me in the long run to just reboot. If I'm wrong, I would also like to know a better way. HTH. -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Registered Linux user 231871