Description of problem: If i give guestmount a set of mount options these are not respected and instead it mount the filesystem as follows: guestmount on /mnt/guest_snapshot type fuse.guestmount (rw,nosuid,nodev) I had tried: guestmount -a /dev/images/autest -m /dev/sda1:/:defaults,noatime /mnt/guest_snapshot Which for my other file systems if mounting a normal disk then I get /dev/sda1 on / type ext4 (rw,noatime,errors=remount-ro) Version-Release number of selected component (if applicable): guestmount 1.15.10 - using development GIT checkout from last week. How reproducible: 100% Steps to Reproduce: 1. guestmount -a /dev/images/autest -m /dev/sda1:/:defaults,noatime /mnt/guest_snapshot 2. mount Actual results: guestmount on /mnt/guest_snapshot type fuse.guestmount (rw,nosuid,nodev) Expected results: guestmount on /mnt/guest_snapshot type fuse.guestmount (rw,noatime,errors=remount-ro) Additional info:
I think this might be controlled by FUSE itself. Did you have a look at 'guestmount --fuse-help' output?
Mark, since you fixed this with a guestmount FUSE option, could you summarise how it was fixed here and close the bug. This ensures there is a record for other users.
I fixed this by adding a '-o' to the guestmount command, this then allowed the mount to process correctly. guestmount -a /dev/images/autest -m /dev/sda1 /mnt/guest_snapshot -o noatime,dev,sync
Interesting, I didn't know you could use 'ordinary' mount options there. I thought it was limited to FUSE options, so you learn something new every day.
After some trial and error, I can confirm that using "-o dev" works (e.g.), but only if you call guestmount as root. Otherwise, the options are ignored are even rejected with an error message.