I own a Packard Bell PC Intel Celeron with 2.2 Ghz using Windows XP home. My hard disk has 60Gb capacity. It uses NTFS file system.
I had only used 17 Gb up to a week or two ago when i received a balloon warning informing me that my hard disk was full. I checked the disk using "Diskview" and 79% of the capacity was filled with .BAK. This is i am told is a Backup file extension. How has this happened,and how do i recover the 43Gb lost. ?
Any info would be greatly appreciated.
.bak is the extension used to identify backup files. Is this a single .bak file that is reportedly taking up the space, or multiple .bak files? If it's only a single file, that would almost cetainly point to some corruption with your filesytem; .bak files just simply do not get that large.
Try to check your drive for (and correct) filesystem errors; instructions for doing so in XP are given here:
I checked the disk re your advice but still no joy. On the CHKDsk printout i have 19542 fragments using up 42.98 GB. There is a number SO39591 Prefix.
S03591.BAK. This is huge in comparison to the full file breakdown.
On the disk defrag printout it is as follows.
Volume HDD (C)
Volume size 53.94GB
Cluster size = 4KB
Free space = 520MB
Percent free space =0%
Total files 123,371
Ave file size 961Kb
Total fragemeted files 2570
Total excess fragments 26500
File Fragmentation =84%
Free space fragmentation= 12%
Excess folder fragments=304
Master file fragmentation
Total MFT size 146Mb
MFT record count=130,175
Percent MFT in use=87%
Total MFT fragments =86
Any ideas from this info? :!:
At this point you should seriously think of backing up your critical data before proceeding with further repairs!!
I checked the disk re your advice but still no joy.
Did the disk repair fail or refuse to run, or did it appear to run but just not fix anything?
- If it failed, please tell us the exact errors (if any) that you received.
- If it did run, did you make sure to check the "automatically fix file system errors" and "scan for and attempt recovery of bad sectors" option boxes?
Try a disk defrag if you haven't already. The amount of fragmentation reported in your printout may be inaccurate due to disk corruption, but if those numbers are correct, you have an extremely fragmented drive.