fsck.c(413): Checking file system integrity of repo Budgets(4dc5181d). Just check if the problem is still here (without trying to repair). fsck.c(650): Fsck finished for repo 4dc5181d.īut after that I’ve tried to check if a file in the seafile-data directory isn’t readable : find. \! -readable give no output.Īn error occurred 10 min ago, and I’ve found something new.Įrror on lib : 4dc5181d-6e0c-4551-8a7e-5ef846de7f56 The seafile-data directory is stored over a NFS disk, but permission seems to be fine.įrom the root directory of seafile (on the same level as logs, conf etc…) running find. I’m running seafile-server6.2.5 on linux (debian 9) common/block-backend-fs.c(72): failed to open block fd7a4b830efaa96204de4328f8e808fa7498f43c for read: Permission denied access-file.c(266): Failed to open block 1d8ac55f-b21e-478c-8794-e2ab76db9c8d:fd7a4b830efaa96204de4328f8e808fa7498f43cĪ simple seaf-fsck.sh -r $lib_id solve the issue, but the problem come back latter, on this library or on another. fsck.c(650): Fsck finished for repo 1d8ac55f. /common/block-backend-fs.c(72): failed to open block fd7a4b830efaa96204de4328f8e808fa7498f43c for read: Permission denied fsck.c(413): Checking file system integrity of repo tek kxkm(1d8ac55f). When I run seaf-fsck I get this : fsck.c(586): Running fsck for repo 1d8ac55f-b21e-478c-8794-e2ab76db9c8d. I’m using Seafile on multiple situations, and it’s running quite well.īut since a week there is some permission denied errors that occurs randomly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |