locked
1TB free space but receiving "Disk Full - Need Additional Space" Error Message RRS feed

  • Question

  • I have 6TB of total space and 1TB of free space on my WHS. But when I try to copy a 50GB file over, I receive an error message saying that "There is not enough free space. You need an additional 13.2GB to copy these files."

    Storage Server panel in the WHS Console shows no useful information, only that there is 977GB of free space, 2.5TB of shared folders, 2.5TB of backups, 30GB for PC backups, and 26GB for system. 

    Using the Disk Management Add-in, I can view usage details on each drive. My main system drive (160GB) is showing 116GB used and only 32GB free. If I connect via Remote Desktop, I can see that the C: partition has 11.2GB out of 20GB free; the D: SYS partition has only 32GB out of 128GB free.

    My question is, why is the D partition so full?  I believe that it is used as a temporary destination prior to moving copied files to other drives, and that is causing this problem. What can I do to free up space on that partition so that I can copy files over?  I copied a couple of 50GB files yesterday with no problem, but today I'm getting this error message.  Any suggestions?

    Thanks,
    -Carlton
    Wednesday, October 29, 2008 1:55 AM

Answers

  • Carlton Bale said:

    I have 6TB of total space and 1TB of free space on my WHS. But when I try to copy a 50GB file over, I receive an error message saying that "There is not enough free space. You need an additional 13.2GB to copy these files."

    Storage Server panel in the WHS Console shows no useful information, only that there is 977GB of free space, 2.5TB of shared folders, 2.5TB of backups, 30GB for PC backups, and 26GB for system. 

    Using the Disk Management Add-in, I can view usage details on each drive. My main system drive (160GB) is showing 116GB used and only 32GB free. If I connect via Remote Desktop, I can see that the C: partition has 11.2GB out of 20GB free; the D: SYS partition has only 32GB out of 128GB free.

    My question is, why is the D partition so full?

    The D partition is used last.  However, if you added files to point of filling up the secondary drives (forcing WHS to use the D partition), then added more hard drives afterward, WHS will not move the data from the D partition.  Is that what happened?

    Carlton Bale said:

    I believe that it is used as a temporary destination prior to moving copied files to other drives, and that is causing this problem.
     

    That is correct.  Your client PCs only see the primary drive (D partition), not the rest of the storage pool.

    Carlton Bale said:

    What can I do to free up space on that partition so that I can copy files over?

    You could try using a tool created by Theo van Elsberg (a fellow WHS user) called LZreallocator.  It's unsupported, but other users have tried it before and it worked for them.  You can download it from here.

    Carlton Bale said:

    I copied a couple of 50GB files yesterday with no problem, but today I'm getting this error message.  Any suggestions?

    Thanks,
    -Carlton


    Wednesday, October 29, 2008 2:56 AM
    Moderator

All replies

  • Carlton Bale said:

    I have 6TB of total space and 1TB of free space on my WHS. But when I try to copy a 50GB file over, I receive an error message saying that "There is not enough free space. You need an additional 13.2GB to copy these files."

    Storage Server panel in the WHS Console shows no useful information, only that there is 977GB of free space, 2.5TB of shared folders, 2.5TB of backups, 30GB for PC backups, and 26GB for system. 

    Using the Disk Management Add-in, I can view usage details on each drive. My main system drive (160GB) is showing 116GB used and only 32GB free. If I connect via Remote Desktop, I can see that the C: partition has 11.2GB out of 20GB free; the D: SYS partition has only 32GB out of 128GB free.

    My question is, why is the D partition so full?

    The D partition is used last.  However, if you added files to point of filling up the secondary drives (forcing WHS to use the D partition), then added more hard drives afterward, WHS will not move the data from the D partition.  Is that what happened?

    Carlton Bale said:

    I believe that it is used as a temporary destination prior to moving copied files to other drives, and that is causing this problem.
     

    That is correct.  Your client PCs only see the primary drive (D partition), not the rest of the storage pool.

    Carlton Bale said:

    What can I do to free up space on that partition so that I can copy files over?

    You could try using a tool created by Theo van Elsberg (a fellow WHS user) called LZreallocator.  It's unsupported, but other users have tried it before and it worked for them.  You can download it from here.

    Carlton Bale said:

    I copied a couple of 50GB files yesterday with no problem, but today I'm getting this error message.  Any suggestions?

    Thanks,
    -Carlton


    Wednesday, October 29, 2008 2:56 AM
    Moderator
  • Olaf:

    Thanks for your suggestion.  I'll give the tool a try.

    In general, I've always had at least 500GB of free space on the server and add new drives when I get close to filling that threshold.  However, it is possible that part of the D: SYS partition was filled during a drive swap and/or failure.  It's very frustrating that WHS doesn't automatically correct this issue!

    I'll let you know how it goes with LZreallocator.

    -Carlton
    Wednesday, October 29, 2008 1:25 PM
  • That solved my problem - thank you!!!  I now have 86GB free out of 129GB.  Which should be enough for anything I do.

    If anyone else experiences this problem, please validate and vote for bug report 354746 on Microsoft Connect.
    Wednesday, October 29, 2008 11:53 PM
  • Carlton Bale said:

    That solved my problem - thank you!!!  I now have 86GB free out of 129GB.  Which should be enough for anything I do.

    If anyone else experiences this problem, please validate and vote for bug report 354746 on Microsoft Connect.


    Rest assured, MS is already aware of the "landing zone" issue.
    Thursday, October 30, 2008 2:27 AM
    Moderator