Global file system

In computer science, global file system has historically referred to a distributed virtual name space built on a set of local file systems to provide transparent access to multiple, potentially distributed, systems.[1] These global file systems had the same properties such as blocking interface, no buffering etc. but guaranteed that the same path name corresponds to the same object on all computers deploying the filesystem. Also called distributed file systems these file systems rely on redirection to distributed systems, therefore latency and scalability can affect file access depending on where the target systems reside.

For the Red Hat product, see GFS2.

History

The Andrew File System attempted to solve this for a campus environment using caching and a weak consistency model to achieve local access to remote files.

More recently, global file systems have emerged that combine cloud or any object storage, versioning and local caching to create a single, unified, globally accessible file system that does not rely on redirection to a storage device [2] but serves files from the local cache while maintaining the single file system and all meta data in the object storage.[3] As described in Google's patents, advantages of these global file systems include the ability to scale with the object storage, use snapshots stored in the object storage for versioning to replace backup, and create a centrally managed consolidated storage repository in the object storage.

gollark: What do you mean "chiplet" exactly?
gollark: In Intel laptop CPUs, CPU and GPU are on the same die. But this is generally worse than discrete graphics cards for thermal, power and memory bandwidth reasons.
gollark: It works on my phone's Firefox for Android, but *not* on another Firefox on Linux install which isn't signed into my account.
gollark: I assume they would be HTTP or HTTP/2 ones, and while I seem to be able to see the rest of those going to my server, there's just *nothing* for the websocket.
gollark: This is weird. I may be capturing wrong, or... Firefox just isn't actually sending any requests to make the websocket?

See also

References
  1. Parallel Database Systems: PRISMA Workshop. Netherlands September 24–26, 1990. edited by Pierre America (Jul 17, 1991 ISBN 3-540-54132-2), page 410
  2. https://www.google.com/patents/US8566362
  3. https://www.google.com/patents/US8661063


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.