Closed lnsyyj closed 2 years ago
I only see these here:
Error: EINVAL: 'Invalid argument'
lba: 0
xfersize: 1024
These are correct, minimal writable unit / sector size in Vitastor is 4096 bytes.
Oh, does this mean that overwriting a 1KB file will have an error?
vdbench added openflag=o_direct parameter, it is no problem not to use this parameter
root@vita-1:~# xfs_info /root/performance/
meta-data=/dev/nbd0 isize=512 agcount=11, agsize=268435455 blks
= sectsz=4096 attr=2, projid32bit=1
= crc=1 finobt=1, sparse=1, rmapbt=0
= reflink=1 bigtime=0
data = bsize=4096 blocks=2952790005, imaxpct=5
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0, ftype=1
log =internal log bsize=4096 blocks=521728, version=2
= sectsz=4096 sunit=1 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
Oh, does this mean that overwriting a 1KB file will have an error?
As I understand all file systems in Linux use 4 KB block size. So when you overwrite 1 KB you actually overwrite 4 KB. :-) But if a tool tries to do O_DIRECT reads or writes smaller than 4 KB - it gets an error, yes. It's basically the same as HDD/SSD switched to 4 KB sectors.
Oh oh, got it. I guess this can be summed up as users use QA.
Hi @vitalif ,
When I format the xfs file system with vitastor nbd and use the test tool vdbench to read and write, the following problems occur occasionally. The performance of vitastor is very good now, and I think it will be perfect if I increase the stability.
vdbench log
file size