Description of problem: Running sectool with default filesystem descriptor (03_filesystem.dsc) will cause the filesystem test to fail when the filesystem type is ext4 Version-Release number of selected component (if applicable): sectool-0.9.1-9 How reproducible: Always Steps to Reproduce: 1. Run sectool with default filesystem descriptor file 2. 3. Actual results: Filesystem tests result is FAILURE! Expected results: Filesystem test will result should not be FAILURE!. It could be either PASSED, WARNING, or ERROR Additional info: Modifying /etc/sectool/tests/03_filesystem.dsc and adding ext4 to FSTYPES will fix the problem and allow the test to execute.
I'll add ext4 to the list. But could you please paste all sectool output + mount. I'm suspicious there might another problem too. thnx.
sectool-0.9.3-2.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/sectool-0.9.3-2.fc11
Below is the output of the mount command. [root@esolis ~]# mount /dev/mapper/vg_esolis-lv_root on / type ext4 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw) /dev/sda1 on /boot type ext3 (rw) tmpfs on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) gvfs-fuse-daemon on /home/esolis/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=esolis)
Created attachment 354067 [details] "sectool -a" output I have attached the output of executing sectool -a
Created attachment 354069 [details] "sectool -a -d" output sectool output with debug option set
sectool-0.9.3-2.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update sectool'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7756
sectool-0.9.3-2.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.