You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a low priority list of things which appear out of step with POSIX style fs behaviour. For any other things like this I'll just add to this issue.
already mentioned on the forum, sn_fs reports directory sizes as '0' whereas they appear to be at least the minimum block size (e.g. 4096) on Ubuntu.
ls -al of a directory should include entries for '.' and '..' as below, whereas for sn_fs these are missing.
PS I've attached a script which I used to test my now defunct SAFE Drive, tweaked slightly to test sn_fs and it passes all tests on Ubuntu 20.04. 🎉
You'll have to rename the .txt to .sh to use it of course. test-sn_fs.sh.txt
It expects to be run from the root of a git repo with the script in a tests subdirectory, for example:
cd ~/sn_fs
mkdir -p ~/SAFE
sn_fs ~/SAFE &
./tests/test-sn_fs.sh mock|disk
I'll also try some of the manual tests which gave SAFE Drive problems.
The text was updated successfully, but these errors were encountered:
This is a low priority list of things which appear out of step with POSIX style fs behaviour. For any other things like this I'll just add to this issue.
ls -al
of a directory should include entries for '.' and '..' as below, whereas for sn_fs these are missing.PS I've attached a script which I used to test my now defunct SAFE Drive, tweaked slightly to test sn_fs and it passes all tests on Ubuntu 20.04. 🎉
You'll have to rename the .txt to .sh to use it of course. test-sn_fs.sh.txt
It expects to be run from the root of a git repo with the script in a tests subdirectory, for example:
I'll also try some of the manual tests which gave SAFE Drive problems.
The text was updated successfully, but these errors were encountered: