Open dmanchado opened 8 years ago
I ran into a similar issue; the error is the same "Not a directory @ rb_sysopen". In my case, the mounts are files. @dmanchado's PR (which expired due to inactivity after he didn't respond to a request to add a unit test and a changelog) checks the filesystem type to see if it's none
; my mounts have type ext4
, so his fix wouldn't address my issue.
I think it would be better to check whether the mount is a directory than to check its fstype. I'm assuming that dmanchado's named.conf, et al are not directories.
If it's not a directory, I'm not sure what further recourse there is to verify that it's writable.
When checking filesystems writable using auto mode it complains of chrooted mounts (bind dns in my case).
Check failed to run: Not a directory @ rb_sysopen - /var/named/chroot/etc/named.conf/.sensu20160621-20363-mv70jc
I have not seen a pattern to filter out when checking /proc/self/mounts, if we were using the output from mount command it would make sense to filter out the' type none' ones.
/proc/self/mounts
check-fs-writable.rb -a