 |
Hi, without a bit of context and configuration it will only a rough guess. It seems that your storage is not able to label (so create) a volume with a device (related to somehow to glusterfs) You have to fix permission rights on the final destination (usually directory) where the volume will be written for example being sure that once the glusterfs mount is done the directory still has your storage user (normally bareos) rights to write there. documentation reference : https://docs.bareos.org/master/TasksAndConcepts/StorageBackends.html?highlight=glusterfs#gfapi-storage-backend and also https://docs.gluster.org/en/latest/Administrator-Guide/Bareos/ |
|
|
hi bruno: i have checked the rights and everthing seems good from this matter: [root@bareos mnt]# ls -la total 12 drwxr-xr-x 4 root root 4096 Jun 12 2019 . dr-xr-xr-x. 22 root root 4096 Oct 5 08:18 .. drwxr-xr-x 2 bareos bareos 4096 Jun 12 2019 bareos [root@bareos mnt]# [root@bareos mnt]# pwd /mnt [root@bareos mnt]# i realize somethig has to be with the volume. I list the files under /mnt/bareos and nothing apears with the volume running. |
|
|
Did you make some progress, any feedback to share here ? |
|
|
hi bruno: things are the same err= no such file or directory tried add the volume name and number again in bcosole but no lock, is there a workaround to create the volume-number in bcosole to create this volume on gluster patition /mnt/bareos where i am creating them. |
|
|
Sorry I'm not that expert of glusterfs but can't you try in a console to run ``` su bareos touch /mnt/bareos/TEST.TOUCH ``` and get a file written there ? If it failed, then you should have a look into your syslog and/or the one the glusterfs server |
|
|
No news since months |
- Anonymous
