Log File Missing??

Hi,

I have encountered an issue with one of my log files which has me somewhat puzzled.
I receieved notification at 00:02:16:36 that the Log file was full:
The log file for database 'TDS' is full. Back up the transaction log for the database to free up some log space..
A large number of these same messages have followed.

Prior to these messages starting the log file was backed up successfully at 00:00:01:10
Shortly after this there is a message - and this is the bit that confuses me - at 00:02:16:35 that says:
d:\mssql\data\tds_log.ldf: Operating system error 112(error not found) encountered.

So from what I can tell the log file was backed up successfully. Then approx 1 minute later the system can't find the log file?
Then I keep getting these log file full messages - until the next log backup (60 min later)...then everything is fine. HUH?

When looking at the log file for SQL it is sitting there, and isn't new, as it's created date is back when I setup the database initially.

Can anyone shed any light on what this message might mean and whether there is specifically something that I can do to circumvent it in the future.

Oh yeah we have nothing tricky in terms of replication or log shipping or anything like that....

Thanks in advance for any assistance.

TroyI started writing the reply but just wanted to make sure that my "hunch" is somewhere in the neiborhood of the real cause, - compressed volume. And after searching for a couple of minutes confirmed that a couple of other SQL guys think of this error the same way. But, to be a little bit more open-minded, I'd also throw in a couple of more possibilities (feel free to throw them away if they don't apply): EFS, VSS, anti-virus. Take a pick!|||thanks for the response - I had a quick search also - but didn't come up with a hell of a lot - most other people who had the same error had a different explaination (ie it said lack of disk space etc etc)...

Annnyhow, thanks for the ideas...in response, we don't have any compressed files on this server, likewise with Encryption.
We have virus scanning enabled, however it's scheduled scan is setup to run at 0400 which is way out of the park for this issue - so not sure how this could be a factor.
As for VSS - what is this?

I might have missed exactly what you are on about, so apologies, but if I have could you ellaborate a little more?

Cheers
Troy