On Friday 01 April 2005 11:57, Hylton Conacher (ZR1HPC) wrote:
I have seen many folk who have signatures stating that the machine has been running for something like 400 days.
Whilst I applaud this type of reliability, I am wondering about the actual fs as the machine isn't rebooted so that fsck can check the partitions.
Why? This isn't a FAT partition that gets screwed up at the drop of a hat.
I am perhaps paranoid about keeping the fs in tip top shape but it is the basis that we all rely on.
Perhaps. But if you look at the system and the fsck command, you will see that you can set the number of reboots or time before the command runs. I'm not sure what the max is, but what if you could set it to 100 reboots, or 500 days? As long as it is still running and you aren't getting any errors then the file system is fine. One of the nice things about linux is that with regards to the file system and the way it logs things, you would know long before there are any real problems.
so my question is this: Can a system that has such uptime have its all its fs checked and not be rebooted?
Depends on what it's doing. If there is a lot of disk activity, then I wouldn't take a partition off-line. That a way to have a disaster for sure. As I've already mentioned, it isn't something that is really required with todays file systems. Well, except for the m$ ones.. Mike -- Powered by SuSE 9.2 Kernel 2.6.8 KDE 3.3.0 Kmail 1.7.1 For Mondo/Mindi backup support go to http://www.mikenjane.net/~mike 8:14pm up 2 days 23:36, 3 users, load average: 2.07, 2.15, 2.08