View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000841 | bareos-core | director | public | 2017-08-07 20:12 | 2017-10-13 12:05 |
Reporter | markus | Assigned To | pstorz | ||
Priority | normal | Severity | major | Reproducibility | sometimes |
Status | closed | Resolution | no change required | ||
Platform | Linux | OS | CentOS | OS Version | 7 |
Product Version | 16.2.6 | ||||
Summary | 0000841: Bareos tries to mount volume from another storage | ||||
Description | Sometimes i have failed backup job with the similar errors: 23-Feb 01:00 backup-sd JobId 18763: Warning: Volume "Incremental-1656" not on device "nc rss01" (/mnt/backup/ncrss01). 23-Feb 01:00 backup-sd JobId 18763: Marking Volume "Incremental-1656" in Error in Catalo g. 23-Feb 01:00 backup-sd JobId 18763: Warning: Volume "Incremental-1656" not on device "nc rss01" (/mnt/backup/ncrss01). 23-Feb 01:00 backup-sd JobId 18763: Marking Volume "Incremental-1656" in Error in Catalo g. 23-Feb 01:00 backup-sd JobId 18763: Warning: mount.c:248 Open device "ncrss01" (/mnt/bac kup/ncrss01) Volume "Incremental-1656" failed: ERR=dev.c:661 Could not open: /mnt/backup/ncrss01/Incremental-1656, ERR=No such file or directory I have two Storages. Common storage FileStorage01 and individual ncrss01-storage for job ncrss01-file-job Job { Name = "ncrss01-file-job" Client = "ncrss01-fd" Type = Backup JobDefs = file Storage = ncrss01-storage } JobDefs { Name = file Type = Backup Level = Incremental FileSet = client_self_fileset Schedule = MonthlyCycle Storage = FileStorage01 Messages = Standard Pool = Incremental Full Backup Pool = Full Differential Backup Pool = Differential Incremental Backup Pool = Incremental Priority = 5 Write Bootstrap' = "/var/lib/bareos/%c.bsr" } DIR config Storage { Name = "FileStorage01" Password = "pass1" Address = backup Device = bareos01 Media Type = File } Storage { Name = "ncrss01-storage" Password = "pass2" Address = backup Device = ncrss01 Media Type = File } SD config Device { Name = bareos01 Media Type = File Device Type = File Archive Device = /mnt/backup/bareos01 LabelMedia = yes Random Access = yes AutomaticMount = yes RemovableMedia = no AlwaysOpen = no } Device { Name = ncrss01 Media Type = File Device Type = File Archive Device = /mnt/backup/ncrss01 LabelMedia = yes Random Access = yes AutomaticMount = yes RemovableMedia = no AlwaysOpen = no } Volume Incremental-1656 belongs FileStorage01 *llist volume=Incremental-1656 Using Catalog "MyCatalog" MediaId: 1,656 VolumeName: Incremental-1656 Slot: 0 PoolId: 10 MediaType: File FirstWritten: 2017-02-22 01:02:27 LastWritten: 2017-02-23 01:00:05 LabelDate: 2017-02-22 01:02:27 VolJobs: 36 VolFiles: 8 VolBlocks: 548,195 VolMounts: 36 VolBytes: 35,363,023,779 VolErrors: 0 VolWrites: 548,196 VolCapacityBytes: 0 VolStatus: Error Enabled: 1 Recycle: 1 VolRetention: 1,209,600 VolUseDuration: 0 MaxVolJobs: 0 MaxVolFiles: 0 MaxVolBytes: 53,687,091,200 InChanger: 0 EndFile: 8 EndBlock: 1,003,284,234 LabelType: 0 StorageId: 3 DeviceId: 0 LocationId: 0 RecycleCount: 0 InitialWrite: 0000-00-00 00:00:00 ScratchPoolId: 0 RecyclePoolId: 0 Comment: NULL Storage: FileStorage01 Why bareos tries to mount volume from another storage? | ||||
Tags | No tags attached. | ||||
I have the same issue with 16.2.5 I experience this as a permanent error. I can help with debugging. My scenario is also a set of 2 usb-disks mounted on 2 different folders. |
|
Please read the docs! http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirStorageMedia%20Type -> If you are writing to disk Volumes, you must make doubly sure that each Device resource defined in the Storage daemon (and hence in the Director’s conf file) has a unique media type. Otherwise Bareos may assume, these Volumes can be mounted and read by any Storage daemon File device. |
|
http://doc.bareos.org/master/html/bareos-manual-main-reference.html#directiveDirStorageMedia%20Type If you are writing to disk Volumes, you must make doubly sure that each Device resource defined in the Storage daemon (and hence in the Director’s conf file) has a unique media type. Otherwise Bareos may assume, these Volumes can be mounted and read by any Storage daemon File device. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2017-08-07 20:12 | markus | New Issue | |
2017-10-11 23:54 | marten | Note Added: 0002787 | |
2017-10-13 12:04 | pstorz | Note Added: 0002791 | |
2017-10-13 12:05 | pstorz | Note Added: 0002792 | |
2017-10-13 12:05 | pstorz | Status | new => closed |
2017-10-13 12:05 | pstorz | Assigned To | => pstorz |
2017-10-13 12:05 | pstorz | Resolution | open => no change required |