"not enough contiguous free space" report in Disk Warrior

Hi
When i do my periodic disk warrior maintenance checks it tells me
that "there is not enough contiguous free space to guarantee a safe rewrite"
It actually does complete the procedure without any proble but i am concerned about the issue of not having enough contiguous free space.

The threads about optimization and defragmentation are hugly polarised and its difficult to really know what i should do or if i should be worried.

I do have idefrag but have as yet been hesitant to use it.

Could anyone tell me some info about this contiguous free space issue and the best route to follow. It does seem wired that none of my free space is bigger than (12?)mb
or whatever it is disk warrior is reporting.

thanks for your time

d

eMac 800MHz Power PC G4 Superdrive, Mac OS X (10.3.9), LACIE X3 - 160GB & 250GB external HD - 1 external burner - 750MB RAM

Posted on Sep 23, 2007 3:22 PM

Reply
12 replies

Sep 24, 2007 4:52 AM in response to didier tickell

Are you sure Disk Warrior is saying "there is not enough" or that it is informing you that it requires 12 MB to perform the operation. It is a subtle difference, where the 'informative' can be misread as reporting a limitation.
Other's using DiskWarrior have reported the same concern but have still been able to perform the operation as you have.
For example, if you were installing software, and you were presented with a message that said "Warning: This software requires 50MB of disk space to install successfully." The message may appear as if you don't have that amount, when in fact you do.

Sep 24, 2007 5:28 AM in response to roam

Hi
Yes you are right - disk warrior does complete the process despite reporting the lack of contiguous free space.
But it's the fact that it reports it that concerns me.

1. see this thread elsewhere which starts off discussing exactly this issue:
http://www.daniweb.com/forums/thread9705.html
"Danarchy" the thread poster describes pritty much the disk warrior messages i get.

2. this is the only ref i have come accross in apple discussions where Kenichi Watanbe makes the following reference to it in the 3rd post down :
"Mac OS X uses free space for it's virtual memory swap file. It works most efficiently if there is sufficient contiguous free space."

3.Here is a more opinionated view of the issue in Section 6 : Defragment A Hard Drive That Is Low On Free Contiguous Space
http://www.macattorney.com/ts.html

When i ran the SHOWVOLUMEFRAGMENTATION app it recommends it says that
88% of my all my disk fragments are below 1mb in size - which i think is alarming.
It still says, however, this is okay for office type work but not audio/visual work.

The whole subject is discussed generally in quite a confusing way with some talk very fuzzy and unclear and others very certain - but from what i can see above - i would need to address the contiguous free space issue and also address the fragmentation issue - it's just funny that all things apple are somehow ellusive on this point when it seems obvious to ask the question why when it obviously can matter where many creative people specifically use macs?

d

Sep 24, 2007 5:46 AM in response to didier tickell

I have had no problem with defragmented disk space or any other disk space. It is a complexity that Diskwarrior creates through the ambiguous use of language that is causing the confusion.

You can put this issue to bed by using SuperDuper to clone your internal to your 250GB external, check that the external clone boots. Erase the volume on the internal and then clone it back again. In doing that you will eliminate all fragmentation and all remaining space will be 100% contiguous. Then run Disk warrior again and it will likely come up with the same message, which as this point will be proved erroneous.

I don't think you need to do that, but if you really want to nail it, that would be the procedure to follow.

Sep 25, 2007 8:39 AM in response to didier tickell

Hi, didier tickell. It may be too obvious to be worth mentioning, but have you asked Alsoft exactly what the message signifies and whether you need to do anything about it? I've always found Alsoft tech support to be responsive, helpful, and exhaustively knowledgeable, even if it often takes two or three days for them to respond to an email. In your case it sounds as though time isn't of the essence anyway, so why not drop them a line?

http://www.alsoft.com/DiskWarrior/support.html

Sep 25, 2007 9:38 AM in response to eww

Hi
re: i did contact alsoft and they said what i mentioned above - that i needed to sort out the fragmentation of my disc's free space.

However i have resolved the issue this way:
1. I used ShowVolumeFragmentation free ware to see level of fragmentation.
2. I used idefrag to confirm the above results.
3. I used Superduper to clone internal boot to external drive- took about 70mins
4. I used idefrag on the clone on 'full defrag' option - about 3 hrs
5. I cloned back the clone to internal - about 70mins.

effortless

My final opinion about the whole thing is fragmented free space DOES crop up as an inhibitor of software processess, particually around the use of video, photography & audio creating software in general and maintenance programmes which utilize free space to complete their procedures.
To my mind, logically, it is better to compose some kind of defrag routine into your maintenance procedures if you use your mac in these areas. Superduper and idefrag have provided me with a good defrag procedure for my specific needs. I think each person's needs may be different and the topic 'defragmentation' hides different issues & is not so striaght forward on Macs.

Sep 25, 2007 10:42 AM in response to didier tickell

Glad that worked for you, didier. But for future reference, you could have saved at least that 3 hours of defragmentation time. By cloning your drive to a blank external drive, it was already defragmented since the OS will always write each file to the next contiguous space. All you had to do after making sure the external would boot was to clone it back.

Also, there's really no distinction between fragmented data and fragmented free space. If one is fragmented, so is the other. That is, saying the free space is fragmented is not somehow worse than the data being fragmented.

Sep 25, 2007 11:05 AM in response to Kurt Lang

point taken
: but the Superduper manual suggests that idefrag would be more thourough at defragging than that which occurs when making a clone with Superduper - hence me idefragging the clone as they recommend. Also i had the time to give.
: regards fragmented free disk space - as opposed to fragmented file pieces - they are not the same in that the gaps between the fragmented files or file-clusters may vary in size. In my case no fragmented free space available was greater than 1mb in size on inspection. ie the fragmented free space had fractured into hundreds of really tiny-weeny chunks throughout the drive - I've had my emac for 4 years and it's never been defragged & loads of video work - so perhaps thats why the free-space was so fragmented. This was why disk warrior and techtool deluxe could not complete - because the contiguous free space was non-existant - not even able to produce a 5mb chunk of contiguous free space - so problems arouse. I agree that maybe for the average user - general fragmented free space will have alot of varied sizes of contiguous chunks which are totally adequate - but in my case, i saw that even those had broken down to tiny bits.
d

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

"not enough contiguous free space" report in Disk Warrior

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.