Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Network-attached storage
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Examples == === Open-source server implementations === [[Open-source software|Open-source]] NAS-oriented distributions of [[Linux]] and [[FreeBSD]] are available. These are designed to be easy to set up on commodity PC hardware, and are typically configured using a web browser. They can run from a [[virtual machine]], [[Live CD]], [[booting|bootable]] USB flash drive ([[Live USB]]), or from one of the mounted hard drives. They run [[Samba (software)|Samba]] (an [[Server Message Block|SMB]] daemon), [[Network File System|NFS]] daemon, and [[File Transfer Protocol|FTP]] daemons which are freely available for those operating systems. === Network-attached secure disks=== '''Network-attached secure disks''' ('''NASD''') is 1997–2001 research project of [[Carnegie Mellon University]], with the goal of providing cost-effective scalable [[Computer data storage|storage]] [[Bandwidth (computing)|bandwidth]].<ref>{{cite web|url=http://www.pdl.cmu.edu/NASD/|title=NASD: Network attached secure disks}}</ref> NASD reduces the overhead on the file [[Server (computing)|server]] (file manager) by allowing storage devices to transfer data directly to [[Client (computing)|client]]s. Most of the file manager's work is offloaded to the storage disk without integrating the file system policy into the disk. Most client operations like Read/Write go directly to the disks; less frequent operations like authentication go to the file manager. Disks transfer variable-length objects instead of fixed-size blocks to clients. The File Manager provides a time-limited cachable capability for clients to access the storage objects. A file access from the client to the disks has the following sequence: # The client authenticates itself with the file manager and requests for the file access. # If the client can be granted access to the file requested, the client receives the [[Computer network|network]] location of NASD disks and their capability. # If the client is accessing the disk for the first time, it receives a time-limited key for the establishment of secure communication to the disk. # The file manager informs the corresponding disk using an independent channel. # From now on, the client directly accesses the NASD disks by giving the capability it received and further data transfers go through the network, bypassing the file manager. === List of network protocols used to serve NAS === {{div col|colwidth=27em}} * [[Andrew File System]] (AFS) * [[Apple Filing Protocol]] (AFP) * [[Server Message Block]] (SMB) * [[File Transfer Protocol]] (FTP) * [[Hypertext Transfer Protocol]] (HTTP) * [[Network File System]] (NFS) * [[rsync|{{mono|rsync}}]] * [[SSH file transfer protocol]] (SFTP) * [[Universal Plug and Play]] (UPnP) {{div col end}}
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)