disk space analyzers and FDISR

Discussion in 'FirstDefense-ISR Forum' started by ashwin, Oct 28, 2008.

Thread Status:
Not open for further replies.
  1. ashwin

    ashwin Registered Member

    Joined:
    Feb 17, 2005
    Posts:
    66
    Hello

    I am using FDISR 3.21 build 205.

    This must be simple,
    but I don't know how to view and plan for my disk usage.

    Question 1:
    Will any of the common disk space analyzers work with FDISR?
    Will they view the entire hard drive or just within the snap
    they are installed in?
    I am considering
    Space Monger ( http://www.snapfiles.com/get/spacemonger.html ) or
    Win Dir Stat ( http://windirstat.info/ ).

    Question 2:
    Will the disk space analyzers let me see the specific files
    taking up the space within any snapshot?

    Question 3:
    Are the readings from the FDISR data section window
    the size of the original snapshot at the time it was created, or
    are they the current size including recent installs?

    If anyone can see what I am not adding correctly please let me know:

    FDISR stats
    primary snap: 9 gigs
    test area snap: 9 gigs
    work area snap: 48 gigs

    anchored is my docs with 22 gigs

    The total from above is 88 gigs.

    My hard drive is 142 gigs, so I was expecting to find about
    54 gigs remaining, but when I go to My Computer--> properties,
    I only have 7 gigs of space left.

    I'm curious what the 48 gig work area is composed of, and if
    somehow another copy of "my docs" in saved there...

    Thanks

    Ashwin
     
  2. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,042
    First what are the spec's on the hard drive. For example on one of my machines, I have two 250gig hard drives in a raid 0 config which yields 500g. But the reality is there is only 465gig. The reason for this is well documented.

    Also we need to know, what was the space on the drive before you installed FDISR and what happened as you added snapshots.

    Pete
     
  3. ashwin

    ashwin Registered Member

    Joined:
    Feb 17, 2005
    Posts:
    66
    Thanks Peter.

    I have a hard drive with no partitions and no raid.

    I installed FDISR and made the primary snap 228 days ago. I have not placed anything else on that snapshot.

    Both the primary and the test snapshot are still rated at 8.84 gigs, but I installed a small graphics program in the test snap, so those figures should no longer be exactly equal.

    Does that mean my work area snap could be a lot larger than what is given in the FDISR window?

    I have not been watching the gig figures for the working snapshot, as I thought by anchoring the "my docs" I still had plenty of space left.
     
  4. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,042
    But I still don't know any more than I did before. Do you know what the space situation was at each step?
     
  5. ashwin

    ashwin Registered Member

    Joined:
    Feb 17, 2005
    Posts:
    66
    No, I do not know the space situation at each step.
     
  6. Peter2150

    Peter2150 Global Moderator

    Joined:
    Sep 20, 2003
    Posts:
    17,042
    What about the size of your drive and the space situation before installing FDISR. Without some of this short of closely examining your drive, it's going to be real hard to say.

    Pete
     
  7. ashwin

    ashwin Registered Member

    Joined:
    Feb 17, 2005
    Posts:
    66
    As I was going to delete the small "test area" snapshot, I right clicked on it and saw the option to get the update on the size of the snapshot.

    My Test Area snap had grown to 17 gigs, and my Work Area snap had decreased in size.

    I also took a look at Win Dir Stat data. Again, I was on the learning curve for that software, but I did notice that the figures for "preload drive C" changed as I went from my Work Snap to the Test Snap. It decreased by 8.8 gigs- the size of the primary snap.

    At least I can report that the WDS was reading something, and it did not crash the system.

    I deleted the Test Area snap, defragged, and have 30 gigs to work with instead of 5-7gigs.

    BTW I started with Ultimate Defrag, but it seemed to hang. It is the second time I noticed it (the first time was on my older laptop). I finished the defrag with the Disk Keeper lite that came bundled with the computer.

    Thanks

    Ashwin
     
Thread Status:
Not open for further replies.