CI: error: no such table: jfs_chunk in random test.

[zhoucheng361]

What happened:

https://github.com/juicedata/juicefs/actions/runs/13861670461/job/38791453049

2025/03/14 17:10:03.468081 juicefs[5684] <ERROR>: error: no such table: jfs_chunk
goroutine 1362195 [running]:
runtime/debug.Stack()
	/opt/hostedtoolcache/go/1.23.7/x64/src/runtime/debug/stack.go:26 +0x5e
github.com/juicedata/juicefs/pkg/meta.errno({0x1c974[40](https://github.com/juicedata/juicefs/actions/runs/13861670461/job/38791453049#step:6:41), 0xc009497e30})
	/home/runner/work/juicefs/juicefs/pkg/meta/utils.go:127 +0xfc
github.com/juicedata/juicefs/pkg/meta.(*dbMeta).doRead(0xc00b1777d0, {0x1cb9178, 0xc00a7dbe00}, 0x2, 0x0)
	/home/runner/work/juicefs/juicefs/pkg/meta/sql.go:2562 +0xda
github.com/juicedata/juicefs/pkg/meta.(*baseMeta).compactChunk(0xc00dbff408, 0x2, 0x0, 0x0, 0x0)
	/home/runner/work/juicefs/juicefs/pkg/meta/base.go:2228 +0x2fa
created by github.com/juicedata/juicefs/pkg/meta.(*baseMeta).Read in goroutine 37
	/home/runner/work/juicefs/juicefs/pkg/meta/base.go:1612 +0x517 [[email protected]:127]

2025/03/14 17:28:44.045022 juicefs[5684] <ERROR>: error: sql: database is closed
goroutine 10901675 [running]:
runtime/debug.Stack()
	/opt/hostedtoolcache/go/1.23.7/x64/src/runtime/debug/stack.go:26 +0x5e
github.com/juicedata/juicefs/pkg/meta.errno({0x1c97280, 0x2922340})
	/home/runner/work/juicefs/juicefs/pkg/meta/utils.go:127 +0xfc
github.com/juicedata/juicefs/pkg/meta.(*dbMeta).doRead(0xc02d2b0120, {0x1cb9178, 0xc0643dac00}, 0x6, 0x0)
	/home/runner/work/juicefs/juicefs/pkg/meta/sql.go:2562 +0xda
github.com/juicedata/juicefs/pkg/meta.(*baseMeta).compactChunk(0xc063bd8008, 0x6, 0x0, 0x0, 0x0)
	/home/runner/work/juicefs/juicefs/pkg/meta/base.go:2228 +0x2fa
created by github.com/juicedata/juicefs/pkg/meta.(*baseMeta).Read in goroutine 37
	/home/runner/work/juicefs/juicefs/pkg/meta/base.go:1612 +0x517 [[email protected]:127]

What you expected to happen:

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:

[jiefenghuang]

The issue arises because the ‘compact’ goroutine continues to execute even after the metadata has been Reset. For now, we can disregard this problem.