Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'A possible fix for 'overlapped extent allocation' errors' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A possible fix for 'overlapped extent allocation' errors
Authored by: dashard on Apr 04, '03 09:27:17PM

How about a shell script to list the 'inum' followed by the path to what was found and put it in a text file at ~/Desktop. This way one could see what was what and then determine the best course of action without having to slog through the error numbers one at a time??

Anyone??



[ Reply to This | # ]
A possible fix for 'overlapped extent allocation' errors
Authored by: webmonster on Dec 10, '03 07:00:58PM
This is UNTESTED, so USE AT YOUR OWN RISK (in other words, it may require minor tweaking, but it's at least some starting point - it is not elegant at all)

for num in `fsck -n / 2>&1 | grep "Overlapped extent allocation" | cut -d'(' -f2 | cut -d' ' -f2 | cut -d'd' -f1 ` ; do find / -inum $num ; done > /OverlappedExtentAllocations.txt

This should produce a file in your boot volume's root directory.

I had the overlapped extent problem right now, but I cured it quick because I moved several files to a different disk before running fsck, so I didn't really try the script above.

Maybe it helps.

Regards, /k

[ Reply to This | # ]

A possible fix for 'overlapped extent allocation' errors
Authored by: johnsawyercjs on Dec 11, '03 02:25:43AM

Diskwarrior will list overlapped files by name, as long as it doesn't choke on the diagnosis phase. Use version 3, it's much faster than version 2, and boot from the Diskwarrior 3 CD, since DW 3 doesn't work yet under OS 10.3.x.



[ Reply to This | # ]