Garbage Collection and nested Datastores

sa10

Renowned Member
Feb 6, 2009
46
0
71
Canada
I tried to run Garbage Collection and have saw the warnings in the log

WARN: warning: unable to access non-existent chunk fbc102dadf17a3dc81e5eb73986f83ee00809b80e47299343b2954ff560c6b1f, required by "/mnt/datastore/PBS1/s12345/host/cent8/2021-09-30T04:26:24Z/catalog.pcat1.didx

Where is the problem?

I can assume - that problem in the placement of my Datastores.
I have my storages in the different zfs datasets:
PBS1 - my main Datastor
PBS1/s12345 - Datastor for a separate user.

And when I ran Garbage Collection on the PBS1 it found chunks in the PBS1/s12345 and I see those warnings.

Important question: - Is there a danger of removing chunks in the nested Datastores?

Is there a good way to move Datastore in the nested ZFS dataset?

I hope I'm not sure

I would do so:
PBS1/main - my main Datastor
PBS1/s12345 - Datastor for a separate user.

I hope there would be enough this command:
zfs set mountpoint=/mnt/datastore/PBS1/main PBS1
But I'm not sure that it is enough.

Could someone give me advice please?
Thanks!
 
Last edited:
zfs set mountpoint=/mnt/datastore/PBS1/main PBS1
After this command I'll have the s12345 in the /mnt/datastore/PBS1/main/s12345

Because I need the command:
zfs set mountpoint=/mnt/datastore/PBS1/s12345 PBS1/s12345

I didn't find commands to change the datastore path
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!