> Fa3ien wrote:
> 
>> In short, a good'ol chkdsk /f solved the problem.
>> I didn't knew that so much empty space could be
>> erroneously marked as allocated...
> 
> Woah! o_O
> 
> That's one unhappy filesystem... heh. Glad it's all fixed now though. 
> (Although you probably ought to find out *why* it did this in the first 
> place...)

I'll check regularly to see if it happens again... Maybe it's related
to the problems I had with Raid in may. I currently run the server
without Raid1, because the bad experience showed me that no raid (with
a daily backup, anyway) is less of a potential hassle than shitty SIS
software Raid (which is more insecure because it doesn't inform you
correctly of the real array state).

Fabien.

Post a reply to this message