Description of problem: $ findmnt -m -O nosuid TARGET SOURCE FSTYPE OPTIONS /proc proc proc rw,relatime /sys sysfs sysfs rw,relatime,seclabel /dev devtmpfs devtmpfs rw,nosuid,relatime,seclabel,size=3980808k,nr_inodes=995202,mode=755 /dev/pts devpts devpts rw,relatime,seclabel,gid=5,mode=620,ptmxmode=000 /dev/shm tmpfs tmpfs rw,relatime,seclabel / /dev/sda2 ext4 rw,noatime,nodiratime,seclabel,user_xattr,barrier=1,data=ordered /run tmpfs tmpfs rw,nosuid,nodev,relatime,seclabel,mode=755 Most of these filesystems aren't mounted with nosuid. Similarly with 'noatime' Version-Release number of selected component (if applicable): util-linux-2.20.1-2.fc16.x86_64 How reproducible: 100% Steps to Reproduce: 1. play with findmnt
The "no" is interpreted as prefix, so the command returns all entries where is not "suid" option. This is expected behaviour... Anyway, I have improved the pattern evaluation and now you can use "+" prefix to disable "no" prefix interpretation -- it means that "+noauto" will return entries where is *literally* "noauto" option: $ findmnt --fstab -O "+noauto" TARGET SOURCE FSTYPE OPTIONS /mnt/store sr.net.home:/mnt/store nfs noauto /mnt/loop /home/fs-images/ext2.img auto defaults,noauto This change will available in the next upstream release (and F17).