Hi Dave, Thanks for your quick reply, and still mount failed. But I can not get some useful message from dmesg.
# mount -t virtio_fs myfs /mnt/virtiofs/ mount: wrong fs type, bad option, bad superblock on myfs, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. On 2019/7/23 16:31, Dr. David Alan Gilbert wrote: > * piaojun ([email protected]) wrote: >> Hi, >> >> I got a problem when mounting virtiofs in kernel5.1 as below: >> >> fuse: loading out-of-tree module taints kernel. >> fuse: module verification failed: signature and/or required key missing - >> tainting kernel >> fuse init (API version 7.29) >> virtio_fs virtio1: Cache len: 0x80000000 @ 0x180000000 >> virtio1 initialised, 524288 pages in 12ms >> virtio_fs_find_instance: fs->tag myfs, tag /dev/null >> virtio-fs: tag </dev/null> not found >> Mounting FUSE Control File System... >> [/bin/bash]: [mount -t virtio_fs /dev/null /mnt/virtiofs/ -o tag=myfs] >> return code=[32], execute failed by [root(uid=0)] from [pts/0 (9.4.90.78)] >> >> And my kernel code is: >> https://github.com/rhvgoyal/linux/commits/virtio-fs-dev-5.1 >> >> I wonder if the mount command has been changed? > > There was a change that went in last night, I believe the new format is: > > mount -t virtio_fs myfs /mnt/virtiofs/ > > with the tagname going into the device position. > > Does that work? > > Dave > > >> Thanks, >> Jun >> >> _______________________________________________ >> Virtio-fs mailing list >> [email protected] >> https://www.redhat.com/mailman/listinfo/virtio-fs > -- > Dr. David Alan Gilbert / [email protected] / Manchester, UK > . >
