All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Servarica unlimited storage new hdd space check
Hi everybody,
I bought an unlimited storage plan from @servarica_hani . It is a plan where every day you earn 3GB of HDD space and it is applied after a reboot. I tried to check if the 3GB per day are correcly applied to my machine but I think I am using the wrong terminal commands because it is like I don't get 3GBxDay, but less (but I am pretty sure I use the wrong commands). I use the "df" command. As you can see from the screenshot I should get 15GB (5 days without rebooting), instead it looks like I got only 10GB. What command should I use?
Here you can find the terminal BEFORE the reboot:
xxxx@root:~$ date
Wed Sep 13 07:23:39 PM UTC 2023
xxxx@root:~$ uptime
19:23:42 up 4 days, 23:38, 1 user, load average: 0.20, 0.10, 0.03
xxxx@root:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 299564 1132 298432 1% /run
/dev/mapper/ubuntu--vg-lv--root 3588069624 2156622732 1285560608 63% /
tmpfs 1497804 4 1497800 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
/dev/xvda2 1100332 257560 768688 26% /boot
tmpfs 299560 4 299556 1% /run/user/1000
xxxx@root:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 293M 1.2M 292M 1% /run
/dev/mapper/ubuntu--vg-lv--root 3.4T 2.1T 1.2T 63% /
tmpfs 1.5G 4.0K 1.5G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/xvda2 1.1G 252M 751M 26% /boot
tmpfs 293M 4.0K 293M 1% /run/user/1000
Here you can find the terminal AFTER the reboot:
xxxx@root:~$ date
Wed Sep 13 07:32:54 PM UTC 2023
xxxx@root:~$ uptime
19:32:56 up 4 min, 1 user, load average: 0.47, 0.96, 0.47
xxxx@root:~$ df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 299564 1116 298448 1% /run
/dev/mapper/ubuntu--vg-lv--root 3588069624 2156611864 1285571476 63% /
tmpfs 1497812 4 1497808 1% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
/dev/xvda2 1100332 257560 768688 26% /boot
tmpfs 299560 4 299556 1% /run/user/1000
xxxx@root:~$ df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 293M 1.1M 292M 1% /run
/dev/mapper/ubuntu--vg-lv--root 3.4T 2.1T 1.2T 63% /
tmpfs 1.5G 4.0K 1.5G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/xvda2 1.1G 252M 751M 26% /boot
tmpfs 293M 4.0K 293M 1% /run/user/1000
Can someone please tell me what command I should use?
Thank you very much,
Valenerd
Comments
I am kinda curious where do you see that 10GB increase as /dev/mapper/ubuntu--vg-lv--root seems to be the same -
3588069624for both logs.You using supported (theirs) system OS image/template?
Hi JabJab,
thank you for your reply.
I am using their template so it should be a supported OS template. Regarding the space I thought it was increasing because looking at the "available space" it actually increased, but just of 10.868 (I did 1285571476 - 1285560608) that I think it's more or less 10GB. But looking at the "Filesystem 1K-blocks" it remains always the same, you are right.
I don't know if I am missing something or if there is something wrong in my VM.
Thanks,
Valenerd
dfwill show you the size of the filesystem. You need to check it withlsblkorfdisk -lfor example which will show you the size of the attached disk.Thank you for your reply Talistech, unfortunately this is a VPS; I see different HDD. Furthermore I expect that the filesystem should increase after every reboot (this is what servarica claims) so the "df" command should work as well.
Thanks,
Valenerd
Did you reboot from the VPS or from the client area
to get the disk space added you need to issue reboot command from the client area
if that didnt work just open a ticket and the team will resolve it for you but it seems you just need to reoot from client area
Thanks
Hani
Hi @servarica_hani,
I continue to re-open the ticket (Ticket #416119) that I opened more than 2 months ago (14th september) and after 2 attempts and manual resize from your support I still don't get a working and automated solution. Honestly I am happy for the VPS per se, but I am reconsidering the renewal because open a ticket and allow your support team to access my VPS (with privacy concern) in order to fix the storage is not an ideal solution and doesn't seem an enterprise way of selling a service like the "unlimited storage".
Can you push for a final resolution please?
Thanks,
Valenerd
@Valenerd the expanding storage doesn't always work after reboot. when it doesn't you have to create a ticket for them to adjust the size manually (they don't need your vps credentials-- those asking are probably just following "the manual"). I used to do this every month and note the storage before and after reboot, and create a ticket if it doesn't increase as expected. Eventually I got tired of this manual maintenance and I don't really trust support to manually adjust disk space with my data potentially at risk, so I gave up on it.
Are there going to be blackfriday deals ?
Hi @Valenerd,
This is the note that I adjust the size manually,
I hope it helps you.
sudo parted -l
Model: Linux device-mapper (linear) (dm)
Disk /dev/mapper/ubuntu--vg-lv--root: 2508GB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Disk Flags:
Number Start End Size File system Flags
1 0.00B 2508GB 2508GB ext4
Model: Xen Virtual Block Device (xvd)
Disk /dev/xvdc: 1074GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 1074GB 1074GB Linux LVM lvm
Model: Xen Virtual Block Device (xvd)
Disk /dev/xvda: 10.7GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB bios_grub
2 2097kB 1184MB 1182MB ext4
3 1184MB 10.7GB 9553MB
Warning: Not all of the space available to /dev/xvdb appears to be used, you can
fix the GPT to use all of the space (an extra 572522496 blocks) or continue with
the current setting?
Fix/Ignore?
fix
Model: Xen Virtual Block Device (xvd)
Disk /dev/xvdb: 1718GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 1425GB 1425GB Linux LVM lvm
sudo reboot
username@root [~] sudo fdisk -l
Disk /dev/loop0: 63.45 MiB, 66527232 bytes, 129936 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/xvda: 10 GiB, 10737418240 bytes, 20971520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: ABCDEF-123456-987654
Device Start End Sectors Size Type
/dev/xvda1 2048 4095 2048 1M BIOS boot
/dev/xvda2 4096 2312191 2308096 1.1G Linux filesystem
/dev/xvda3 2312192 20969471 18657280 8.9G Linux filesystem
Disk /dev/xvdb: 1.56 TiB, 1717986918400 bytes, 3355443200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: ABCDEF-123456-987654
Device Start End Sectors Size Type
/dev/xvdb1 2048 2782920670 2782918623 1.3T Linux LVM
Disk /dev/xvdc: 1000 GiB, 1073741824000 bytes, 2097152000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: ABCDEF-123456-987654
Device Start End Sectors Size Type
/dev/xvdc1 2048 2097151966 2097149919 1000G Linux LVM
Disk /dev/mapper/ubuntu--vg-lv--root: 2.28 TiB, 2508139266048 bytes, 4898709504 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
username@root [~] sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 63.4M 1 loop /snap/core20/1950
loop1 7:1 0 63.4M 1 loop /snap/core20/1974
loop2 7:2 0 103M 1 loop /snap/lxd/23541
loop3 7:3 0 111.9M 1 loop /snap/lxd/24322
loop4 7:4 0 53.3M 1 loop /snap/snapd/19361
loop5 7:5 0 53.3M 1 loop /snap/snapd/19457
sr0 11:0 1 1024M 0 rom
xvda 202:0 0 10G 0 disk
├─xvda1 202:1 0 1M 0 part
├─xvda2 202:2 0 1.1G 0 part /boot
└─xvda3 202:3 0 8.9G 0 part
└─ubuntu--vg-lv--root 253:0 0 2.3T 0 lvm /
xvdb 202:16 0 1.6T 0 disk
└─xvdb1 202:17 0 1.3T 0 part
└─ubuntu--vg-lv--root 253:0 0 2.3T 0 lvm /
xvdc 202:32 0 1000G 0 disk
└─xvdc1 202:33 0 1000G 0 part
└─ubuntu--vg-lv--root 253:0 0 2.3T 0 lvm /
username@root [~] sudo growpart /dev/xvdb 1
CHANGED: partition=1 start=2048 old: size=2782918623 end=2782920671 new: size=3355441119 end=3355443167
username@root [~] sudo lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 63.4M 1 loop /snap/core20/1950
loop1 7:1 0 63.4M 1 loop /snap/core20/1974
loop2 7:2 0 103M 1 loop /snap/lxd/23541
loop3 7:3 0 111.9M 1 loop /snap/lxd/24322
loop4 7:4 0 53.3M 1 loop /snap/snapd/19361
loop5 7:5 0 53.3M 1 loop /snap/snapd/19457
sr0 11:0 1 1024M 0 rom
xvda 202:0 0 10G 0 disk
├─xvda1 202:1 0 1M 0 part
├─xvda2 202:2 0 1.1G 0 part /boot
└─xvda3 202:3 0 8.9G 0 part
└─ubuntu--vg-lv--root 253:0 0 2.3T 0 lvm /
xvdb 202:16 0 1.6T 0 disk
└─xvdb1 202:17 0 1.6T 0 part
└─ubuntu--vg-lv--root 253:0 0 2.3T 0 lvm /
xvdc 202:32 0 1000G 0 disk
└─xvdc1 202:33 0 1000G 0 part
└─ubuntu--vg-lv--root 253:0 0 2.3T 0 lvm /
username@root [~] sudo pvresize /dev/xvda3
Physical volume "/dev/xvda3" changed
1 physical volume(s) resized or updated / 0 physical volume(s) not resized
username@root [~] sudo pvdisplay
--- Physical volume ---
PV Name /dev/xvda3
VG Name ubuntu-vg
PV Size <8.90 GiB / not usable 0
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 2277
Free PE 0
Allocated PE 2277
PV UUID ABCDEF-123456-987654
--- Physical volume ---
PV Name /dev/xvdc1
VG Name ubuntu-vg
PV Size <1000.00 GiB / not usable 2.98 MiB
Allocatable yes (but full)
PE Size 4.00 MiB
Total PE 255999
Free PE 0
Allocated PE 255999
PV UUID ABCDEF-123456-987654
--- Physical volume ---
PV Name /dev/xvdb1
VG Name ubuntu-vg
PV Size 1.56 TiB / not usable 1.98 MiB
Allocatable yes
PE Size 4.00 MiB
Total PE 409599
Free PE 69888
Allocated PE 339711
PV UUID ABCDEF-123456-987654
username@root [~] sudo vgdisplay
--- Volume group ---
VG Name ubuntu-vg
System ID
Format lvm2
Metadata Areas 3
Metadata Sequence No 16
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 1
Open LV 1
Max PV 0
Cur PV 3
Act PV 3
VG Size <2.55 TiB
PE Size 4.00 MiB
Total PE 667875
Alloc PE / Size 597987 / 2.28 TiB
Free PE / Size 69888 / 273.00 GiB
VG UUID ABCDEF-123456-987654
username@root [~] sudo lvdisplay
--- Logical volume ---
LV Path /dev/ubuntu-vg/lv-root
LV Name lv-root
VG Name ubuntu-vg
LV UUID AH3M2k-u1UW-ScK7-l2Fq-4Nuq-Z7PO-nPkc2h
LV Write Access read/write
LV Creation host, time ubuntu-server, 2022-06-28 10:42:21 +0000
LV Status available
# open 1
LV Size 2.28 TiB
Current LE 597987
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
username@root [~] sudo df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 293M 1.1M 292M 1% /run
/dev/mapper/ubuntu--vg-lv--root 2.3T 2.0T 199G 92% /
tmpfs 1.5G 0 1.5G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/xvda2 1.1G 253M 750M 26% /boot
tmpfs 293M 4.0K 293M 1% /run/user/1000
username@root [~] sudo lvextend -l +100%FREE /dev/mapper/ubuntu--vg-lv--root
Size of logical volume ubuntu-vg/lv-root changed from 2.28 TiB (597987 extents) to <2.55 TiB (667875 extents).
Logical volume ubuntu-vg/lv-root successfully resized.
username@root [~] sudo lvdisplay
--- Logical volume ---
LV Path /dev/ubuntu-vg/lv-root
LV Name lv-root
VG Name ubuntu-vg
LV UUID ABCDEF-123456-987654
LV Write Access read/write
LV Creation host, time ubuntu-server, 2022-06-28 10:42:21 +0000
LV Status available
# open 1
LV Size <2.55 TiB
Current LE 667875
Segments 3
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 253:0
username@root [~] sudo lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0 0 100% /snap/core20/1950
loop1 squashfs 4.0 0 100% /snap/core20/1974
loop2 squashfs 4.0 0 100% /snap/lxd/23541
loop3 squashfs 4.0 0 100% /snap/lxd/24322
loop4 squashfs 4.0 0 100% /snap/snapd/19361
loop5 squashfs 4.0 0 100% /snap/snapd/19457
sr0
xvda
├─xvda1
├─xvda2 ext4 1.0 ABCDEF-123456-987654 749.4M 24% /boot
└─xvda3 LVM2_member LVM2 001 ABCDEF-123456-987654
└─ubuntu--vg-lv--root ext4 1.0 ABCDEF-123456-987654 198G 87% /
xvdb
└─xvdb1 LVM2_member LVM2 001 ABCDEF-123456-987654
└─ubuntu--vg-lv--root ext4 1.0 ABCDEF-123456-987654 198G 87% /
xvdc
└─xvdc1 LVM2_member LVM2 001 ABCDEF-123456-987654
└─ubuntu--vg-lv--root ext4 1.0 ABCDEF-123456-987654 198G 87% /
username@root [~] sudo df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 293M 1.1M 292M 1% /run
/dev/mapper/ubuntu--vg-lv--root 2.3T 2.0T 199G 92% /
tmpfs 1.5G 0 1.5G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/xvda2 1.1G 253M 750M 26% /boot
tmpfs 293M 4.0K 293M 1% /run/user/1000
username@root [~] sudo resize2fs /dev/mapper/ubuntu--vg-lv--root -p
resize2fs 1.46.5 (30-Dec-2021)
Filesystem at /dev/mapper/ubuntu--vg-lv--root is mounted on /; on-line resizing required
old_desc_blocks = 292, new_desc_blocks = 327
The filesystem on /dev/mapper/ubuntu--vg-lv--root is now 683904000 (4k) blocks long.
username@root [~] sudo df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 293M 1.1M 292M 1% /run
/dev/mapper/ubuntu--vg-lv--root 2.6T 2.0T 456G 82% /
tmpfs 1.5G 0 1.5G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/xvda2 1.1G 253M 750M 26% /boot
tmpfs 293M 4.0K 293M 1% /run/user/1000
reference
How to fix error: GPT PMBR size mismatch
https://arstech.net/gpt-pmbr-size-mismatch/
How to Extend LVM Partition with lvextend Command in Linux
https://www.linuxtechi.com/extend-lvm-partitions/
How to Extend a Logical Volume in LVM - for XFS, ext4 and swap filesystem
https://www.thegeeksearch.com/how-to-extend-a-logical-volume-in-lvm-for-xfs-ext4-and-swap-filesystem/
well for me it isnt working either.... I just open every month a ticket. It doesnt even append in the control panel..
Hi everybody and thank you for your replies.
@Gelofuego thank you so much, really useful even if I hope servarica will solve my issue
@_cece, @artxs so it looks like "fake" the advertised automatic unlimited storage
@servarica_hani do you have any statements on this?
@servarica_hani Same question. Waiting for your BF promotion.