Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Space usage not showing after moving data to a different directory and back

    Nextcloud
    graphs disk usage
    3
    6
    213
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      msbt App Dev last edited by girish

      I've moved my nextcloud data around (changed resources directory to a different path and then later back to the original) quite some time ago and it still only shows 4kb of data, but it should be around ~35gb or something. Any ideas why that might be?

      1 Reply Last reply Reply Quote 0
      • girish
        girish Staff last edited by girish

        @msbt I assume you are referring to the graphs? If so, they are only calculated once a day to reduce disk churn.

        Maybe we can add a button to say "refresh stats" or something but it's a bit tricky since this is done internally by collectd.

        d19dotca 1 Reply Last reply Reply Quote 1
        • M
          msbt App Dev last edited by

          talking about the system info tab, but as I said, that was more than a week ago, so it should have definitely be scanned by now

          1 Reply Last reply Reply Quote 0
          • d19dotca
            d19dotca @girish last edited by

            @girish It would be nice to have a way to manually enforce a re-sync of the data.

            --
            Dustin Dauncey
            www.d19.ca

            1 Reply Last reply Reply Quote 0
            • M
              msbt App Dev last edited by

              would be nice indeed. nextcloud just got updated and it seems to work again, so i guess this is "solved" 😉

              1 Reply Last reply Reply Quote 0
              • girish
                girish Staff last edited by

                Just leaving a note for myself, but it's unclear why the issue got fixed after the update. After an app update, the container is recreated and the collectd config is regenerated. Maybe the collectd restart did the trick.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Powered by NodeBB