[Bug 206978] filesystems/fusefs-ntfs: Disable UBLIO as it breaks mkntfs
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 18 Feb 2025 14:43:24 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206978 --- Comment #30 from Alexey Dokuchaev <danfe@FreeBSD.org> --- (In reply to Zane C. Bowers-Hadley from comment #29) > Also are we sure that copying and the like is consistently working > properly given these other issues? I use it every day, copying files in and out without issues, at least I don't encounter any data corruption. > Waiting for a fix has been a decade now. Okay, let's try to reproduce the problem. Original "terminal output" attachment shows version 2017.3.23 and logs the creation of 14G filesystem. We need some newish data: $ pkg query %Ok=%Ov fusefs-ntfs-2022.10.3 CRYPTO=off DOCS=on EXTRAS=on LOCK=on UBLIO=on $ su - # mdconfig -t malloc -s 14G md0 # mkntfs --partition-start 63 --label NTFS-MBR --quick --debug /dev/md0 The number of sectors per track was not specified [...] has been set to 0. The number of heads was not specified [...] has been set to 0. Cluster size has been automatically set to 4096 bytes. [...] Creating NTFS volume structures. [...] Creating $Reparse (mft record 26) Syncing root directory index record. Syncing $Bitmap. Syncing $MFT. Updating $MFTMirr. Syncing device. mkntfs completed successfully. Have a nice day. # echo $? 0 Does it only fail when backed by the real storage? I don't have a spare 14G lying around ATM. -- You are receiving this mail because: You are the assignee for the bug.