 |
 |
Overlapped Extent Allocations
|
|
|
|
|
Mac Elite
Join Date: Sep 2000
Location: Canada
Status:
Offline
|
|
So, fsck reports 16 overlapped extent allocations, and DiskWarrior's going to take roughly 3 or 4 days to fix 'em all (I let it go for 36 hours and it was up to only 9 overlaps detected). Well, I couldn't let the app run for much longer, so I used a command to identify the files affected by this corruption, and I noticed that the entry "/: /dev/fd/4: No such file or directory" shows up in almost every instance. Notice that this is different from "/dev/fd/4" which actually exists.
Can anyone tell me why such entries are found and what I can do about them? My initial hope was to find the corrupt files, delete them and then run DiskWarrior again, but if the entry doesn't actually exist, am I resigned to letting DiskWarrior run over a very long weekend?
|
|
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Sep 2000
Location: Canada
Status:
Offline
|
|
|
|
|
|
| |
|
|
|
|
|
|
|
Forum Regular
Join Date: Mar 1999
Location: Union,MO,USA
Status:
Offline
|
|
Let Disk Warrior do it's thing.
|
|
It is better to light one candle than to curse the darkness
|
| |
|
|
|
|
|
|
|
Mac Elite
Join Date: Apr 2001
Location: Frickersville
Status:
Offline
|
|
When I have disk problems like that I:
1) junk Mac OS X. And I mean all of it (apple apps, system, bin, sbin, etc.) It is the reason diskwarrior is going to take forever because of all the files it installs.
2) Use diskwarrior to repair the disk while there are a ton fewer files. You will notice the difference.
3) Reinstall Mac OS X.
|
|
|
| |
|
|
|
|
|
|
|
Professional Poster
Join Date: Jul 2001
Location: New York, NY
Status:
Offline
|
|
yep.
disk utility doesn't seem to be able to fix overlapping extent allocations - you need a better disk repair utility or to backup and do a clean install...
|
|
cpac
|
| |
|
|
|
|
|
|
|
Senior User
Join Date: Apr 2000
Location: Woodridge, IL
Status:
Offline
|
|
Originally posted by forkies:
When I have disk problems like that I:
1) junk Mac OS X. And I mean all of it (apple apps, system, bin, sbin, etc.) It is the reason diskwarrior is going to take forever because of all the files it installs.
2) Use diskwarrior to repair the disk while there are a ton fewer files. You will notice the difference.
3) Reinstall Mac OS X.
Dear God, NO! NEVER do something that will write to disk when you have directory corruption. When it goes to update the directory to delete those files, it could very easily screw it up to the point where the whole drive is unrecoverable.
Let DiskWarrior sit and do its thing. It's much, much better than anything else, including Disk Utility.
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
 
|
|
|
Forum Rules
|
|
|
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
|
|
|
|
|
|
|
Top
