T
T
Talyan2019-11-06 19:07:21
linux
Talyan, 2019-11-06 19:07:21

Why does PROXMOX see 239 gigs in storage instead of 2 terabytes?

There is a proxmox server that runs on zfs from two SAS disks with a capacity of 270 gigs in the form of a 270 gig mirror ride.

Plus one more ZFS in the same server from two of the same mirror disks, for storing Linux images on it, etc. In general, useless storage, which is not a pity to disable.

It was required to launch a virtual machine that weighs 600+ gigs.

On a hot one, I poked out both second disks, on which images were lying.
I did not steer the zpool utility, because after the manipulations I needed, I'm going to stick these two second SAS disks in place.

But since there are no more holes in the server where you can stick an HDD, I stuck one SATA 2 TB into the server, mounted it in / mnt / backup
I created a "Directory" repository in the promox and specified the path to the directory I needed: /mnt/backup.

As a result, fdisk sees all 2 TB, where I uploaded the vmdk image.
But in proxmox, the picture is this:
5dc2ee107c497217421770.png
5dc2ee16d3335575521901.png

By the way - 239 gig, this is exactly the size of the pool that I just pulled out on a hot one. The storage where the images of Linux lay was just 239 gigabytes. But damn it, I created a new, different repository. It has nothing to do with the old imagery.

By the way, the vmdk image that you see in the screenshot is just 600 gigs. But proxmox shows it as 32 gig.

Answer the question

In order to leave comments, you need to log in

1 answer(s)
T
Talyan, 2019-11-07
@flapflapjack

Answer:
because you are stupid.
It is necessary not to do such things through one place, but in the way it is supposed by the developers.
I mean zpool create sdc
, that's all. One team without any

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question