Menu

#646 Netatalk 3.1.7 and updatedb on ubuntu

None
wont-fix
nobody
None
1
2023-04-10
2017-09-06
No

Hi!
I found an incompatability between netatalk and mlocate package.
The environment is ubuntu 14.04 server in a container with netatalk 3.1.7 and mlocate 0.26-1ubuntu1 installed. The mlocate package the default installed one. Mlocate is file indexer being used by "find" utility.

I have a setup for 5 different users to back up to my "capsule" server. On the system each user has their own virtual disk attached and mounted, which in turn is shared with netatalk. I have had multiple crashes for my hfsplus filesystems, which rendered them unusable and created uninterruptabble processes, that are trying to access the disks. Last time it happened I noticed that updatedb was run right before the crash and that updatedb process was the one left uninterruptabble this time. I looked back and noticed that this has happened right before every crash I had. I have now determined, that if updatedb is indexing any of the hfsplus filesystems, while they are being used by netatalk, then it results in the crash I have been having. The one of the 2 being run after the other has already started is the one crashing, so it is not just a problem with netatalk or mlocate or even hfsplus support on ubuntu since I have been able to work with the filesystems while backing up some Macs. Mlocates updatedb utility runs with cron.daily and if a backup is ahppening during the indexing period the system fails miserably.

TLDR: netatalk accessing a hfsplus filesystem being indexed by mlocate (updatedb process) crashes the filesystem, creates uninterruptabble processes and ruines all the backups.

Maybe this is not the place for this, but it feels netatalk related.

If this happens again, I will try to add logs.

Discussion

  •  HAT

    HAT - 2017-10-10

    This problem is unrelated for Netatalk.

     
  • Daniel Markstedt

    • status: open --> wont-fix
    • Group: -->
     

Log in to post a comment.

MongoDB Logo MongoDB