Closed mhtvsSFrpHdE closed 1 year ago
@mhtvsSFrpHdE What are your formatting options for exfat so I can try to recreate your scenario?
@mhtvsSFrpHdE What are your formatting options for exfat so I can try to recreate your scenario?
gparted default format option, dnf install gparted
or version 1.4.0
Another is just dual boot to Windows 11 22H2 then format D: /fs:exfat
OK. I will try to run through this exercise over the weekend. But just a few things to note:
@pkoutoupis
Not a very critical issue for me right now because I use kernel 6.1.12-200.fc37
which is come with NTFS support so I'm using NTFS to do cross device access.
For 3.
I'm sorry, I didn't realize that issue is exist with title "4K Logical Drives",
My attention is all drawn to exfat.
In my mind, I seem to mount it successfully and viewed file content with ls command for once,
before combine it with rapiddisk. I can't recall the details, and now I formatted it to NTFS.
I do a test here:
/dev/nvme0n1p8
sudo mount /dev/nvme0n1p8 ~/ramdisk
sudo nano ~/ramdisk/1.txt
type abc savesudo cat ~/ramdisk/1.txt
says abc, so it seems to work in both write and read operationTo create ramdisk on a NVME SSD seems funny because they are already fast.
No, what I'm doing is try to reduce total write to nand.
Read once, write x terabytes who knows, and dm-writecache flush 2GB to disk, unmount.
Oh, I overlooked that detail. I didn't realize that you are using writeback. OK, that relies on a different module: dm_writecache and not rapiddisk-cache. Anyway, thank you for the details. I will let you know what I find out this weekend.
OK. I was able to reproduce. So, I haven't dived too deep into it but it looks as if there is a block alignment issue introduced by dm_writecache. My underlying device which is a 512 logical block size is formatted with exfat and it expects to find the boot sector, superblock, etc at certain regions BUT dm_writecache changed the logical block size to 4096 (or 4K) and after the mapping, it fails to mount. The only way around that so far, is to format the dm_writecache mapping and THEN mount:
petros@ubuntudevvm:~/rapiddisk/src$ sudo mkfs.exfat -n TEST /dev/mapper/rc-wb_loop5
exfatprogs version : 1.1.3
Creating exFAT filesystem(/dev/mapper/rc-wb_loop5, cluster size=32768)
Writing volume boot record: done
Writing backup volume boot record: done
Fat table creation: done
Allocation bitmap creation: done
Upcase table creation: done
Writing root directory entry: done
Synchronizing...
exFAT format complete!
petros@ubuntudevvm:~/rapiddisk/src$ sudo mount /dev/mapper/rc-wb_loop5 /mnt/
petros@ubuntudevvm:~/rapiddisk/src$ df -t exfat
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/mapper/rc-wb_loop5 522240 96 522144 1% /mnt
Unfortunately, I cannot change the dm_writecache logical block size. It is an upstream driver not maintained by the RapidDisk project and also, the 4K setting may play an integral part to the way it works.
Thank you for the information! I continue to stick with my NTFS configuration then.
NTFS file system with write back works fine
Sounds good. I will just close this comment then and if you feel the need to reopen or open a new one, do not hesitate. Thank you.
Formatted use either Windows
format.exe
and Linuxgparted
and get these when
mount
If formatted to ext4, the issue is gone.
But I'm interested to access this drive on Windows natively.