-
That is the same issue. In @bmalkow case, the issue was caused but the file system errors leading to hanging during access to the database file.
@wojtek Could you check if there are any file system errors on your macOS? and if not follow ideas from #issue #217 (grep logs from the console)
-
Threre were some issues on the disk:
Ejecutando Primera Ayuda en “Atlantis ZPM - Datos” (disk1s1) Verificar el volumen de arranque hará que el ordenador deje de responder. Verificando sistema de archivos. No se ha podido desmontar el volumen. Usando modo en tiempo real. Ejecutando fsck_apfs -n -l -x /dev/rdisk1s1 Checking the container superblock. Checking the EFI jumpstart record. Checking the space manager. Checking the space manager free queue trees. Checking the object map. Checking volume. Checking the APFS volume superblock. The volume Atlantis ZPM - Datos was formatted by hfs_convert (748.1.46) and last modified by apfs_kext (1412.101.1). Checking the object map. Checking the snapshot metadata tree. Checking the snapshot metadata. Checking the extent ref tree. Checking the fsroot tree. warning: xf : INO_EXT_TYPE_DSTREAM : found unexpected dstream associated with non-regular file warning: xf : INO_EXT_TYPE_DSTREAM : found unexpected dstream associated with non-regular file warning: found orphan dstream id object (id 70047464, refcnt 1) warning: found orphan dstream id object (id 70049075, refcnt 1) Verifying allocated space. Performing deferred repairs. The volume /dev/rdisk1s1 appears to be OK. El código de salida de la comprobación del sistema de archivos es 0. Restaurando el estado original encontrado como montado. Operación correcta.
Not really sure if macOS fixed anything though - there are warnings, information about some deferred repairs and in the end "OK". Let's hope that this fixed the issue.
Type |
Bug
|
Priority |
Normal
|
Assignee |
Issue Votes (0)
Watchers (0)