[SOLVED] CFIS - can't move/create disk

voarsh

Member
Nov 20, 2020
218
19
23
28
Similar to:
https://forum.proxmox.com/threads/cant-use-nfs-share.53463/

I can add it as a network drive on Windows and create a file just fine - I can touch /path/filename on the node for the CFIS.
But moving the disk to the CFIS gives
create full clone of drive sata0 (share1:102/vm-102-disk-0.qcow2)
TASK ERROR: storage migration failed: mkdir /mnt/pve/D2600-16TBThree/images/102: Permission denied at /usr/share/perl5/PVE/Storage/Plugin.pm line 728.

- Any ideas? I've tried rebooting as well.

Can't seem to touch /mnt/pve/D2600-16TBThree/images/tetingsan though
 
Last edited:
hi,

Can't seem to touch /mnt/pve/D2600-16TBThree/images/tetingsan though
then it will not work as observed from the error, there's likely a permission issue with that folder.

what do you see when you run ls -anR /mnt/pve/D2600-16TBThree/
 
hi,


then it will not work as observed from the error, there's likely a permission issue with that folder.

what do you see when you run ls -anR /mnt/pve/D2600-16TBThree/

Bash:
[root@RIG ~]$ ls -anR /mnt/pve/D2600-16TBThree/
/mnt/pve/D2600-16TBThree/:
total 4
drwxr-xr-x 2 0 0    0 May 11 12:02 .
drwxr-xr-x 6 0 0 4096 May 11 11:35 ..
drwxr-xr-x 2 0 0    0 May  4 02:11 ct
drwxr-xr-x 2 0 0    0 May 11 09:29 dump
drwxr-xr-x 2 0 0    0 May 10 14:14 images
-rwxr-xr-x 1 0 0    0 May  3 18:14 .lock
drwxr-xr-x 2 0 0    0 Apr  8 13:37 lost+found
drwxr-xr-x 2 0 0    0 Apr  8 13:37 private
drwxr-xr-x 2 0 0    0 May 11 12:02 .recycle
drwxr-xr-x 2 0 0    0 May 10 14:14 snippets
drwxr-xr-x 2 0 0    0 Apr  8 13:37 template
drwxr-xr-x 2 0 0    0 May  4 02:10 vm

/mnt/pve/D2600-16TBThree/ct:
total 0
drwxr-xr-x 2 0 0 0 May  4 02:11 .
drwxr-xr-x 2 0 0 0 May 11 12:02 ..
drwxr-xr-x 2 0 0 0 May  4 02:11 192

/mnt/pve/D2600-16TBThree/ct/192:
total 1024
drwxr-xr-x 2 0 0 0 May  4 02:11 .
drwxr-xr-x 2 0 0 0 May  4 02:11 ..
-rwxr-xr-x 1 0 0 9 May  4 02:11 owner

/mnt/pve/D2600-16TBThree/dump:
total 185550848
drwxr-xr-x 2 0 0           0 May 11 09:29 .
drwxr-xr-x 2 0 0           0 May 11 12:02 ..
-rwxr-xr-x 1 0 0        1420 May  8 08:44 vzdump-lxc-135-2021_05_08-08_42_47.log
-rwxr-xr-x 1 0 0  1069845412 May  8 08:44 vzdump-lxc-135-2021_05_08-08_42_47.tar.zst
-rwxr-xr-x 1 0 0        2465 May  8 08:45 vzdump-lxc-141-2021_05_08-08_44_49.log
-rwxr-xr-x 1 0 0   416715915 May  8 08:45 vzdump-lxc-141-2021_05_08-08_44_49.tar.zst
-rwxr-xr-x 1 0 0        2247 May  8 08:47 vzdump-lxc-169-2021_05_08-08_45_43.log
-rwxr-xr-x 1 0 0   710951924 May  8 08:47 vzdump-lxc-169-2021_05_08-08_45_43.tar.zst
-rwxr-xr-x 1 0 0        1853 May  8 08:47 vzdump-lxc-172-2021_05_08-08_47_14.log
-rwxr-xr-x 1 0 0   399371771 May  8 08:47 vzdump-lxc-172-2021_05_08-08_47_14.tar.zst
-rwxr-xr-x 1 0 0         180 May  4 08:15 vzdump-qemu-127-2021_05_04-08_15_02.log
-rwxr-xr-x 1 0 0        5705 May  5 08:17 vzdump-qemu-127-2021_05_05-08_15_02.log
-rwxr-xr-x 1 0 0  9749399242 May  5 08:17 vzdump-qemu-127-2021_05_05-08_15_02.vma.lzo
-rwxr-xr-x 1 0 0   374149142 May  6 09:38 vzdump-qemu-127-2021_05_06-08_15_33.vma.dat
-rwxr-xr-x 1 0 0        6813 May  7 08:19 vzdump-qemu-127-2021_05_07-08_15_02.log
-rwxr-xr-x 1 0 0 14231658427 May  7 08:19 vzdump-qemu-127-2021_05_07-08_15_02.vma.lzo
-rwxr-xr-x 1 0 0        6809 May  8 08:57 vzdump-qemu-127-2021_05_08-08_52_05.log
-rwxr-xr-x 1 0 0 14242318572 May  8 08:57 vzdump-qemu-127-2021_05_08-08_52_05.vma.lzo
-rwxr-xr-x 1 0 0        6375 May 11 09:29 vzdump-qemu-127-2021_05_11-09_23_43.log
-rwxr-xr-x 1 0 0  9617205717 May 11 09:29 vzdump-qemu-127-2021_05_11-09_23_43.vma.lzo
-rwxr-xr-x 1 0 0       11230 May  1 17:35 vzdump-qemu-142-2021_05_01-16_27_18.log
-rwxr-xr-x 1 0 0 48493786105 May  1 17:35 vzdump-qemu-142-2021_05_01-16_27_18.vma.zst
-rwxr-xr-x 1 0 0         794 Apr 29 07:30 vzdump-qemu-163-2021_04_29-07_30_03.log
-rwxr-xr-x 1 0 0        6359 May  3 07:33 vzdump-qemu-163-2021_05_03-07_30_02.log
-rwxr-xr-x 1 0 0  2964047955 May  3 07:33 vzdump-qemu-163-2021_05_03-07_30_02.vma.zst
-rwxr-xr-x 1 0 0         794 May  6 07:31 vzdump-qemu-163-2021_05_06-07_30_17.log
-rwxr-xr-x 1 0 0        6604 May  9 10:14 vzdump-qemu-163-2021_05_09-10_09_18.log
-rwxr-xr-x 1 0 0  3057122075 May  9 10:14 vzdump-qemu-163-2021_05_09-10_09_18.vma.zst
-rwxr-xr-x 1 0 0         724 Apr 29 07:30 vzdump-qemu-164-2021_04_29-07_30_06.log
-rwxr-xr-x 1 0 0        7941 May  3 07:39 vzdump-qemu-164-2021_05_03-07_33_56.log
-rwxr-xr-x 1 0 0  3518346111 May  3 07:39 vzdump-qemu-164-2021_05_03-07_33_56.vma.zst
-rwxr-xr-x 1 0 0         724 May  6 07:31 vzdump-qemu-164-2021_05_06-07_31_28.log
-rwxr-xr-x 1 0 0        8282 May  9 10:20 vzdump-qemu-164-2021_05_09-10_14_33.log
-rwxr-xr-x 1 0 0  3652325625 May  9 10:20 vzdump-qemu-164-2021_05_09-10_14_33.vma.zst
-rwxr-xr-x 1 0 0        8971 Apr 22 07:58 vzdump-qemu-165-2021_04_22-07_50_48.log
-rwxr-xr-x 1 0 0  8211180450 Apr 22 07:58 vzdump-qemu-165-2021_04_22-07_50_48.vma.zst
-rwxr-xr-x 1 0 0        4062 May  6 20:25 vzdump-qemu-177-2021_05_06-20_22_48.log
-rwxr-xr-x 1 0 0  3405219870 May  6 20:25 vzdump-qemu-177-2021_05_06-20_22_48.vma.zst
-rwxr-xr-x 1 0 0        3503 May  6 22:44 vzdump-qemu-177-2021_05_06-22_41_23.log
-rwxr-xr-x 1 0 0  3405577640 May  6 22:44 vzdump-qemu-177-2021_05_06-22_41_23.vma.zst
-rwxr-xr-x 1 0 0        4695 May  8 08:52 vzdump-qemu-177-2021_05_08-08_47_47.log
-rwxr-xr-x 1 0 0  4136313540 May  8 08:52 vzdump-qemu-177-2021_05_08-08_47_47.vma.zst
-rwxr-xr-x 1 0 0         838 Apr 29 07:30 vzdump-qemu-195-2021_04_29-07_30_09.log
-rwxr-xr-x 1 0 0        8898 May  3 08:00 vzdump-qemu-195-2021_05_03-07_39_22.log
-rwxr-xr-x 1 0 0  9165189812 May  3 08:00 vzdump-qemu-195-2021_05_03-07_39_22.vma.zst
-rwxr-xr-x 1 0 0         838 May  6 07:31 vzdump-qemu-195-2021_05_06-07_31_34.log
-rwxr-xr-x 1 0 0       11382 May  9 10:55 vzdump-qemu-195-2021_05_09-10_20_48.log
-rwxr-xr-x 1 0 0  9815963667 May  9 10:55 vzdump-qemu-195-2021_05_09-10_20_48.vma.zst
-rwxr-xr-x 1 0 0         833 Apr 29 07:30 vzdump-qemu-196-2021_04_29-07_30_11.log
-rwxr-xr-x 1 0 0        8847 May  3 08:17 vzdump-qemu-196-2021_05_03-08_00_11.log
-rwxr-xr-x 1 0 0  8245672044 May  3 08:17 vzdump-qemu-196-2021_05_03-08_00_11.vma.zst
-rwxr-xr-x 1 0 0         833 May  6 07:31 vzdump-qemu-196-2021_05_06-07_31_41.log
-rwxr-xr-x 1 0 0       11375 May  9 11:17 vzdump-qemu-196-2021_05_09-10_55_22.log
-rwxr-xr-x 1 0 0  8285097421 May  9 11:17 vzdump-qemu-196-2021_05_09-10_55_22.vma.zst
-rwxr-xr-x 1 0 0         732 Apr 29 07:30 vzdump-qemu-197-2021_04_29-07_30_13.log
-rwxr-xr-x 1 0 0        6619 May  3 08:20 vzdump-qemu-197-2021_05_03-08_17_07.log
-rwxr-xr-x 1 0 0  5148734153 May  3 08:20 vzdump-qemu-197-2021_05_03-08_17_07.vma.zst
-rwxr-xr-x 1 0 0         732 May  6 07:32 vzdump-qemu-197-2021_05_06-07_31_50.log
-rwxr-xr-x 1 0 0        6955 May  9 11:23 vzdump-qemu-197-2021_05_09-11_17_07.log
-rwxr-xr-x 1 0 0  5282964589 May  9 11:23 vzdump-qemu-197-2021_05_09-11_17_07.vma.zst
-rwxr-xr-x 1 0 0         952 Apr 29 07:30 vzdump-qemu-198-2021_04_29-07_30_16.log
-rwxr-xr-x 1 0 0        8817 May  3 08:36 vzdump-qemu-198-2021_05_03-08_20_49.log
-rwxr-xr-x 1 0 0  6158994754 May  3 08:36 vzdump-qemu-198-2021_05_03-08_20_49.vma.zst
-rwxr-xr-x 1 0 0         831 May  6 07:34 vzdump-qemu-198-2021_05_06-07_32_27.log
-rwxr-xr-x 1 0 0       11281 May  9 11:44 vzdump-qemu-198-2021_05_09-11_23_39.log
-rwxr-xr-x 1 0 0  6191854005 May  9 11:44 vzdump-qemu-198-2021_05_09-11_23_39.vma.zst

/mnt/pve/D2600-16TBThree/images:
total 0
drwxr-xr-x 2 0 0 0 May 10 14:14 .
drwxr-xr-x 2 0 0 0 May 11 12:02 ..
drwxr-xr-x 2 0 0 0 May  2 03:45 126
drwxr-xr-x 2 0 0 0 May  6 15:50 134
drwxr-xr-x 2 0 0 0 May  4 03:15 154
drwxr-xr-x 2 0 0 0 May  7 10:19 177
drwxr-xr-x 2 0 0 0 May 10 14:28 180
drwxr-xr-x 2 0 0 0 May  4 03:15 182
drwxr-xr-x 2 0 0 0 May  3 17:04 193
drwxr-xr-x 2 0 0 0 May  4 03:16 194
drwxr-xr-x 2 0 0 0 Apr 18 17:08 196
drwxr-xr-x 2 0 0 0 Apr 23 03:01 197
drwxr-xr-x 2 0 0 0 Apr 28 13:21 203

/mnt/pve/D2600-16TBThree/images/126:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/126': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/134:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/134': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/154:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/154': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/177:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/177': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/180:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/180': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/182:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/182': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/193:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/193': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/194:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/194': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/196:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/196': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/197:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/197': Permission denied
total 0

/mnt/pve/D2600-16TBThree/images/203:
ls: reading directory '/mnt/pve/D2600-16TBThree/images/203': Permission denied
total 0

/mnt/pve/D2600-16TBThree/lost+found:
ls: reading directory '/mnt/pve/D2600-16TBThree/lost+found': Permission denied
total 0

/mnt/pve/D2600-16TBThree/private:
total 0
drwxr-xr-x 2 0 0 0 Apr  8 13:37 .
drwxr-xr-x 2 0 0 0 May 11 12:02 ..

/mnt/pve/D2600-16TBThree/.recycle:
total 0
drwxr-xr-x 2 0 0 0 May 11 12:02  .
drwxr-xr-x 2 0 0 0 May 11 12:02  ..
-rwxr-xr-x 1 0 0 0 May 11 12:02 'Copy #1 of tetingsan'
-rwxr-xr-x 1 0 0 0 May 11 11:57 'New Text Document.txt'
-rwxr-xr-x 1 0 0 0 May 11 11:59  tetingsan

/mnt/pve/D2600-16TBThree/snippets:
total 1024
drwxr-xr-x 2 0 0   0 May 10 14:14 .
drwxr-xr-x 2 0 0   0 May 11 12:02 ..
-rwxr-xr-x 1 0 0 304 May 10 14:14 180.yaml

/mnt/pve/D2600-16TBThree/template:
total 0
drwxr-xr-x 2 0 0 0 Apr  8 13:37 .
drwxr-xr-x 2 0 0 0 May 11 12:02 ..
drwxr-xr-x 2 0 0 0 Apr  8 13:37 cache
drwxr-xr-x 2 0 0 0 May 10 14:10 iso

/mnt/pve/D2600-16TBThree/template/cache:
total 0
drwxr-xr-x 2 0 0 0 Apr  8 13:37 .
drwxr-xr-x 2 0 0 0 Apr  8 13:37 ..

/mnt/pve/D2600-16TBThree/template/iso:
total 521216
drwxr-xr-x 2 0 0         0 May 10 14:10 .
drwxr-xr-x 2 0 0         0 Apr  8 13:37 ..
-rwxr-xr-x 1 0 0 533528576 May  6 23:55 focal-server-cloudimg-amd64-disk-kvm.img

/mnt/pve/D2600-16TBThree/vm:
total 0
drwxr-xr-x 2 0 0 0 May  4 02:10 .
drwxr-xr-x 2 0 0 0 May 11 12:02 ..
drwxr-xr-x 2 0 0 0 May  4 02:10 206

/mnt/pve/D2600-16TBThree/vm/206:
total 1024
drwxr-xr-x 2 0 0 0 May  4 02:10 .
drwxr-xr-x 2 0 0 0 May  4 02:10 ..
-rwxr-xr-x 1 0 0 9 May  4 02:10 owner

The CFIS share is suppose to have all users running it as root:
1620731608521.png
 
could you also show cat /etc/pve/storage.cfg?
 
could you also show cat /etc/pve/storage.cfg?
Thansks:

Code:
cat /etc/pve/storage.cfg
dir: local
        path /var/lib/vz
        content iso,backup,vztmpl

lvmthin: local-lvm
        thinpool data
        vgname pve
        content rootdir,images

cifs: share1
        path /mnt/pve/share1
        server 192.168.100.66
        share share1
        content iso,snippets,vztmpl,images,backup,rootdir
        prune-backups keep-all=1
        username root

cifs: share2
        disable
        path /mnt/pve/share2
        server 192.168.100.66
        share vgpu
        content rootdir,backup,vztmpl,images,snippets,iso
        prune-backups keep-all=1
        username root

cifs: Seagate1TBDriveThree
        path /mnt/pve/Seagate1TBDriveThree
        server 192.168.100.66
        share Seagate1TBDriveThree
        content snippets,rootdir,vztmpl,images,backup,iso
        prune-backups keep-all=1
        username root

cifs: D2600-16TBThree
        path /mnt/pve/D2600-16TBThree
        server 192.168.100.66
        share D2600-16TBThree
        content vztmpl,images,snippets,iso,rootdir,backup
        prune-backups keep-all=1
        username root
 
are you using this storage also as datastore with PBS? that could be the reason for the permission denied.
the datastore shouldn't be in the same directory as your other share
 
are you using this storage also as datastore with PBS? that could be the reason for the permission denied.
the datastore shouldn't be in the same directory as your other share
It has been in the past, it's not actively in use now.
I've disabled PBS storage backend. Do you recommend deleting /ct/ /vm/ /.chunks/ - is that it?
 
yes you can delete it unless data is important (otherwise you could just move it somewhere else).

but i assume the file permissions on your share filesystem might be broken due to this, might be a good idea to check the ls -n outputs of those directories in your share server
 
yes you can delete it unless data is important (otherwise you could just move it somewhere else).

but i assume the file permissions on your share filesystem might be broken due to this, might be a good idea to check the ls -n outputs of those directories in your share server

I'll move them. Seems that /images /dumps/ can't be written to directly.
I'll check again.

Thanks.
 
I removed vm, ct, etc
I chmod 777 -R /mnt/pve/HPStorageWorksD2600-16TBThree/images/dump, etc.
I made the owner of these dirs root and problem gone away - thanks.
 

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!