Forums / Support / Error 8 when writing line to file. Failing.

Error 8 when writing line to file. Failing.

by Shinji @
Hello.

BB 1,97 buil93 did stop with the following line in the log-tab:
'Error 8 when writing line to file. Failing.'
Normally I would think: Error 8 = not enough Space.
So I checked my PC:
- SSD (SATA3) with Parts Folder: F: around 27GB Free
- SSD (SATA2) with Windows7pro32Bit and Programs: C: around 18GB free
- HDD (SATA3 Velociraptor) for Attachments: D: around 260GB
- PC has 4GB DDR3 RAM and Win-Systemmonitor tells me 1,6GB are free.

How can i search for the cause of this Problem?
Or has BB a problem with running 24/7 in an endless loop?
 

BinaryBoy's reply to Shinji #15643 @

Running 24/7 hours shouldn't cause this to happen (unless the drive really does fill). The error 8 "Not enough storage is available to process this command" is coming from Windows immediately after attempting to write to the file. Since you have room on your drive, I don't know exactly what could be causing this. One possibility is that BB for some reason is telling Windows to write a lot more data to the part file than is really available. I'll look into that but so far I don't have a clue.
 

Shinji's reply to BinaryBoy #15677 @

Hello.

Here ist is again.
LOG-Tab:
Error 8 when writing line to file. (I64d free). Failing.
Stop(): State: 5, Socket: 63412
Stop(): State: 5, Socket: 63220
Stop(): State: 5, Socket: 63256
Stop(): State: 4, Socket: 63016
Stop(): State: 5, Socket: 63236
Stop(): State: 5, Socket: 62496
=====================

Windows7Pro32Bit and Program-Drive C:
381.061.230.592 Bytes free

Attachement-Folder: D:\BBOY
381.036.064.768 Bytes free

Main-Parts-Folder: F:\BB-PARTS
29.179.527.168 Bytes free
=====================
And my 'binboy.xml' got destroyed (size = 0 Byte).
I restored this file from a backup and now bb runds agin.
 

BinaryBoy's reply to Shinji #15678 @

That I64d should have been a number but the logging got a little messed up.

The disk full error is still coming directly from Windows and not from the program so I'm a bit stumped at the moment. If Binary Boy hadn't received the error, it would have happily continued writing to disk. This is a bit of a long shot but maybe it ran low on RAM rather than disk space and was unable to cache the data for the write. The best I can figure out right now is to add a bit more logging for the next time the error happens.

Did Binary Boy crash while closing? Or maybe the computer forced Binary Boy to close while rebooting? That could potentially cause the 0 byte xml file (or a corrupted history file).
 

nikkil's reply to BinaryBoy #16041 @

Hi Shinji, I was wondering on how this worked out for you.