drmike
100% Tier-1 Gogent
So, you bought one of those super duper under-priced and guaranteed to be oversold VPS packages. You know, one of those featuring 50GB, 100GB or even more disk space.
Wisely, you bought it on a special, and now are letting it idle and season to see if it is reliable before deploying it.
All while your provider is busy noticing the node is empty, the CPU is idle and continues to oversell the server more.
Or perhaps your provider lost your data, took ten days to reply to tickets and finally informed you that you are screwed, the data is gone.
What to do? Claim some of your resources for the rest of your stay as a customer: Consume disk, eat up your backup space, etc.
sudo su
mkdir /home/workfiles
cd /home/workfiles
dd if=/dev/urandom of=/home/workfiles/music_edit1.wav bs=100M count=100
What we are doing:
sudo su = become root
mkdir /home/workfiles = creating a new directory under /home for our stash files
cd /home/workfiles = changing to our newly created directory
dd if=/dev/urandom of=/home/workfiles/music_edit1.wav bs=100M count=100
- this creates a file from random data (/dev/urandom). The file is 100M in chunk size before the write to disk happens. We keep this small so as to not run out RAM. We do 100 of these to create a 10GB file.
Outcome: We just chewed up 10GB of disk space or reserved it for your future use.
To reserve larger blocks of disk space for later use, adjust the count= to larger values (i.e. 200 = 20GB) or smaller values (i.e. 50 = 5GB). Be sure to adjust the of= end file name for each file (i.e. /home/workfiles/music_edit2.wav).
I'd create a number of these files so you can "recover" disk space as needed. For instance, if you have 50GB of disk:
Create files that are 5% of total available disk in size or 2.5GB per file.
music_edit1.wav
music_edit2.wav
music_edit3.wav
music_edit4.wav
music_edit5.wav
music_edit6.wav
music_edit7.wav
music_edit8.wav
music_edit9.wav
music_edit10.wav
=================
10 files @ 2.5GB each = 25GB or 50% of the available storage provided in your package.
When you decide to put your VPS to regular good use and need disk space, delete reserved space files as needed.
Yes, you can create one big reserve file (say if 50GB of disk allocated, create a 40GB single file).
Note:
Since we are populating these files with random data, the files will not show any size in savings when compressed. Meaning backups and other disk reduction methods will not succeed in reducing your use footprint. You will use every byte of disk you have reserved in these files on that disk and same will be true of the provider backups.
Wisely, you bought it on a special, and now are letting it idle and season to see if it is reliable before deploying it.
All while your provider is busy noticing the node is empty, the CPU is idle and continues to oversell the server more.
Or perhaps your provider lost your data, took ten days to reply to tickets and finally informed you that you are screwed, the data is gone.
What to do? Claim some of your resources for the rest of your stay as a customer: Consume disk, eat up your backup space, etc.
sudo su
mkdir /home/workfiles
cd /home/workfiles
dd if=/dev/urandom of=/home/workfiles/music_edit1.wav bs=100M count=100
What we are doing:
sudo su = become root
mkdir /home/workfiles = creating a new directory under /home for our stash files
cd /home/workfiles = changing to our newly created directory
dd if=/dev/urandom of=/home/workfiles/music_edit1.wav bs=100M count=100
- this creates a file from random data (/dev/urandom). The file is 100M in chunk size before the write to disk happens. We keep this small so as to not run out RAM. We do 100 of these to create a 10GB file.
Outcome: We just chewed up 10GB of disk space or reserved it for your future use.
To reserve larger blocks of disk space for later use, adjust the count= to larger values (i.e. 200 = 20GB) or smaller values (i.e. 50 = 5GB). Be sure to adjust the of= end file name for each file (i.e. /home/workfiles/music_edit2.wav).
I'd create a number of these files so you can "recover" disk space as needed. For instance, if you have 50GB of disk:
Create files that are 5% of total available disk in size or 2.5GB per file.
music_edit1.wav
music_edit2.wav
music_edit3.wav
music_edit4.wav
music_edit5.wav
music_edit6.wav
music_edit7.wav
music_edit8.wav
music_edit9.wav
music_edit10.wav
=================
10 files @ 2.5GB each = 25GB or 50% of the available storage provided in your package.
When you decide to put your VPS to regular good use and need disk space, delete reserved space files as needed.
Yes, you can create one big reserve file (say if 50GB of disk allocated, create a 40GB single file).
Note:
Since we are populating these files with random data, the files will not show any size in savings when compressed. Meaning backups and other disk reduction methods will not succeed in reducing your use footprint. You will use every byte of disk you have reserved in these files on that disk and same will be true of the provider backups.
Last edited by a moderator:
)
