Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Fix So WHS And WHS Clients Report Correct Free Disc Space RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

     

    At present it seems if your WHS has more than one drive fitted, Microsoft Windows client PC's will see an incorrect (low) value for availble free disc space and also and incorrect value for disc space used.

     

    The only place to check the correct value at present is by loading the Home Server Console.

     

    WHS needs to correctly report to the Windows Operating System the correct values thus making operation more logical.

     

    This would help...

    1. Avoid bogus errors when you try and copy files on to the server and Windows reports "not enough free space".

    2. Ease of managing disc space.

    3. Reduce end user confusion.

     

    Of course, it would seem logical to me that the product should have done this from day 1 and can think of no reason why it does not....

     

    IM35461

    Friday, August 8, 2008 8:45 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually, it is most likely correctly reporting the amount of free space, just not where yoiu think it 'should be':
    The server (and, by extention, any PC that's trying to copy data to it) is reporting the amount of free space in the 'landing zone' on the primary hard drive.
    Data is not copied directly to the shares; rather, it's copied to the landing zone.  The migrator service (a part of WHS) then moves the data from the landing zone, to the target folder in the shared folders.

    A good read for you would be the Drive Extender white paper.

    A question for you:  how many drives do you have, and what are the sizes of each (notably, what's the size of the system drive?)
    How large is the file (or, group of files) that you're trying to copy to the server when it pukes?

    Saturday, August 9, 2008 5:13 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually, it is most likely correctly reporting the amount of free space, just not where yoiu think it 'should be':
    The server (and, by extention, any PC that's trying to copy data to it) is reporting the amount of free space in the 'landing zone' on the primary hard drive.
    Data is not copied directly to the shares; rather, it's copied to the landing zone.  The migrator service (a part of WHS) then moves the data from the landing zone, to the target folder in the shared folders.

    A good read for you would be the Drive Extender white paper.

    A question for you:  how many drives do you have, and what are the sizes of each (notably, what's the size of the system drive?)
    How large is the file (or, group of files) that you're trying to copy to the server when it pukes?

    Saturday, August 9, 2008 5:13 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
     cuppie wrote:

    A question for you:  how many drives do you have, and what are the sizes of each (notably, what's the size of the system drive?)
    How large is the file (or, group of files) that you're trying to copy to the server when it pukes?

     

    My unit had 1 x 500Gb SATA drive and last week I fitted another one the same size. The system partition is the standard 20Gb of this first drive.

     

    The first drive at that time had 45Gb of true free space when I added the new drive and now reports that it has 48.9Gb of free space.

     

    I have set two of the shares to be duplicated, music files, 42.34Gb and my user files, 12.05Gb.

     

    Other shares are Video, 220.78Gb, Photos, 24.88Gb and PC Backups 72Gb

     

    Since then I created a new share to store the backups of SDHC cards from my HD Camcorder which I have been storing on antother PC.

     

    When I tried to move the first 50Gb of these to the new share Windows said "Not Enough Space". I get the idea about the tombstones on the firs drive actually pointing to where the data is actually stored but still cannot see why the operating system can't report the total array space.

     

    Even now my system reports 44Gb free to the operating system but the WHS console says I have 399Gb free

     

    1st Drive is 89% physically full and second is 24% physically full (according to 3rd party add-in).

     

    Last storage balance was one hour ago.

     

     

    Saturday, August 9, 2008 7:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Quick math says that those numbers are just about right - your client PC is (correctly) seeing that the space available in the landing zone exceeds the space needed for the copy operation; therefore, the operation fails. 
    Always remember this:  data is not copied directly to the shares.  It must first be copied to the landing zone (which is on the primary hard drive; your primary only has ~11% available); DEMigrator then moves the data to the target shared folder.
    There's no point in the client 'seeing' the total free space available on the WHS, as the data doesn't go directly to that 'total' free space.

    One question:  have you yet installed Power Pack 1 on your WHS?

    Never mind - I went looking for another post (I had a good analogy there), and the realized that is was also your thread.
    Cross-post! 
    http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=3719513&SiteID=50
    Grr.

    Tuesday, August 12, 2008 3:20 AM