vchanger keeps mounting wrong volume

[Erich Eckner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

I have a disk-based bareos setup with vchanger deploying files across
multiple volumes (thanks, spadajspadaj, for helping me set this up). This
worked fine until a few days ago, when vchanger mounted the wrong volume:

Device "vchanger-1-0" (/var/spool/vchanger/vchanger-1/0) is waiting for sysop intervention:
Volume: vchanger-1_0005_0153
Pool: Incremental
Media type: Offsite-File
Device is BLOCKED waiting for mount of volume "vchanger-1_0005_0292",
Pool: Incremental
Media type: Offsite-File
Slot 753 is loaded in drive 0.
Total Bytes Read=213 Blocks Read=1 Bytes/block=213
Positioned at File=0 Block=0

There is nothing reading from this device, there are only jobs waiting for
1_0005_0292 to be mounted. If I tell vchanger (via bconsole) to mount any
volume, it only mounts 1_0005_0153 again, which is also evident in the fs
itself:

/var/spool/vchanger/vchanger-1/0 -> /mnt/bareos/mnt6/vchanger-1_0005_0153

If I change that symlink and the info in
/var/spool/vchanger/vchanger-1/drive_state-0 manually to point to the
right volume, vchanger reports the right volume, but bareos does not
notice the change. So here are my questions:

Has anyone had similar trouble before and how did you solve it?

If not, how can I refresh the info in bconsole without re-mounting (this
will only mount the wrong volume again)?

regards,
Erich

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl76zIQACgkQCu7JB1Xa
e1ohxRAArGXw61HJ8eaxMjHYnDRrhAWNEq3mKWUvRUVKEp2bRPXm62VLuTLKtQMU
DHdWMuxF+W9A9M+oX7wJIh87xG95Zu4SBtQS0v0uo+RjinODJsR9z5M+zA4G31Oy
24ubgHyBnOF+o7HkXBQLVT3ll/5xjkI1NJTaL40EHmrsDmjFPjno5qSQWTQrEcXM
T5QxQVS/JAe+dePtuaFmIjd7X6H9JseLljsifnh0sbTuHaS8+WhBAWdnibDNVwzu
u8cw2VdL91oUzdDuDXSQDyNg1OW/wTDQ2ys+rY/mGnSpeQ85TnwTuOC7Y8mNjn+H
zjpe7mMC6m+4mDxNo2kJ8FMAr2ZaeKapLghLk/eVYqMQut+IViLfsdKqmVmd3A8R
V9+DpgPyd4ygzo+7NbxYP+oFzLbLd6JRaULsedyYyg+o7mEqZC6sdTLY9GULCe9a
h0pKbP4ch0XTurz85+4HVP+GHytaLNRObF6CJBD/QYtOTvoYVaHA1sCIovEOkJjd
/finBWWRicA2DaFbUDvmi/PUN2E32FqStbmT/TBZ7A50GYlZzW9RhiCEVeG92vFL
zwTpelcACBKd4O8jIi1H/nDEY9lzSlnLigmZLKdlheJszjKRrfDNkXblpQjLIGYT
BVJOCfBxOsELhm8G5Xvk9c8uub5MzS9OAQJmL0eN9RnW9x6Sv5A=
=m5OD
-----END PGP SIGNATURE-----

[Spadajspadaj]

On 30.06.2020 07:24, Erich Eckner wrote:
> Device "vchanger-1-0" (/var/spool/vchanger/vchanger-1/0) is waiting
> for sysop intervention:
>     Volume:      vchanger-1_0005_0153
>     Pool:        Incremental
>     Media type:  Offsite-File
>     Device is BLOCKED waiting for mount of volume "vchanger-1_0005_0292",
>        Pool:        Incremental
>        Media type:  Offsite-File
>     Slot 753 is loaded in drive 0.
>     Total Bytes Read=213 Blocks Read=1 Bytes/block=213
>     Positioned at File=0 Block=0
>
> There is nothing reading from this device, there are only jobs waiting
> for 1_0005_0292 to be mounted. If I tell vchanger (via bconsole) to
> mount any volume, it only mounts 1_0005_0153 again, which is also
> evident in the fs itself:
>
> /var/spool/vchanger/vchanger-1/0 -> /mnt/bareos/mnt6/vchanger-1_0005_0153
>
> If I change that symlink and the info in
> /var/spool/vchanger/vchanger-1/drive_state-0 manually to point to the
> right volume, vchanger reports the right volume, but bareos does not
> notice the change. So here are my questions:
>

I'd try running director and sd with higher debug level and see what's
happening.

> If not, how can I refresh the info in bconsole without re-mounting
> (this will only mount the wrong volume again)?

update slots doesn't help?

[Erich Eckner]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

Thanks for the suggestion, I'll do this next time, I have to look into
this (see below).

>
>
> > If not, how can I refresh the info in bconsole without re-mounting
(this will only mount the wrong volume again)?
>
>
> update slots doesn't help?

Yes, it does help! Great :-) Bconsole re-indexed some "tapes" and now I
can mount, what I expect it to mount via "mount ...".

Now I feel kind of stupid for not looking through the possibilities, that
bconsole offers :-/

Btw: The source of the issue seems to be, that I had once not all
directories properly mounted, so all vchanger-1_0004_xxxx volumes were
missing, and I think, bareos might have re-indexed the others, then (or
maybe, I did).

regards,
Erich


-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE3p92iMrPBP64GmxZCu7JB1Xae1oFAl77wNAACgkQCu7JB1Xa
e1rdTRAAoGzBNyPxwB9BrUwHOG49NgQKLpCI2TByxFKmyaXvnl1jVpnzWbjXOd1c
Ui3ui/lHhFIPqotprMz1At1O+GacAA8Vm+iGuNcIQL6nTOIHNF2ZlfunmDx/imn8
/47TtqHluI4FPNCC7a933Sfb/04SCwS0YhKEJLAC7y0aWp6XPc8bC/9QuIUmuAuc
SJbvEZIR6JiZ+evQ1UaSBjTyfch8JMpSILmatN/KG3TZf6e2n24WhUCMO6KixDDB
/uLpaT66Kxy6LHI2CnGSh79lXbm3xugR6g5m//jVPXREsyiF8+WdNuCQeC+76FtG
7Y67lKq2CmsTLchHnq9HGe/D0d7F9AZIjerT5qilZLvZlhau4wd4liYyt+oX2SFj
geqnQU6Ue/yq5Bzt+y12M9Oy3V2PJtsJcg0EJnIXiQrRBhL4wJAY4w+c8HuObj4x
52OyuvdS5TVgEuB2jnr00q2XbXwaVRRhki2wSkTGz8ea+kRFS5HHjx6tXrv9ROec
omeC4kP1RJgLI5tt9Gu0Q1AM7yW4lM/T7BZkrvhvTCO8CLs3NolDscP/iqmDESF5
X/7XwesSeg6rsE9NaeZCNk4gRuvWxKaz5C/Gb5ThUqboPDULxZvviWkOxuEYr8Oi
q8anyitNZC6+kjx3gghiYxr6Zq383aQf3oIDz5TcKcwF+RxGrM4=
=4N0a
-----END PGP SIGNATURE-----