Bill I am still on 11.0.6 for Dir and SD
> On 2. Mar 2023, at 21:31, Bill Arlofski <w...@protonmail.com> wrote: > > On 3/2/23 12:08, Justin Case wrote: >> Dear Bill, please find my response inline, further down: >>> On 2. Mar 2023, at 17:33, Bill Arlofski via Bacula-users >>> <bacula-users@lists.sourceforge.net> wrote: >>> >>> On 3/1/23 16:22, Justin Case wrote: >>>> What I actually did was to select them in Baculum and purged them. Then >>>> they were in state “Purged”. Then next time a volume from this pool was >>>> needed, Baculum grabbed the first one and used it without problems. >>> >>> Hello Justin, >>> >>> Well this does not make sense to me from what I understand from your >>> initial description of the issue of volumes in error. >>> >>> I will do a couple tests to be sure, but if the scenario is like: >>> >>> - New volume needed >>> - Director creates one in the catalog >>> - SD is instructed to create same volume on disk >>> - Disk Volume creation fails (due to unmounted filesystem, permissions >>> issue, etc) >>> - Director marks the volume in Error status (well, Read-Only in my tests >>> here) in the catalog and it is no longer eligible for any write/truncate >>> actions by the Director, nor the SD. >>> >>> In the scenario above, we have an "orphaned" volume in the catalog, and no >>> file volume on disk. Nothing except deleting this volume from the catalog >>> can really be done. >>> >>> If the volstatus is manually set to Append, Recycle, or Purged, the next >>> time any action is attempted by the SD, it will fail since the file volume >>> does not exist to read. >>> >>> When the SD attempts to open a volume, the first thing the SD does is >>> attempt to read its label. Of course this would fail on a non-existent file >>> volume, and the Director would reset the volume to Error (Read-Only) in the >>> catalog. >>> >>> BUT... As I re-read your initial email, I see that the scenario I described >>> above is not what happened. :) >>> >>> In your case, the file volume did exist on disk, but at the time of the >>> error, the SD could not access it (disk not mounted, NFS/iSCSI/FC/CIFS >>> problems, etc). It seems that later, as you described this partition and >>> the volumes on it became available. This is why the purge worked for you. >>> >> I am sorry you are mistaken. I triple checked that the volume did NOT exist >> on disk. When I checked, the disk was mounted. The volume limit of the pool >> was not reached yet. The disk shows as 100% full, but there were some >> hundred GB freeon disk, however, seems to have been the root cause. I have >> not changed any permissions and it works smoothly again. > > > Hello Justin, now we are talking apples and oranges. > > The original volume you show a single log entry for was this: > ----8<---- > Warning: mount.c:216 Open of File device “storagedev1" (/mnt/storage1) Volume > "vol-2675" failed: ERR=file_dev.c:189 Could not > open(/mnt/storage1/vol-2675,OPEN_READ_WRITE,0640): ERR=No such file or > directory > ----8<---- > > This is clearly just a mount request. Also, notice that is is a mount request > for `OPEN_READ_WRITE` access. > > The new volume you show here was indeed a couple label attempts, followed by > a mount request for 'CREATE_READ_WRITE' access: > ----8<---- >> Created new Volume="vol-2667", Pool=“client1", MediaType=“file" in catalog. >> Warning: label.c:404 Open File device “storagdev1" (/mnt/storage1) Volume >> "vol-2667" failed: ERR=file_dev.c:189 Could not >> open(/mnt/storage1/vol-2667,CREATE_READ_WRITE,0640): ERR=No space left on >> device >> Warning: label.c:404 Open File device “storagedev1" (/mnt/storage1) Volume >> “vol-2667" failed: ERR=file_dev.c:189 Could not >> open(/mnt/storage1/vol-2667,CREATE_READ_WRITE,0640): ERR=No space left on >> device >> Warning: mount.c:216 Open of File device “storagedev1" (/mnt/storage1) >> Volume "vol-2667" failed: ERR=file_dev.c:189 Could not >> open(/mnt/storage1/vol-2667,CREATE_READ_WRITE,0640): ERR=No space left on >> device >> Marking Volume "vol-2667" in Error in Catalog. > ----8<---- > > Also, notice the cause of the errors on this new volume vol-2667 was due to > "ERR=No space left on device", whereas the initial volume you reported on was > due to "ERR=No such file or directory" > > So, two different problems, two different situations. :) > > Also interesting is the "Error" status where I get "Read-Only" statuses.. Are > you using a version prior to 13.0.2? > > > Best regards, > Bill > > -- > Bill Arlofski > w...@protonmail.com <mailto:w...@protonmail.com>
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
