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


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Backup failing (flaky CIFS mount)

Backup failing (flaky CIFS mount)

Scheduled Pinned Locked Moved Solved Support
backupshetznermountsshfs
26 Posts 7 Posters 3.4k Views 7 Watching
  • 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.
  • girishG girish

    @nebulon Maybe https://askubuntu.com/questions/1210867/remount-cifs-on-network-reconnect ? (just expands on your link)

    imc67I Offline
    imc67I Offline
    imc67
    translator
    wrote on last edited by
    #21

    @girish & @nebulon any news on this issue?

    I started yesterday to backup via cifs to a Hetzner storagebox (2 backups a day), today the first backup failed due to

    Command failed with exit code 1 (EPERM): df -kPT /backups_cifs
    

    I solved it with a manual:

    sudo umount /backups_cifs
    sudo mount -a
    

    But do I need to script this with a daily cron or is Cloudron able to recover from this somehow?

    P 1 Reply Last reply
    0
    • imc67I imc67

      @girish & @nebulon any news on this issue?

      I started yesterday to backup via cifs to a Hetzner storagebox (2 backups a day), today the first backup failed due to

      Command failed with exit code 1 (EPERM): df -kPT /backups_cifs
      

      I solved it with a manual:

      sudo umount /backups_cifs
      sudo mount -a
      

      But do I need to script this with a daily cron or is Cloudron able to recover from this somehow?

      P Offline
      P Offline
      p44
      translator
      wrote on last edited by p44
      #22

      @imc67 Dear, this happened because Hetzner did some maintenance on their Box Service.

      Also a Cloudron restart solved problem.

      nebulonN 1 Reply Last reply
      0
      • P p44

        @imc67 Dear, this happened because Hetzner did some maintenance on their Box Service.

        Also a Cloudron restart solved problem.

        nebulonN Offline
        nebulonN Offline
        nebulon
        Staff
        wrote on last edited by
        #23

        @p44 actually I hit the same thing today morning, had to remount the disk. I happily ignored the heads up warning email about the maintenance from hetzner 😉

        P 1 Reply Last reply
        1
        • nebulonN nebulon

          @p44 actually I hit the same thing today morning, had to remount the disk. I happily ignored the heads up warning email about the maintenance from hetzner 😉

          P Offline
          P Offline
          p44
          translator
          wrote on last edited by p44
          #24

          @nebulon Yes, but not all my Cloudron installs has been affected, even if attached at the same Hetzner Box... Just restarted and all was operational again 🙂

          nebulonN 1 Reply Last reply
          0
          • P p44

            @nebulon Yes, but not all my Cloudron installs has been affected, even if attached at the same Hetzner Box... Just restarted and all was operational again 🙂

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #25

            @p44 in such cases a remount alone would be enough, no need to reboot the whole server, if that is what you did. This would then not affect downtime. We will soon implement auto-remounting in such cases.

            P 1 Reply Last reply
            5
            • nebulonN nebulon

              @p44 in such cases a remount alone would be enough, no need to reboot the whole server, if that is what you did. This would then not affect downtime. We will soon implement auto-remounting in such cases.

              P Offline
              P Offline
              p44
              translator
              wrote on last edited by
              #26

              @nebulon Yes before rebooting I tried to umount-remount but it seems it has been impossible due to an error... So I decided to restart.

              About auto-remounting it will be an amazing feature

              1 Reply Last reply
              1
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • Bookmarks
              • Search