leonardorame
Contributor
- Joined
- Jun 30, 2018
- Messages
- 106
Hi, in a TrueNAS 12.0-U5 we have one dataset called "PoolPrincipal/Imagenes" where we store medical images. That dataset is shared through NFS.
Then, on the same server, we have an Ubuntu virtual machine with a service in charge of receiving those images from medical equipment. This VM has the "Imagenes" dataset mounted using NFS.
BTW, the NFS share's access is only allowed to the IP of the VM. Also, the VM is hosted on the same TrueNAS, so, everything is constrained to the same host.
Ok, now let's describe the problem.
When a CT sends images (between ~100 and ~1000 files of ~300kb in a short period) the "Dicom Server" running on the Ubuntu VM receive those and saves to the filesystem, pointing to the mounted NFS directory and record the file path in a database table. Then, when a physician opens a dicom viewer, the system reads the database and opens the image pointing to the filesystem.
Since this week, I had two calls claiming that some images can't be opened. The database record is there, but the file isn't, even when the Dicom Server's log shows the file was saved without errors.
Can the NFS server be returning "ok, I saved the file", when it doesn't?, the same for the underlying ZFS filesystem.
Then, on the same server, we have an Ubuntu virtual machine with a service in charge of receiving those images from medical equipment. This VM has the "Imagenes" dataset mounted using NFS.
BTW, the NFS share's access is only allowed to the IP of the VM. Also, the VM is hosted on the same TrueNAS, so, everything is constrained to the same host.
Ok, now let's describe the problem.
When a CT sends images (between ~100 and ~1000 files of ~300kb in a short period) the "Dicom Server" running on the Ubuntu VM receive those and saves to the filesystem, pointing to the mounted NFS directory and record the file path in a database table. Then, when a physician opens a dicom viewer, the system reads the database and opens the image pointing to the filesystem.
Since this week, I had two calls claiming that some images can't be opened. The database record is there, but the file isn't, even when the Dicom Server's log shows the file was saved without errors.
Can the NFS server be returning "ok, I saved the file", when it doesn't?, the same for the underlying ZFS filesystem.
