开发者版:部分数据库损坏了且无法修复,能删除吗?

我进入容器后运行了seaf-gc.sh脚本,提示有几个数据库损坏了,然后我运行了seaf-fsck.sh脚本修复,但提示无法修复,怎么办,能删除吗?
以下是返回的信息:
root@68cf4893f6b8:/opt/seatable/seatable-server-latest# ./seaf-gc.sh

Starting seafserv-gc, please wait …
2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo plugins repo(e11350a1-d3a4-4b20-9422-157f9805ea4f)
2023-09-09 20:38:10 gc-core.c(387): GC started. Total block number is 173.
2023-09-09 20:38:10 gc-core.c(41): GC index size is 1024 Byte.
2023-09-09 20:38:10 gc-core.c(412): Populating index.
2023-09-09 20:38:10 gc-core.c(187): Populating index for repo e11350a1.
2023-09-09 20:38:10 gc-core.c(240): Traversed 236 commits, 173 blocks.
2023-09-09 20:38:10 gc-core.c(430): Scanning and deleting unused blocks.
2023-09-09 20:38:10 gc-core.c(467): GC finished. 173 blocks total, about 173 reachable blocks, 0 blocks are removed.

2023-09-09 20:38:10 repo-mgr.c(295): Commit 267f45a6232e5715de5f2bad3dfddb24759e9e63 is missing
2023-09-09 20:38:10 gc-core.c(554): Repo dbb8e20c-370a-4bf9-b521-8d40b6657765 is damaged, skip GC.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo My Workspace(d0d5ee80-d1dc-463c-94d1-29d42f8717ea)
2023-09-09 20:38:10 gc-core.c(365): No blocks. Skip GC.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo My Workspace(c0e5514b-0b7d-417a-88ef-1ad2f982bdba)
2023-09-09 20:38:10 gc-core.c(387): GC started. Total block number is 293.
2023-09-09 20:38:10 gc-core.c(41): GC index size is 1024 Byte.
2023-09-09 20:38:10 gc-core.c(412): Populating index.
2023-09-09 20:38:10 gc-core.c(187): Populating index for repo c0e5514b.
2023-09-09 20:38:10 gc-core.c(240): Traversed 367 commits, 293 blocks.
2023-09-09 20:38:10 gc-core.c(430): Scanning and deleting unused blocks.
2023-09-09 20:38:10 gc-core.c(467): GC finished. 293 blocks total, about 293 reachable blocks, 0 blocks are removed.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo My Workspace(999e8090-e1be-4c1a-aa64-8d4f4de50a50)
2023-09-09 20:38:10 gc-core.c(365): No blocks. Skip GC.

2023-09-09 20:38:10 repo-mgr.c(295): Commit 328a62a7738258f26c0d48fa7b515c5b82d95c22 is missing
2023-09-09 20:38:10 gc-core.c(554): Repo 9596e3c1-8503-4072-b432-b11d33a3b25a is damaged, skip GC.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo My Workspace(93b262fe-5f3a-4133-a94e-553694ccc80f)
2023-09-09 20:38:10 gc-core.c(365): No blocks. Skip GC.

2023-09-09 20:38:10 repo-mgr.c(295): Commit 9977449436e1e4bea093d490f48bc168c15e3fe1 is missing
2023-09-09 20:38:10 gc-core.c(554): Repo 93686886-93e5-4fbf-b2b1-db2ce1db5dfa is damaged, skip GC.

2023-09-09 20:38:10 repo-mgr.c(295): Commit b08609a44d3b7d0409258c83786436dc502ec31b is missing
2023-09-09 20:38:10 gc-core.c(554): Repo 6ee6e482-6218-47cc-9036-d5a965d15a13 is damaged, skip GC.

2023-09-09 20:38:10 repo-mgr.c(295): Commit 6a19c0bac4f1a4180117a53d4b359f22452ca4d2 is missing
2023-09-09 20:38:10 gc-core.c(554): Repo 6ed8af32-e5ad-46f6-a313-040c3a4fee7f is damaged, skip GC.

2023-09-09 20:38:10 repo-mgr.c(295): Commit edd1c1862d44b7edc3cf526f01365e869b6bb5f6 is missing
2023-09-09 20:38:10 gc-core.c(554): Repo 56824973-9b96-4b18-9016-f53dcff03162 is damaged, skip GC.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo plugins repo(384d0da6-6306-4e73-bd6e-b6a92b298bb6)
2023-09-09 20:38:10 gc-core.c(365): No blocks. Skip GC.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo My Workspace(25d2e8df-2faa-4060-bb7f-f7b7dd585268)
2023-09-09 20:38:10 gc-core.c(365): No blocks. Skip GC.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo My Library Template(193e7e17-53a2-4d00-8cde-1d3cc12a3ec7)
2023-09-09 20:38:10 gc-core.c(365): No blocks. Skip GC.

2023-09-09 20:38:10 gc-core.c(559): GC version 1 repo My Workspace(0c3f0fab-b781-4678-8f34-f085ad5d2c4e)
2023-09-09 20:38:10 gc-core.c(387): GC started. Total block number is 101.
2023-09-09 20:38:10 gc-core.c(41): GC index size is 1024 Byte.
2023-09-09 20:38:10 gc-core.c(412): Populating index.
2023-09-09 20:38:10 gc-core.c(187): Populating index for repo 0c3f0fab.
2023-09-09 20:38:10 gc-core.c(240): Traversed 219 commits, 101 blocks.
2023-09-09 20:38:10 gc-core.c(430): Scanning and deleting unused blocks.
2023-09-09 20:38:10 gc-core.c(467): GC finished. 101 blocks total, about 101 reachable blocks, 0 blocks are removed.

2023-09-09 20:38:10 repo-mgr.c(295): Commit b5c83dc9fb3e7901eb336fdc76b1ba09ea725cc6 is missing
2023-09-09 20:38:10 gc-core.c(554): Repo 08d08f48-4af3-4539-9c4d-3a4c638b1979 is damaged, skip GC.

2023-09-09 20:38:10 gc-core.c(504): === Repos deleted by users ===
2023-09-09 20:38:10 gc-core.c(576): === GC is finished ===
2023-09-09 20:38:10 gc-core.c(579): The following repos are damaged. You can run seaf-fsck to fix them.
2023-09-09 20:38:10 gc-core.c(583): 08d08f48-4af3-4539-9c4d-3a4c638b1979
2023-09-09 20:38:10 gc-core.c(583): 56824973-9b96-4b18-9016-f53dcff03162
2023-09-09 20:38:10 gc-core.c(583): 6ed8af32-e5ad-46f6-a313-040c3a4fee7f
2023-09-09 20:38:10 gc-core.c(583): 6ee6e482-6218-47cc-9036-d5a965d15a13
2023-09-09 20:38:10 gc-core.c(583): 93686886-93e5-4fbf-b2b1-db2ce1db5dfa
2023-09-09 20:38:10 gc-core.c(583): 9596e3c1-8503-4072-b432-b11d33a3b25a
2023-09-09 20:38:10 gc-core.c(583): dbb8e20c-370a-4bf9-b521-8d40b6657765
seafserv-gc run done

Done.
root@68cf4893f6b8:/opt/seatable/seatable-server-latest# ./seaf-fsck.sh -r

Starting seaf-fsck, please wait …

2023-09-09 20:39:19 fsck.c(599): Running fsck for repo e11350a1-d3a4-4b20-9422-157f9805ea4f.
2023-09-09 20:39:19 fsck.c(424): Checking file system integrity of repo plugins repo(e11350a1)…
2023-09-09 20:39:19 fsck.c(663): Fsck finished for repo e11350a1.

2023-09-09 20:39:19 fsck.c(599): Running fsck for repo dbb8e20c-370a-4bf9-b521-8d40b6657765.
2023-09-09 20:39:19 repo-mgr.c(295): Commit 267f45a6232e5715de5f2bad3dfddb24759e9e63 is missing
2023-09-09 20:39:19 fsck.c(615): Repo dbb8e20c HEAD commit is damaged, need to restore to an old version.
2023-09-09 20:39:19 fsck.c(510): Scanning available commits…
2023-09-09 20:39:19 fsck.c(516): No available commits for repo dbb8e20c, can’t be repaired.
2023-09-09 20:39:19 fsck.c(663): Fsck finished for repo dbb8e20c.

2023-09-09 20:39:19 fsck.c(599): Running fsck for repo d0d5ee80-d1dc-463c-94d1-29d42f8717ea.
2023-09-09 20:39:19 fsck.c(424): Checking file system integrity of repo My Workspace(d0d5ee80)…
2023-09-09 20:39:19 fsck.c(663): Fsck finished for repo d0d5ee80.

2023-09-09 20:39:19 fsck.c(599): Running fsck for repo c0e5514b-0b7d-417a-88ef-1ad2f982bdba.
2023-09-09 20:39:19 fsck.c(424): Checking file system integrity of repo My Workspace(c0e5514b)…
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo c0e5514b.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 999e8090-e1be-4c1a-aa64-8d4f4de50a50.
2023-09-09 20:39:21 fsck.c(424): Checking file system integrity of repo My Workspace(999e8090)…
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 999e8090.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 9596e3c1-8503-4072-b432-b11d33a3b25a.
2023-09-09 20:39:21 repo-mgr.c(295): Commit 328a62a7738258f26c0d48fa7b515c5b82d95c22 is missing
2023-09-09 20:39:21 fsck.c(615): Repo 9596e3c1 HEAD commit is damaged, need to restore to an old version.
2023-09-09 20:39:21 fsck.c(510): Scanning available commits…
2023-09-09 20:39:21 fsck.c(516): No available commits for repo 9596e3c1, can’t be repaired.
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 9596e3c1.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 93b262fe-5f3a-4133-a94e-553694ccc80f.
2023-09-09 20:39:21 fsck.c(424): Checking file system integrity of repo My Workspace(93b262fe)…
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 93b262fe.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 93686886-93e5-4fbf-b2b1-db2ce1db5dfa.
2023-09-09 20:39:21 repo-mgr.c(295): Commit 9977449436e1e4bea093d490f48bc168c15e3fe1 is missing
2023-09-09 20:39:21 fsck.c(615): Repo 93686886 HEAD commit is damaged, need to restore to an old version.
2023-09-09 20:39:21 fsck.c(510): Scanning available commits…
2023-09-09 20:39:21 fsck.c(516): No available commits for repo 93686886, can’t be repaired.
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 93686886.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 6ee6e482-6218-47cc-9036-d5a965d15a13.
2023-09-09 20:39:21 repo-mgr.c(295): Commit b08609a44d3b7d0409258c83786436dc502ec31b is missing
2023-09-09 20:39:21 fsck.c(615): Repo 6ee6e482 HEAD commit is damaged, need to restore to an old version.
2023-09-09 20:39:21 fsck.c(510): Scanning available commits…
2023-09-09 20:39:21 fsck.c(516): No available commits for repo 6ee6e482, can’t be repaired.
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 6ee6e482.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 6ed8af32-e5ad-46f6-a313-040c3a4fee7f.
2023-09-09 20:39:21 repo-mgr.c(295): Commit 6a19c0bac4f1a4180117a53d4b359f22452ca4d2 is missing
2023-09-09 20:39:21 fsck.c(615): Repo 6ed8af32 HEAD commit is damaged, need to restore to an old version.
2023-09-09 20:39:21 fsck.c(510): Scanning available commits…
2023-09-09 20:39:21 fsck.c(516): No available commits for repo 6ed8af32, can’t be repaired.
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 6ed8af32.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 56824973-9b96-4b18-9016-f53dcff03162.
2023-09-09 20:39:21 repo-mgr.c(295): Commit edd1c1862d44b7edc3cf526f01365e869b6bb5f6 is missing
2023-09-09 20:39:21 fsck.c(615): Repo 56824973 HEAD commit is damaged, need to restore to an old version.
2023-09-09 20:39:21 fsck.c(510): Scanning available commits…
2023-09-09 20:39:21 fsck.c(516): No available commits for repo 56824973, can’t be repaired.
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 56824973.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 384d0da6-6306-4e73-bd6e-b6a92b298bb6.
2023-09-09 20:39:21 fsck.c(424): Checking file system integrity of repo plugins repo(384d0da6)…
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 384d0da6.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 25d2e8df-2faa-4060-bb7f-f7b7dd585268.
2023-09-09 20:39:21 fsck.c(424): Checking file system integrity of repo My Workspace(25d2e8df)…
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 25d2e8df.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 193e7e17-53a2-4d00-8cde-1d3cc12a3ec7.
2023-09-09 20:39:21 fsck.c(424): Checking file system integrity of repo My Library Template(193e7e17)…
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 193e7e17.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 0c3f0fab-b781-4678-8f34-f085ad5d2c4e.
2023-09-09 20:39:21 fsck.c(424): Checking file system integrity of repo My Workspace(0c3f0fab)…
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 0c3f0fab.

2023-09-09 20:39:21 fsck.c(599): Running fsck for repo 08d08f48-4af3-4539-9c4d-3a4c638b1979.
2023-09-09 20:39:21 repo-mgr.c(295): Commit b5c83dc9fb3e7901eb336fdc76b1ba09ea725cc6 is missing
2023-09-09 20:39:21 fsck.c(615): Repo 08d08f48 HEAD commit is damaged, need to restore to an old version.
2023-09-09 20:39:21 fsck.c(510): Scanning available commits…
2023-09-09 20:39:21 fsck.c(516): No available commits for repo 08d08f48, can’t be repaired.
2023-09-09 20:39:21 fsck.c(663): Fsck finished for repo 08d08f48.

seaf-fsck run done

Done.
root@68cf4893f6b8:/opt/seatable/seatable-server-latest#

你看下这个资料库对应的是存储的哪个群组的数据。把这个群组删掉就可以了。

好的谢谢好的谢谢