Use minio for object storage, vdbench for testing and smooth upgrade of the client, vdbench exit

[YunhuiChen]

What happened:Use minio for object storage, vdbench for testing and smooth upgrade of the client, vdbench exit

What you expected to happen:
1、./juicefs mount redis://127.0.0.1:6379/2 /juicefs1 --cache-dir /data/cache -d
2、start vdbench test
data_errors=1
fsd=fsd1,anchor=/juicefs1,depth=1,width=10,files=5,sizes=(100m,0),shared=yes,openflags=o_direct
fwd=fwd1,fsd=fsd*,threads=10,xfersize=(512,20,4k,20,64k,20,512k,20,1024k,20),fileio=random,fileselect=random,rdpct=50
rd=rd1,fwd=fwd*,fwdrate=max,format=restart,elapsed=2000,interval=1
3、./juicefs mount redis://127.0.0.1:6379/2 /juicefs1 --cache-dir /data/cache -d
4、error :11:15:37.701 localhost-0: 11:15:37.700 op: read lun: /juicefs1/vdb.1_7.dir/vdb_f0034.file lba: 76546048 0x04900000 xfer: 524288 errno: EINTR: 'Interrupted system call'

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?

Environment:

• JuiceFS version (use juicefs --version) or Hadoop Java SDK version:
• Cloud provider or hardware configuration running JuiceFS:
• OS (e.g cat /etc/os-release):
• Kernel (e.g. uname -a):
• Object storage (cloud provider and region, or self maintained):
• Metadata engine info (version, cloud provider managed or self maintained):
• Network connectivity (JuiceFS to metadata engine, JuiceFS to object storage):
• Others:

[zhijian-pro]

juicefs.log

2024-04-16 10:34:34.099472 I | try to restart gracefully
2024-04-16 10:34:37.917566 I | FUSE: interrupt request 61262
2024-04-16 10:34:37.920511 I | writer: Write/Writev failed, err: 2=no such file or directory. opcode: READ

This is the expected behavior and cannot be improved temporarily.

[YunhuiChen]

#4739 (comment)

[SandyXSD]

It happens not only on vdbench, but also when using ls or fio.