JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser .
overlapped extents - which files?
We don't like Ads much either, but they do help cover the costs of running the site. Please consider turning off your ad blocker. Thank you.
I have some of the dreaded "overlapped extents" that it seems only disk warrior can fix.
How can I identify the files that are affected so that I can see if I can just delete them? What do the numbers mean in the error message?
Checking Catalog file.
Overlapped extent allocation (file 2978884d)
Overlapped extent allocation (file 2988594d)
Overlapped extent allocation (file 2988587d)
Overlapped extent allocation (file 2988593d)
Overlapped extent allocation (file 2988591d)
Overlapped extent allocation (file 2988592d)
Overlapped extent allocation (file 2988590d)
find / -inum xxxx
does the trick.
where xxxx is the number given in the error message (drop the final d)
It takes quite a long time but eventually all my problems seemed to come down to a virex software update!!
Overlapped extent allocation (file 2988594d) /Library/Receipts/V7030402.pkg/Contents/Info.plist
Overlapped extent allocation (file 2988587d) /Library/Receipts/V7030402.pkg/Contents/PkgInfo
Overlapped extent allocation (file 2988593d) /Library/Receipts/V7030402.pkg/Contents/Resources/V7030402.loc
Overlapped extent allocation (file 2988591d) /Library/Receipts/V7030402.pkg/Contents/Resources/V7030402.sizes
Overlapped extent allocation (file 2988592d) /Library/Receipts/V7030402.pkg/Contents/Resources/Welcome.html
Overlapped extent allocation (file 2988590d) /Library/Receipts/V7030402.pkg/Contents/Resources/English.lproj/V7030402.info
OK, i just had this problem too, and found a quick and easy (ish) way to save the files that are affected.
Locate the files using the command outlined above, then copy each file, and delete the origional, broken one. (i did it in the terminal)
The code i used for this was:
sudo -s
chdir <the directory containing the problem file>
cp <file> <file>-copy
rm -r <file>
then, i rebooted in single user mode (command-s immediately after the startup chime), and ran 'fsck -y' , and all was good
(then i rebooted by typing 'reboot')