Hello Beatrix,

There isn't much left to do regarding random filesystem errors; all suspicious areas have already been addressed.

Some NAS devices support Docker containers, so it's possible to install Valentina Server directly on them. While not as easy, it is much safer for data.
Or perhaps you are already using this approach for your application whenever possible?

My users want to use their databases on a NAS and not install Valentina Server. If the NAS works for any type of large file except Valentina I am 100% sure that the fault lies with Valentina.

My users want to use their databases on a NAS and not install Valentina Server. If the NAS works for any type of large file except Valentina I am 100% sure that the fault lies with Valentina.

What file system is on the NAS?

The type of NAS varies.

The newest case is a user with a WD EX2 Ultra and the OS MyCloud-OS 5.28.105. He gets input/output error all of a sudden.

The type of NAS varies.

The newest case is a user with a WD EX2 Ultra and the OS MyCloud-OS 5.28.105. He gets input/output error all of a sudden.

Okay, there is some discussion going on about this with the engineering team. I know a sizable update is coming soon, but I don't expect a fix to be in that, but in a possible hot fix after that (hopefully, that will address what is happening but there are a number of possibilities as to the cause).

Just to set aside something that comes to mind but, did you ever have this happen when a user was using an xFAT formatted drive?

There's a lot going on between a user computer and an NAS, and opening large files over a network can have complications at multiple points. I think drives (and networks) being so fast nowadays its easy to forget. This sort of thing isn't that easy to sleuth out.

I don't think that users on macOS NAS have xFAT drives. But I could send an email to my mailing list.

I know that the network is complicated and NAS are complicated, too. But I have gotten complaints from my users again and again. They don't want to have a server. They have a NAS which is perfect for the large databases which my app makes.

I don't think that users on macOS NAS have xFAT drives. But I could send an email to my mailing list.

I know that the network is complicated and NAS are complicated, too. But I have gotten complaints from my users again and again. They don't want to have a server. They have a NAS which is perfect for the large databases which my app makes.

My understanding is that macOS can work with xFat drives on a network (I don't think NTFS is an option) so its a good choice in a mixed network of macOS and Windows desktops. If xFat made a difference (no difference, same outcome vs doesn't occur on xFat at all) it could be informative in diagnosing what's causing the problem.

A network related issue like this is a step beyond the blind men figuring out what the elephant looks like. It is more like the blind men feeling the elephant and trying to figure out what type of mustache the elephant rider has.

Next user with the same problem: input/output error. By now the probability that everyone is working with a NAS that is kaput is equal to 0.

This user has an interesting variation: his lock files are not deleted when closing my app. I've asked him how the hard disk are formatted.

This user has an interesting variation: his lock files are not deleted when closing my app. I've asked him how the hard disk are formatted.

Okay, thanks. Someone is looking into this now and there's some discussion going on to try to figure out what is happening, but the mustache metaphor problem remains.

Great to hear. I'm familiar with fixing not-reproducible bugs. Sometimes poking a bug is necessary.

Got another user with the same problem. Either the problem is specific to Germans or only Germans continue to send me bug reports about this problem.

Patience is not my virtue. Any news?

Hi Beatrix,

Some improvements/fixes were made in v.14.5 in this area which is now available as a beta.

Please, try it, and if (I hope not) some issues appear again, please, register all possible info from such client - every detail may matter - NAS/ExternalDrive, its vendor, model, even cables (state, vendor), WiFi characteristics, NAS's OS ... (for NAS) as much as possible.
It is also essential to understand how many errors happen (same users or someone only), and its frequency,
This info should be structured as well.

Because, for now, we can be sure that such issues happen on NAS/External Drives only and the rest info can not be used to see any patterns.

Great! Got the new version.