The Experts below are selected from a list of 324 Experts worldwide ranked by ideXlab platform

Ethan L Miller - One of the best experts on this subject based on the ideXlab platform.

  • measurement and analysis of large scale network file system workloads
    USENIX Annual Technical Conference, 2008
    Co-Authors: Andrew W Leung, Shankar Pasupathy, Garth R Goodson, Ethan L Miller
    Abstract:

    In this paper we present the analysis of two large-scale network file system workloads. We measured CIFS traffic for two enterprise-class file servers deployed in the NetApp data center for a three month period. One file server was used by marketing, sales, and finance departments and the other by the engineering department. Together these systems represent over 22TB of storage used by over 1500 employees, making this the first ever large-scale study of the CIFS protocol. We analyzed how our network file system workloads compared to those of previous file system trace studies and took an in-depth look at access, usage, and sharing patterns. We found that our workloads were quite different from those previously studied; for example, our analysis found increased read-write file access patterns, decreased read-write ratios, more randomfile access, and longer file lifetimes. In addition, we found a number of interesting properties regarding file sharing, file re-use, and the access patterns of file types and users, showing that modern file system workload has changed in the past 5-10 years. This change in workload characteristics has implications on the future design of network file systems, which we describe in the paper.

  • USENIX Annual Technical Conference - Measurement and analysis of large-scale network file system workloads
    2008
    Co-Authors: Andrew W Leung, Shankar Pasupathy, Garth R Goodson, Ethan L Miller
    Abstract:

    In this paper we present the analysis of two large-scale network file system workloads. We measured CIFS traffic for two enterprise-class file servers deployed in the NetApp data center for a three month period. One file server was used by marketing, sales, and finance departments and the other by the engineering department. Together these systems represent over 22TB of storage used by over 1500 employees, making this the first ever large-scale study of the CIFS protocol. We analyzed how our network file system workloads compared to those of previous file system trace studies and took an in-depth look at access, usage, and sharing patterns. We found that our workloads were quite different from those previously studied; for example, our analysis found increased read-write file access patterns, decreased read-write ratios, more randomfile access, and longer file lifetimes. In addition, we found a number of interesting properties regarding file sharing, file re-use, and the access patterns of file types and users, showing that modern file system workload has changed in the past 5-10 years. This change in workload characteristics has implications on the future design of network file systems, which we describe in the paper.

David Noveck - One of the best experts on this subject based on the ideXlab platform.

  • Transport-generic network file system (NFS) Upper Layer Bindings To RPC- Over-RDMA
    2017
    Co-Authors: David Noveck
    Abstract:

    This document specifies Upper Layer Bindings to allow use of RPC- over-RDMA by protocols related to the network file system (NFS). Such bindings are required when using RPC-over-RDMA, in order to enable use of Direct Data Placement and for a number of other reasons. These bindings are structured to be applicable to all known version of the RPC-over-RDMA transport, including optional extensions. All versions of NFS are addressed.

  • network file system nfs version 4 external data representation standard xdr description
    RFC, 2015
    Co-Authors: Thomas Haynes, David Noveck
    Abstract:

    The network file system (NFS) version 4 protocol is a distributed file system protocol that owes its heritage to NFS protocol version 2 (RFC 1094) and version 3 (RFC 1813). Unlike earlier versions, the NFS version 4 protocol supports traditional file access while integrating support for file locking and the MOUNT protocol. In addition, support for strong security (and its negotiation), COMPOUND operations, client caching, and internationalization has been added. Of course, attention has been applied to making NFS version 4 operate well in an Internet environment. RFC 7530 formally obsoletes RFC 3530. This document, together with RFC 7530, replaces RFC 3530 as the definition of the NFS version 4 protocol.

  • network file system nfs version 4 minor version 1 protocol
    RFC, 2010
    Co-Authors: Spencer Shepler, David Noveck, Mike Eisler
    Abstract:

    This document describes the network file system (NFS) version 4 minor version 1, including features retained from the base protocol (NFS version 4 minor version 0, which is specified in RFC 3530) and protocol extensions made subsequently. Major extensions introduced in NFS version 4 minor version 1 include Sessions, Directory Delegations, and parallel NFS (pNFS). NFS version 4 minor version 1 has no dependencies on NFS version 4 minor version 0, and it is considered a separate protocol. Thus, this document neither updates nor obsoletes RFC 3530. NFS minor version 1 is deemed superior to NFS minor version 0 with no loss of functionality, and its use is preferred over version 0. Both NFS minor versions 0 and 1 can be used simultaneously on the same network, between the same client and server. [STANDARDS-TRACK]

  • network file system nfs version 4 minor version 1 external data representation standard xdr description
    RFC, 2010
    Co-Authors: Spencer Shepler, David Noveck, Mike Eisler
    Abstract:

    This Internet-Draft provides the XDR description for NFSv4 minor version one. This Internet-Draft is an active work item of the NFSv4 working group. Active and resolved issues may be found in the issue tracker at: http://www.nfsv4-editor.org/cgi-bin/roundup/nfsv4. New issues related to this document should be raised with the NFSv4 Working Group nfsv4@ietf.org.

  • network file system nfs version 4 protocol
    RFC, 2003
    Co-Authors: Spencer Shepler, Brent Callaghan, David Robinson, Robert Thurlow, C Beame, Mike Eisler, David Noveck
    Abstract:

    The network file system (NFS) version 4 is a distributed filesystem protocol which owes heritage to NFS protocol version 2, RFC 1094, and version 3, RFC 1813. Unlike earlier versions, the NFS version 4 protocol supports traditional file access while integrating support for file locking and the mount protocol. In addition, support for strong security (and its negotiation), compound operations, client caching, and internationalization have been added. Of course, attention has been applied to making NFS version 4 operate well in an Internet environment.

Mike Eisler - One of the best experts on this subject based on the ideXlab platform.

  • network file system nfs version 4 minor version 1 external data representation standard xdr description
    RFC, 2010
    Co-Authors: Spencer Shepler, David Noveck, Mike Eisler
    Abstract:

    This Internet-Draft provides the XDR description for NFSv4 minor version one. This Internet-Draft is an active work item of the NFSv4 working group. Active and resolved issues may be found in the issue tracker at: http://www.nfsv4-editor.org/cgi-bin/roundup/nfsv4. New issues related to this document should be raised with the NFSv4 Working Group nfsv4@ietf.org.

  • network file system nfs version 4 minor version 1 protocol
    RFC, 2010
    Co-Authors: Spencer Shepler, David Noveck, Mike Eisler
    Abstract:

    This document describes the network file system (NFS) version 4 minor version 1, including features retained from the base protocol (NFS version 4 minor version 0, which is specified in RFC 3530) and protocol extensions made subsequently. Major extensions introduced in NFS version 4 minor version 1 include Sessions, Directory Delegations, and parallel NFS (pNFS). NFS version 4 minor version 1 has no dependencies on NFS version 4 minor version 0, and it is considered a separate protocol. Thus, this document neither updates nor obsoletes RFC 3530. NFS minor version 1 is deemed superior to NFS minor version 0 with no loss of functionality, and its use is preferred over version 0. Both NFS minor versions 0 and 1 can be used simultaneously on the same network, between the same client and server. [STANDARDS-TRACK]

  • network file system nfs version 4 protocol
    RFC, 2003
    Co-Authors: Spencer Shepler, Brent Callaghan, David Robinson, Robert Thurlow, C Beame, Mike Eisler, David Noveck
    Abstract:

    The network file system (NFS) version 4 is a distributed filesystem protocol which owes heritage to NFS protocol version 2, RFC 1094, and version 3, RFC 1813. Unlike earlier versions, the NFS version 4 protocol supports traditional file access while integrating support for file locking and the mount protocol. In addition, support for strong security (and its negotiation), compound operations, client caching, and internationalization have been added. Of course, attention has been applied to making NFS version 4 operate well in an Internet environment.

John Ousterhout - One of the best experts on this subject based on the ideXlab platform.

  • the zebra striped network file system
    ACM Transactions on Computer Systems, 1995
    Co-Authors: John H. Hartman, John Ousterhout
    Abstract:

    Zebra is a network file system that increases throughput by striping the file data across multiple servers. Rather than striping each file separately, Zebra forms all the new data from each client into a single stream, which it then stripes using an approach similar to a log-structured file system. This provides high performance for writes of small files as well as for reads and writes of large files. Zebra also writes parity information in each stripe in the style of RAID disk arrays; this increases storage costs slightly, but allows the system to continue operation while a single storage server is unavailable. A prototype implementation of Zebra, built in the Sprite operating system, provides 4–5 times the throughput of the standard Sprite file system or NFS for large files and a 15–300% improvement for writing small files.

  • SOSP - The Zebra striped network file system
    Proceedings of the fourteenth ACM symposium on Operating systems principles - SOSP '93, 1994
    Co-Authors: John H. Hartman, John Ousterhout
    Abstract:

    Zebra is a network file system that increases throughput by striping file data across multiple servers. Rather than striping each file separately, Zebra forms all the new data from each client into a single stream, which it then stripes using an approach similar to a log-structured file system. This provides high performance for writes of small files as well as for reads and writes of large files. Zebra also writes parity information in each stripe in the style of RAID disk arrays; this increases storage costs slightly but allows the system to continue operation even while a single storage server is unavailable. A prototype implementation of Zebra, built in the Sprite operating system, provides 4--5 times the throughput of the standard Sprite file system or NFS for large files and a 20%-3x improvement for writing small files.

  • Zebra: A Striped network file system
    ACM SIGOPS Operating Systems Review, 1993
    Co-Authors: John H. Hartman, John Ousterhout
    Abstract:

    This paper presents the design of Zebra, a striped network file system. Zebra applies ideas from log-structured file system (LFS) and RAID research to network file systems, resulting in a network file system that has scalable performance, uses its servers efficiently even when its applications are using small files, and provides high availability. Zebra stripes file data across multiple servers, so that the file transfer rate is not limited by the performance of a single server. High availability is achieved by maintaining parity information for the file system. If a server fails its contents can be reconstructed using the contents of the remaining servers and the parity information. Zebra differs from existing striped file systems in the way it stripes file data: Zebra does not stripe on a per-file basis; instead it stripes the stream of bytes written by each client. Client write to the servers in units called stripe fragments, which are analogous to segments in an LFS. Stripe fragments contain file blocks that were written recently, without advantages over per-file striping, including increased server efficiency, efficient parity computation, and elimination of parity update.

Andrew W Leung - One of the best experts on this subject based on the ideXlab platform.

  • measurement and analysis of large scale network file system workloads
    USENIX Annual Technical Conference, 2008
    Co-Authors: Andrew W Leung, Shankar Pasupathy, Garth R Goodson, Ethan L Miller
    Abstract:

    In this paper we present the analysis of two large-scale network file system workloads. We measured CIFS traffic for two enterprise-class file servers deployed in the NetApp data center for a three month period. One file server was used by marketing, sales, and finance departments and the other by the engineering department. Together these systems represent over 22TB of storage used by over 1500 employees, making this the first ever large-scale study of the CIFS protocol. We analyzed how our network file system workloads compared to those of previous file system trace studies and took an in-depth look at access, usage, and sharing patterns. We found that our workloads were quite different from those previously studied; for example, our analysis found increased read-write file access patterns, decreased read-write ratios, more randomfile access, and longer file lifetimes. In addition, we found a number of interesting properties regarding file sharing, file re-use, and the access patterns of file types and users, showing that modern file system workload has changed in the past 5-10 years. This change in workload characteristics has implications on the future design of network file systems, which we describe in the paper.

  • USENIX Annual Technical Conference - Measurement and analysis of large-scale network file system workloads
    2008
    Co-Authors: Andrew W Leung, Shankar Pasupathy, Garth R Goodson, Ethan L Miller
    Abstract:

    In this paper we present the analysis of two large-scale network file system workloads. We measured CIFS traffic for two enterprise-class file servers deployed in the NetApp data center for a three month period. One file server was used by marketing, sales, and finance departments and the other by the engineering department. Together these systems represent over 22TB of storage used by over 1500 employees, making this the first ever large-scale study of the CIFS protocol. We analyzed how our network file system workloads compared to those of previous file system trace studies and took an in-depth look at access, usage, and sharing patterns. We found that our workloads were quite different from those previously studied; for example, our analysis found increased read-write file access patterns, decreased read-write ratios, more randomfile access, and longer file lifetimes. In addition, we found a number of interesting properties regarding file sharing, file re-use, and the access patterns of file types and users, showing that modern file system workload has changed in the past 5-10 years. This change in workload characteristics has implications on the future design of network file systems, which we describe in the paper.