QNAP NAS Community Forum

The most crucial thing I was using the QNAP for was TimeMachine backups. I found the perfect bug fix for this, total cost a few hundred dollars equivalent - but so well worth the money that it's not worth spending time mucking around with other unreliable kludges.

I suggest everyone else needing the TimeMachine support functionality in the QNAP server does the same.

http://tinyurl.com/2mgv4o

-ed

It seems as though QNAP have fixed some of the issues relating to AFP after the OS X Lion update caused widespread problems -- I am curious to know if this fix has also cured the TimeMachine issues, I suspect it has.

I am now a happy QNAP user again, finding that after applying their update for Lion, everything seems to be working well. I am very glad to see that they have taken this seriously and maintained support for this product, just disappointed that it took so long to address the AFP / TimeMachine issue for this piece of hardware (409 Pro)

Hi there,

Recently fixed a problem with my TS-879 (TimeMachine wouldn't backup anymore as it complained about the volume format:

see: http://forum.qnap.com/viewtopic.php?f=15&t=79107

After I fixed the problem, I sometimes see this message:
I see posts about this problem from 2010, so I think it is a problem that was solved??

I have that same problem now (2013) so what can be done to get it fixed??

Anyone??

Rgds

Robbert

Hi Robbert,

This can happen if a Mac with file activities is loosing power, hibernating, roamed out of Wi-Fi reach, or the like. This does lead to the Netatalk AFP CNID DB issue, because of the distributed CDB (operated on each AFP client, stored on the NAS) are not properly closed or cleaned-up. With the switch to the NAS-centric DBD I expect to see in later summer, this issue should be mitigated finally.

Regards,
-Kurt.

I've had this issue ever since I purchased QNAP in May of 2013. I upgraded to 3.8.3 right away, and this is happening on every AFP share every time I try to mount it. The error message is: "Something wrong with the volume's CNID DB, using temporary CNID DB instead.Check server messages for details!"

This won't go away by booting or updating. Once the CNID DB are corrupt, they remain corrupt until removed, permitting AFPD recreating.

I'm not sure what it means. Is there any way to fix this issue? Right now, I have to access shares via SMB; I can't access any share via AFP at all. Time Machine backups work fine, though.