I'm trying to get a clearer picture of what's happening with files that are stored on a server using ZFS and ECC when accessed from a workstation that also has ECC, but lacks a resilient file system. Specifically, I want to know if the file is cached on the workstation or if it's just temporarily held in RAM. I've seen some suggestions that the best practice is to download the file and work locally before uploading it back to the server for data integrity reasons. However, this seems to hinge on whether the workstation also employs ECC and ZFS, which many don't. Shouldn't those workstations only have read access to these files instead?
2 Answers
Downloading the files and working on them locally does make sense, especially for data integrity reasons, but it really depends on the setup of your workstation. If it doesn't support ZFS, it would be risky to work directly on files from the server. Ideally, workstations should mostly have read-only access unless they meet the necessary requirements.
I think you're worrying a bit too much about this. Whether a file gets cached or just used from RAM really depends on the application you're using to access it. Some apps might keep it solely in RAM, while others could cache a local copy. Can you share your specific use case? It seems like the technologies you’re using shouldn’t compromise data integrity too much. For situations where data integrity is absolutely critical, there are specialized system architectures for that.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures