I have Lightroom 3.3 on a Windows 7 x64 machine. It's started to throw a disk critically low warning every few days for the drive that has my LR catalog on it. The drive has 390GB free
Has anyone else seen this before? Is it a known issue? How do I make it go away?
Do you, by any chance, have your page file set at a fixed size? If so, change the setting by either increasing the max size alloted to the page file or by letting Windows manage the size. I saw this a few times on Vista 32 bit until I changed back to letting Windows manage the page file size.
I checked the drive by using the built-in Windows error checking tools. I've never mucked with the page file settings. It's NTFS, not FAT32. Windows automatically defrags all my disks every Wednesday at 1am. It last defraged the drive on 3/3 at 2:20am and it is listed as 0% fragmented.
The windows error tool really won't show much about your drives and the condition of them. You need to access the SMART info for the temperature they are running at (anything over 35 C is really bad news). There are lots of free apps that will give you a better idea of drive condition, sometimes supplied by the manufacturers. Try google.
As suggested elsethread, you need to look at something that peaks use and then releases space on that volume. There are a few cases where the OS can issue this message. An app can only respond and report on this condition.
Just powered my machine on from sleep and Lightroom had this message up again. Which made me wonder... does it have anything to do with waking the machine from sleep? But alas, no. I tried to reproduce the problem by going to sleep with LR open and then waking the machine again, but the message didn't come up.
Anyone have any other ideas for how to chase the cause of this down? There are currently no files in the recycle bin and 393GB free on the drive.
You could install one of the utils from http://technet.microsoft.com/en-us/sysinternals/bb545046 Sysinternals and see if you can see what system call is failing, and when, and on what file item.
Those of you who need to defrag the SQLite catalogue should look there, too.
This error is reported here every couple of months or so. It always seems to happen just occasionally on the problematic systems, and it seems to do no real harm, other than worrying the victims. I haven't run across any workarounds, fixes, or explanations. Personally, if it were happening to me every so often, I'd ignore it.