Hi all,
I use LVM quite a lot.
> richard@backup:~$ sudo lvs|wc -l
> 140
The trouble is, things like device mapper seem to involve lots of name
translations.
So the volume I call
d-rh-rm1-home
(for dirvish backups of /home on rh-rm1 (my (rh) first (1) redmine
(rm) server)) on
vg-backup0
which is understandably known (to me) as
/dev/vg-backup0/d-rh-rm1-home
is then known by its alternative name:
/dev/mapper/vg--backup0-d--rh--rm1--home
because dev mapper seems to need '-' for its own purposes.
But then if systemd has a problem with it, I see a log line like this:
Apr 5 07:06:25 backup systemd[1]:
dev-mapper-vg\x2d\x2dbackup0\x2dd\x2d\x2drh\x2d\x2drm1\x2d\x2dsrv.device:
Job
dev-mapper-vg\x2d\x2dbackup0\x2dd\x2d\x2drh\x2d\x2drm1\x2d\x2dsrv.device/start
failed with result 'timeout'.
in my logcheck email. Which is nearly unintelligible.
Now I could make the effort to avoid using '-' in my volume names (and
mount points, which also get messed up in systemd's reporting).
But is this all really necessary? Can't these tools work without
assigning special meaning to ordinary characters?
(The problem systemd's reporting, of course, is that I must have
forgotten to "systemctl daemon-reload" after editing /etc/fstab ... that
never used to be needed either.)
Grumpily,
Richard
