# Disk has now run out of space, even though allocated storage was set? **URL:** \ **Category:** troubleshooting\ **Tags:** windows, hardware\ **Created:** [November 8, 2023, 7:39pm UTC](https://forum.storj.io/t/disk-has-now-run-out-of-space-even-though-allocated-storage-was-set/24293 "2023-11-08T19:39:23Z")\ **Posts on this page:** 1\ **Showing post:** 27
**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\ **Post date:** [July 28, 2024, 4:20am UTC](https://forum.storj.io/t/disk-has-now-run-out-of-space-even-though-allocated-storage-was-set/24293/27 "2024-07-28T04:20:31Z")
> [@miicar204](#): > > logfile not self cleaning… It will not clean itself, you may setup a logrotate > [@How to create daily storagenode logs](https://forum.storj.io/t/topic/6199/5): > > are you running in a NAS or Windows or Linux? In Ubuntu I use the “logrotate” command in a cron job to create/compress log files. First you have to make sure you have added in the “Log Location” and “Log level” fields in the “config.yaml” Then look in the “/etc/logrotate.d/” folder, you’ll see a list of files, those are the configs used to rotate logfiles ( usually found in “/var/log/”). I just put a “storj” config file in the logrotate.d/ and it’s done automatically To rotate my logs i use … or use a custom script: > [@Native logs rotation in Windows with a simple PowerShell script](https://forum.storj.io/t/topic/6241/1): > > Hello, Unfortunately, in the current windows version of the Storage Node there is no way to rotate or limit the size of the generated logs files. You cannot delete them from the GUI because they are locked by the services processes. Using Clear-Content in PowerShell to reset the files works but there is no easy solution if you want to keep a few days / weeks of logs. I have written a small PowerShell script that can rotate the Storjs Logs without the need of Stop\>Start the services to release … > [@miicar204](#): > > the inflating disk, way above allocation This is mean that the usage in the databases is incorrect. To fix it you need to have an enabled scan on startup (it’s enabled by default) and restart the node, to track the progress of the used-space-filewalker: > [@Storagenode.exe stopping for too long, for 10h+](https://forum.storj.io/t/topic/25316/12): > > Windows/PowerShell Logs should be at least info level Used space filewalker Regulated by the parameter in the config.yaml file or as a command line argument (add -- before the parameter, remove :, place it after the image name in your docker run command): # if set to true, all pieces disk usage is recalculated on startup (default true) storage2.piece-scan-on-startup: true to watch for a progress: cat "C:\Program Files\Storj\Storage Node\*.log" -Wait | sls "used-space-filewalker" | sls "sta… Make sure that you do not have errors related to the filewalker (search for `error` and `filewalker`) and/or the databases (search for `error` and `database`). --- _[View the full topic](https://forum.storj.io/t/disk-has-now-run-out-of-space-even-though-allocated-storage-was-set/24293)._