So here’s a new one to me. I’ve seen SharePoint logging creating 0k log files in the past – due to a variety of reasons like service account permissions being out of wack and the timer job somehow getting ‘stuck’. Usually when I come across these 0k files, it’s when I’m trying to debug something on a site only to find out that nothing I’ve been doing is getting logged – irritating. Anyhow, the other common circumstance I run into is that by the time I notice that 0k files are being created (hey, maybe 0k log files should be a monitorable event that gets reported by MOM, etc… someone get on that…) its long after any useful logs have been purged from the system – so there’s a directory full of 0k files. Go put your troubleshooting hat on. This week while working on a client site, I actually got to catch the log files ‘going 0k’, so there were still a few logs with content in them. So, I checked out the most recent log with any data in it and found an interesting entry – the last one in fact:10/01/2007 15:41:43.65 wsstracing.exe (0x0664) 0x07AC ULS Logging Unified Logging Service uls2 Monitorable Not enough free disk space available. The tracing service has temporary stopped outputting trace messages to the log file. Tracing will resume when more than 220 MB of disk space becomes availableWow, that’s hilarious. Not only is SharePoint intelligent enough to know when to hold off on logging so it doesn’t contribute any further to the obvious issue, but it’s polite enough to tell us about it. I had a good laugh about this, but it gets better. I go ahead and clean up what few files I can to get above the 220 MB limit. (yes, there were a few other issues here that should be dealt with – this particular environment was very constrained for space and the log files should be moved off of the C: drive, etc…) Then I go back and check the log files. True to its word, not only has SharePoint restarted its logging it’s given us the following message:10/02/2007 15:29:12.92 wsstracing.exe (0x0664) 0x1030 ULS Logging Unified Logging Service 7055 Information The tracing service has resumed outputting trace messages to the log file.Fun stuff. It made me smile. J