From 5328d534a0b576ecff933de875b4d0d7f95c8cd6 Mon Sep 17 00:00:00 2001 From: Dmitry Marakasov Date: Wed, 5 Aug 2015 19:41:08 +0000 Subject: [PATCH] - Mentione another ublio bug: Current implementation does not properly work with partitions of size which is not a multiply of UBLIO_BLOCKSIZE (cannot read/write last cluster). For instance, you may not be able to create ntfs filesystem because of this with Initializing device with zeroes: 99%Failed to complete writing to /dev/ada0s1 after three retries. --- sysutils/fusefs-ntfs/files/README.FreeBSD | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/sysutils/fusefs-ntfs/files/README.FreeBSD b/sysutils/fusefs-ntfs/files/README.FreeBSD index f1c101be8952..0c9905d230f7 100644 --- a/sysutils/fusefs-ntfs/files/README.FreeBSD +++ b/sysutils/fusefs-ntfs/files/README.FreeBSD @@ -105,9 +105,16 @@ useful for testing purposes and in practice has no use. 5. Known issues ============================================================================== -For mkntfs(8) -F must be used to allow non-block device to be processed. +- For mkntfs(8) -F must be used to allow non-block device to be processed. -When reading/writting the same file repeatedly while doing many simultaneous +- Current implementation does not properly work with partitions of size which +is not a multiply of UBLIO_BLOCKSIZE (cannot read/write last cluster). For +instance, you may not be able to create ntfs filesystem because of this with + + Initializing device with zeroes: 99%Failed to complete writing to + /dev/ada0s1 after three retries. + +- When reading/writting the same file repeatedly while doing many simultaneous operations on different files sometimes the former one fails: read(2) returns -1 and sets errno to EAGAIN. This is because of a difference between the FUSE kernel implementation in Linux and FreeBSD, and is being worked on. An example