Contact Details

No response

Is there an existing issue for this?

• I have searched all the existing issues

Priority

low (Default)

Environment

- CubeFS version: 3.4.0
- Deployment mode(docker or standalone or cluster): cluster
- Dependent components:
- OS kernel version(Ubuntu or CentOS): centos
- CPU/Memory:
- Others:

Current Behavior

When the recycle bin feature is enabled for a volume, performing concurrent deletions may result in a client panic due to unexpected behavior or errors

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x95f1ab]

goroutine 1 [running]:
github.com/cubefs/cubefs/sdk/meta.(*Trash).initTrashRootInodeInfo(0xc00064f3b0)
	sdk/meta/trash.go:129 +0x2b
github.com/cubefs/cubefs/sdk/meta.(*Trash).InitTrashRoot(0xc00064f3b0)
	sdk/meta/trash.go:107 +0x275
github.com/cubefs/cubefs/sdk/meta.NewTrash(0xc000c0b500, 0x3c, {0x0, 0x0}, 0xc002fbfa40, 0xa)

Expected Behavior

Experiencing a client panic during the compilation phase can adversely impact business operations, potentially leading to service interruptions or degraded performance

Steps To Reproduce

No response

CubeFS Log

No response

Anything else? (Additional Context)

No response