locked
SYS VOL is Full RRS feed

Answers

  • This is not normal. Please file a connect bug (I believe one exists already. If so, add to it).

    There could be two issues:

    1. The logs under C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\Logs could have grown too big.

    2. Desktop search index has grown too big (known Beta issue) - do you have a huge number of files in the shared folders?

    You may try deleting log files from C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\Logs  or copying it elsewhere. We would be interested to see why the log file grew this big (normally it happens in case of repeating errors). So please add to the connect bug.

    Monday, March 19, 2007 6:07 PM
    Moderator

All replies

  • This is not normal. Please file a connect bug (I believe one exists already. If so, add to it).

    There could be two issues:

    1. The logs under C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\Logs could have grown too big.

    2. Desktop search index has grown too big (known Beta issue) - do you have a huge number of files in the shared folders?

    You may try deleting log files from C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\Logs  or copying it elsewhere. We would be interested to see why the log file grew this big (normally it happens in case of repeating errors). So please add to the connect bug.

    Monday, March 19, 2007 6:07 PM
    Moderator
  • Before I file a connect  bug...

    My log file is only 15.6MB. I only have 9.85GB shared out.

    Update...  I look into the index and you are right, the index grew too big. What I am going try to do is move the index location to the D drive. Let's see what happen. I will keep you guys updated.

    Thanks

     

     

    Monday, March 19, 2007 8:26 PM
  • Well it seems like its working. I created a new folder in D drive called index_new, and I rebooted the WHS, and let it do its things for about 30mins or so. And... Woohoo!!! I have 5.97 GB of free space.

    Now I am just wondering; should I be deleting the old index from the sys vol?

    And Dileep K THANK YOU!!!!!!!!!! And here I thought I would have to reformat... again... phew...

    Oh.. Still file connect bug??? 

     


     

     

    Monday, March 19, 2007 9:06 PM
  • You are welcome!

    No, you don't need to file the bug since it is a know issue.

    Thank you.

     

    Monday, March 19, 2007 9:50 PM
    Moderator
  • I have over 6Gb of files in C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\Logs  am I ok to delete them?

     

    Do you have the details of the connect bug so that I can add to it?

     

    Cheers

    Jack

    Monday, May 21, 2007 9:54 PM
  • I did not filed a bug at at. Even so that was at Beta 2 stage. You will need to log at new bug at connect. Be sure to include the TalQ for server and client. Otherwise, WHS team will not be able to do anything. You should try moving your index location as above. I don't see the harm of deleting the logs files.
    Tuesday, May 22, 2007 12:04 AM
  • Most probably, the biggest logs are QSM.log and Transport.log, possibly q_de.log

     

    This bug has been filed, so no need to add to it. You may safely delete these logs (as per the procedure that I outline below) if you are not planning to file any issue that occured during the time period until you delete them. For bugs to be investigated properly, we need the logs. If you do not have any bugs to file until now, please follow the steps below to get rid of the logs:

     

    1. Close Admin Console if it is open

    2. From command prompt, type net stop qsm , type Y when asked.

    3. Delete Qsm.log & q_de.log

    4. From command prompt, type net stop whstransportservice

    5. Delete all Transport.mmddyy.log files

    6. From command prompt, type net start qsm

    7. From command prompt, type net start whstransportservice

     

    Enjoy your new space Smile

    Tuesday, May 22, 2007 6:54 PM
    Moderator
  • Dileep,

    I had the same problem and your good, detailed instrucitons fixed my system too!  Thank you very much for providing this informaiton.  I linked to this thread from another thread on this subject so as many others as possible could benefit from your knowledge of how WHS works.  Here is that link.

     

    Thanks again, and

     

    Best regards,

    Thursday, May 24, 2007 2:05 PM
  • I have a RTM version and all of the sudden I have no space on my C partition.  I have HUGE log files in the "application Data\Microsoft\Windows Home Server" directory.

     

    Can I deleate all of these and what caused these?

     

    thanks,

     

    Malcolm

     

    Monday, February 18, 2008 11:27 PM
  • Read the messages above about deleting log files.
    Tuesday, February 19, 2008 1:04 PM
  • So I delete the log files and they keep reappearing.

     

    I cannot open the huge files but I did open the q_de.log file and it shows as an example:

     

     

    CORE:  02/20/2008 06:35:55:625: Expected c:\fs\4\DE\shares\Spain Photos\Suzanne Photos\DSCN0774.JPG(id = 4000000000f1e) to be in the reparsepoint entries in D:\shares\Spain Photos\Suzanne Photos\DSCN0774.JPG

     

    This file no longer exists on the Server but could be the cause of my problem.

     

    Question is how to fix it?  Some of these log files as 400MB...

     

    thanks,

     

    Malcolm

    Thursday, February 21, 2008 3:47 AM
  • Also, how do you move the index?  I did a search and could not find anything.

     

    BTW this is not a Beta copy but the full release...

     

    thanks,

     

    Malcolm

     

    Thursday, February 21, 2008 3:49 AM
  • Same problem here. File chkdsk_c__fs_N.log consumes ALL aviable space on C: drive. As I delete any file on drive, it immediately grows in size, keeping 0 B free space. File cannot be deleted even when directions posted at May 22/2007 were followed. File can be deleted after system restart, but in some time it is back (routine checkup starts again?).

    File path: C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\logs\chkdsk_c__fs_N.log
    Windows version: 3790.srv03_sp2_gdr.090805-1438

    I have 5 drives in my server, so I'm not comfortable with recommended solution to scan drives in other PC - while I'm not sure which drive causes problem.

    Thursday, January 28, 2010 10:00 PM
  • Hi,

     

    I am having exactly the same problem, my system volume runs out of space, because a file called chkdsk_c__fs_H.log is eating up all my diskspace.

     

    I checked all drives individually in another system, no errors.

     

    I also run checkdisk manually on C:\fs\H (I assume this is the share the logfile refers to), but it works flawlessly.

     

    Here are some contents from that huge file (I have split before), looks like chkdsk is running over 100%:

     

    7010 Prozent abgeschlossen. (33052011 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052012 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052013 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052014 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052015 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052016 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052017 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052018 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052019 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052020 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052021 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052022 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052023 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052024 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052025 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052026 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052027 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052028 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052029 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052030 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052031 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052032 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052033 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052034 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052035 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052036 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052037 von 398272 Indexeintr„gen verarbeitet)
    7010 Prozent abgeschlossen. (33052038 von 398272 Indexeintr„gen verarbeitet)

     

    It's going on like this all the time.

     

    Now, in order to prevent that from happening again, please help:

    - when is chkdsk automatically scheduled? Can I start this task manually to see if the problem has gone?

    - can I configure chkdsk not to run at all, or only run when I want it to? Since it seems to be absolutely unreliable, I don't wanna have such a process blocking my whole system!

    - will this ever be fixed by Microsoft?

    - can I configure a maximum logfile size for chkdsk?

     

    This is really an annoying issue, so please help.

    Sunday, February 20, 2011 8:02 AM