[SOLVED] problem with storage / directory

[jjgoldman]

Hello,

Please, excuse me for my poor English

beginner in proxmox solution, i try to add a directory / it's a hard disk.
1 partition / format ext4 / mounted via fstab on /mnt/bkp_sdc
it works

root@pve:/etc/pve# df -h
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 786M 9.1M 777M 2% /run
rpool/ROOT/pve-1 438G 12G 427G 3% /
tmpfs 3.9G 43M 3.8G 2% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/sdc1 687G 73M 652G 1% /bkp_sdc
rpool 427G 128K 427G 1% /rpool
rpool/ROOT 427G 128K 427G 1% /rpool/ROOT
rpool/data 427G 128K 427G 1% /rpool/data
/dev/fuse 30M 16K 30M 1% /etc/pve
tmpfs 786M 0 786M 0% /run/user/0


it's dev/sdc1
but in the proxmox webgui ...

Activé > Oui
Actif > Oui
Contenu > Fichier sauvegarde VZDump
Type > Répertoire
Utilisation > 2.56% (11.21 GiB sur 437.38 GiB)

437.38 GiB vs 687 ???
what's the problem ?

thanks

 

[aaron]

Can you show the output of lsblk and paste it into [code][/code] tags please?

 

[jjgoldman]

Hello,

root@pve:/etc/pve# lsblk
NAME     MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda        8:0    0 465.8G  0 disk
├─sda1     8:1    0  1007K  0 part
├─sda2     8:2    0   512M  0 part
└─sda3     8:3    0 465.3G  0 part
sdb        8:16   0 465.8G  0 disk
├─sdb1     8:17   0  1007K  0 part
├─sdb2     8:18   0   512M  0 part
└─sdb3     8:19   0 465.3G  0 part
sdc        8:32   0 698.7G  0 disk
└─sdc1     8:33   0 698.7G  0 part /bkp_sdc
zd0      230:0    0    50G  0 disk
├─zd0p1  230:1    0   549M  0 part
└─zd0p2  230:2    0  49.5G  0 part
zd16     230:16   0    50G  0 disk
├─zd16p1 230:17   0     1G  0 part
└─zd16p2 230:18   0    49G  0 part
zd32     230:32   0   100G  0 disk
├─zd32p1 230:33   0    28G  0 part
├─zd32p2 230:34   0     1K  0 part
├─zd32p5 230:37   0     2G  0 part
└─zd32p6 230:38   0  70.1G  0 part

thanks

 

[jjgoldman]

is this forum only for subscripters ?

 

[tom]

is this forum only for subscripters ?

no.

 

[Dominic]

The GUI takes the content from df relatively directly itself. If you still have this problem, please also post the following output in code brackets:

pveversion -v
pvesm status

 

[jjgoldman]

pveversion -v
proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: 6.2-4 (running version: 6.2-4/9824574a)
pve-kernel-5.4: 6.2-1
pve-kernel-helper: 6.2-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.3-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.15-pve1
libproxmox-acme-perl: 1.0.3
libpve-access-control: 6.1-1
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.1-2
libpve-guest-common-perl: 3.0-10
libpve-http-server-perl: 3.0-5
libpve-storage-perl: 6.1-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.2-1
lxcfs: 4.0.3-pve2
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-1
pve-cluster: 6.1-8
pve-container: 3.1-5
pve-docs: 6.2-4
pve-edk2-firmware: 2.20200229-1
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: 3.0-9
pve-i18n: 2.1-2
pve-qemu-kvm: 5.0.0-2
pve-xtermjs: 4.3.0-1
qemu-server: 6.2-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: 0.8.3-pve1

pvesm status
Name             Type     Status           Total            Used       Available        %
bkp               dir     active       457809920        13503104       444306816    2.95%
local             dir     active       457809920        13503104       444306816    2.95%
local-zfs     zfspool     active       457823748        13516892       444306856    2.95%

df
Filesystem                   1K-blocks     Used Available Use% Mounted on
udev                           3996032        0   3996032   0% /dev
tmpfs                           804076     9276    794800   2% /run
rpool/ROOT/pve-1             457809792 13503104 444306688   3% /
tmpfs                          4020364    43680   3976684   2% /dev/shm
tmpfs                             5120        0      5120   0% /run/lock
tmpfs                          4020364        0   4020364   0% /sys/fs/cgroup
/dev/sdc1                    720025536    73756 683306720   1% /bkp_sdc
rpool                        444306816      128 444306688   1% /rpool
rpool/ROOT                   444306816      128 444306688   1% /rpool/ROOT
rpool/data                   444306816      128 444306688   1% /rpool/data
rpool/data/subvol-103-disk-0   8388608   745600   7643008   9% /rpool/data/subvol-103-disk-0
/dev/fuse                        30720       16     30704   1% /etc/pve
tmpfs                           804072        0    804072   0% /run/user/0

vzdump works

i found that / i'm not alone

Justin says:

16th June 2020 at 5:04 pm

Hello,


I followed this guide to set up an external hdd for saving backups of my VMs & LXCs. Everything looked good but then the reported size of the backup storage changed. On the summary page of the storage it now says the backup storage is the exact same size as the local storage – Usage 4.59% (4.31 GiB of 93.99 GiB). Is this normal?



it's an external hd but it looks like my question

Best regards,
bernard

 

[Dominic]

The only way I got equal sizes for the two storages displayed in pvesm status so far is when the directory storage in Proxmox VE (that is bkp in your case) does not have is_mountpoint 1 and the directory is actually not mounted.

Could you please also post the relevant lines from the following commands?

cat /etc/pve/storage.cfg
cat /etc/fstab

 

[jjgoldman]

problem with a storm

cat storage.cfg
dir: local
    path /var/lib/vz
    content vztmpl,iso
    shared 0

zfspool: local-zfs
    pool rpool/data
    content rootdir,images
    sparse 1

dir: bkp
    path /mnt/bkp_sdc
    content backup
    maxfiles 1

cat fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
/dev/sdc1 /bkp_sdc ext4 defaults 0 2

Best regards,
bernard

 

[Dominic]

First of all, add the option that I mentioned before, that is is_mountpoint 1, to your storage.cfg, so that the file contains

dir: bkp
    path /mnt/bkp_sdc
    content images
    shared 0
    is_mountpoint 1

If you then run pvesm status you should get a warning:

unable to activate storage 'bkp' - directory is expected to be a mount point but is not mounted: '/mnt/bkp_sdc'

because what you have initially mentioned

1 partition / format ext4 / mounted via fstab on /mnt/bkp_sdc

is actually not the case. It is mounted on /bkp_sdc and not on /mnt/bkp_sdc.

You can see this in your /etc/fstab

/dev/sdc1 /bkp_sdc ext4 defaults 0 2

and also in the df -h output:

/dev/sdc1         687G   73M  652G   1% /bkp_sdc

and in lsblk as well

/dev/sdc1         687G   73M  652G   1% /bkp_sdc

As a result, both your storages local and bkp are on the root filesystem rpool/ROOT/pve-1.
Consequently, the numbers in pvesm status for those two storages

pvesm status
Name             Type     Status           Total            Used       Available        %
bkp               dir     active       457809920        13503104       444306816    2.95%
local             dir     active       457809920        13503104       444306816    2.95%

are the same as the numbers for the filesystem in df

rpool/ROOT/pve-1             457809792 13503104 444306688   3% /

and this also leads to the numbers in the web UI.

 

[jjgoldman]

it works
thank you very much

pvesm status
Name             Type     Status           Total            Used       Available        %
bkp               dir     active       720025536           73760       683306716    0.01%
local             dir     active       453081984        15007488       438074496    3.31%
local-zfs     zfspool     active       456316360        18241752       438074608    4.00%

proxmox is a very good product / i'm the problem
how can i marked the thread as solved

Best regards,
bernard