Mount fails with wrong fs type, bad option, bad superblock

[devent]

Hello, I'm using Convoy, but if I try to setup data containers I get the following error:

sudo docker run -v nginx_cache_data:/var/cache/nginx --volume-driver=convoy --name nginx_cache_data -d erwinnttdata/nginx:latest
docker: Error response from daemon: Failed to execute: mount [/dev/mapper/nginx_cache_data /var/lib/rancher/convoy/devicemapper/mounts/nginx_cache_data], output mount: wrong fs type, bad option, bad superblock on /dev/mapper/nginx_cache_data,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.
, error exit status 32.

This is my Convoy service script.

[Unit]
Description=Convoy Daemon
Requires=docker.service

[Service]
ExecStart=/usr/local/bin/convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6

[Install]
WantedBy=multi-user.target

And Convoy starts up just fine.

sudo systemctl status convoy.service
● convoy.service - Convoy Daemon
   Loaded: loaded (/etc/systemd/system/convoy.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2016-07-12 16:18:15 CEST; 11ms ago
 Main PID: 7789 (convoy)
    Tasks: 5
      CPU: 4ms
   CGroup: /system.slice/convoy.service
           └─7789 /usr/local/bin/convoy daemon --drivers devicemapper --driver-opts dm.datadev=/dev/loop5 --driver-opts dm.metadatadev=/dev/loop6

Jul 12 16:18:15 emlenovo systemd[1]: Started Convoy Daemon.
Jul 12 16:18:15 emlenovo convoy[7789]: time="2016-07-12T16:18:15+02:00" level=debug msg="Found existing config. Ignoring command line opts, loading config from /var/lib/rancher/convoy" pkg=daemon
Jul 12 16:18:15 emlenovo convoy[7789]: time="2016-07-12T16:18:15+02:00" level=debug msg= driver=devicemapper driver_opts=map[dm.datadev:/dev/loop5 dm.metadatadev:/dev/loop6] event=init pkg=daemon reason=prepare r

file /dev/mapper/nginx_cache_data 
/dev/mapper/nginx_cache_data: block special (253/12)

That is weird. Shouldn't the device suppose to be formatted with ext4? That setup was definitely working before for a MySQL Database.

[devent]

Oh, if I use sudo docker run -v vol1:/var/cache/nginx --volume-driver=convoy --name nginx_cache_data -d erwinnttdata/nginx:latest then it works fine. Can't I chose the name arbitrary?

[yasker]

Can it be mkfs cannot recognize underscore_? Can you try only put one underscore in the volume name?

[wilsonp]

Hi

I got the same error ,and I use the 'v1:/v1' so it has nothing with 'mkfs'