Uploading backup -> not enough space on disk

support
,
1

I’m trying to upload a 14.4MB backup to my VPS and get this message after 20%

//assets-meta-cdck-prod-meta.s3.dualstack.us-west-1.amazonaws.com/original/3X/6/9/690beb2215180e83a5effd4b472f6095c20d65f9.jpg

this is the output of df though:

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/ploop21283p1 11220208 2410508 8285604 23% /
none 4 0 4 0% /sys/fs/cgroup
none 104860 72 104788 1% /run
none 524288 0 524288 0% /dev/shm
none 5120 0 5120 0% /run/lock
none 524288 0 524288 0% /run/shm
none 102400 0 102400 0% /run/user

What could be the cause of this error?

2

I wonder if there is something wrong with your VPS since this is the second time you have reported unexplainable out of disk errors.

1 Like
3

Try making a backup first on that VPS, then upload the existing one.

  def has_enough_space_on_disk?(size)
    `df -Pk #{Rails.root}/public/backups | awk 'NR==2 {print $4 * 1024;}'`.to_i > size
  end

This function fails when the public/backups directory does not exist (making a backup creates it).
Maybe add another check?

1 Like
4

Hmm, @techapj can you repro that, is this a bug when the folder does not exist?

5

If using Discourse Docker the folder will be there.

1 Like
6

Based on previous discussions I thought @hedgehog is using our official Docker install for his Discourse… perhaps he can clarify on this point?

7

After creating a backup and then uploading the one I want to use I get the message that it uploaded successfully but it never appears in the backup-list. Any ideas?

@codinghorror
After trying the whole weekend I wasn’t able to get Discourse running on the pesky OVH-host so I tried pl3bs’ installation-script. I know I could pay more and get better Discourse-hosting but I’m dead set on the cheap solution just for the sake of beeing able to say “yes, it does work”.

8

Maybe go there for support? Since this clutters meta with all kinds of weird stuff that never happens to other people.