View Issue Details

IDProjectCategoryView StatusLast Update
0001392bareos-coreGeneralpublic2022-01-24 10:58
Reporternelson.gonzalez6 Assigned Tobruno-at-bareos  
PriorityhighSeverityminorReproducibilityunable to reproduce
Status closedResolutionunable to reproduce 
PlatformLinuxOSCentOSOS Version7
Product Version19.2.11 
Summary0001392: problem with a backup - warning stored/label Failed err=stored/ could not open:
Descriptionbareos-sd JobId 15737: Warning: stored/ Open device "GlusterStorage" (Gluster Device) Volume "Incrementalecourses-0572" failed: ERR=stored/ Could not open: Gluster Device/Incrementalecourses-0572, ERR=No such file or directory

How can i fix this problem, seems that dosent do anything. I wait but dosent continues. Any suegestions..


TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action




2021-10-13 15:17

developer   ~0004307

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 :
and also


2021-10-15 04:12

reporter   ~0004309

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
[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.


2021-11-10 09:59

developer   ~0004324

Did you make some progress, any feedback to share here ?


2021-11-10 14:44

reporter   ~0004333

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.


2021-11-10 15:14

developer   ~0004334

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


2022-01-24 10:58

developer   ~0004484

No news since months

Issue History

Date Modified Username Field Change
2021-10-12 12:07 nelson.gonzalez6 New Issue
2021-10-13 15:17 bruno-at-bareos Note Added: 0004307
2021-10-13 15:29 bruno-at-bareos Assigned To => bruno-at-bareos
2021-10-13 15:29 bruno-at-bareos Status new => assigned
2021-10-15 04:12 nelson.gonzalez6 Note Added: 0004309
2021-11-10 09:59 bruno-at-bareos Note Added: 0004324
2021-11-10 14:44 nelson.gonzalez6 Note Added: 0004333
2021-11-10 15:14 bruno-at-bareos Note Added: 0004334
2022-01-24 10:58 bruno-at-bareos Status assigned => closed
2022-01-24 10:58 bruno-at-bareos Resolution open => unable to reproduce
2022-01-24 10:58 bruno-at-bareos Note Added: 0004484