[go: up one dir, main page]

WO2000014632A1 - Serveur de fichiers virtuels - Google Patents

Serveur de fichiers virtuels Download PDF

Info

Publication number
WO2000014632A1
WO2000014632A1 PCT/US1999/019243 US9919243W WO0014632A1 WO 2000014632 A1 WO2000014632 A1 WO 2000014632A1 US 9919243 W US9919243 W US 9919243W WO 0014632 A1 WO0014632 A1 WO 0014632A1
Authority
WO
WIPO (PCT)
Prior art keywords
file
request
content data
virtual
formats
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US1999/019243
Other languages
English (en)
Inventor
Roger A. Sayle
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
METAPHORICS LLC
Original Assignee
METAPHORICS LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by METAPHORICS LLC filed Critical METAPHORICS LLC
Priority to AU57829/99A priority Critical patent/AU5782999A/en
Priority to JP2000569312A priority patent/JP5019669B2/ja
Priority to EP99945151A priority patent/EP1112537A4/fr
Publication of WO2000014632A1 publication Critical patent/WO2000014632A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/188—Virtual file systems
    • G06F16/192—Implementing virtual folder structures
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99931—Database or file accessing
    • Y10S707/99933—Query processing, i.e. searching
    • Y10S707/99934—Query formulation, input preparation, or translation

Definitions

  • the present invention relates generally to systems and methods for managing databases, and more particularly, systems and methods for providing file systems that are further capable of receiving and replying to file system requests involving data stored in remote machines through conventional protocol means.
  • HTTP HyperText Transfer Protocol
  • NFS Network File System
  • NFS Network File System
  • a file server is a machine that exports a set of files.
  • Clients are machines that access such files.
  • Clients and servers communicate via "remote procedure calls" which operate as synchronous requests.
  • the kernel sends a request to the server and the client blocks until it receives a reply.
  • the server waits for incoming client requests, processes them and sends replies back to the clients.
  • NFS server exports one or more file systems. Each exported file system may be either an entire partition or a subtree thereof.
  • the server can specify, typically through entries in the "/etc/exports" file, which clients may access each exported file system and whether the access permitted is read-only or read-write. Client machines then mount such a file system, or a subtree of it, onto any directory in their existing file hierarchy, just as they would mount a local file system.
  • the client may mount the directory as read-only, even if the server has exported it as read-write.
  • NFS supports two types of mounts -- "hard” and "soft". This influences the client behavior if the server does not respond to a request.
  • the client keeps retrying until a reply is received.
  • the client gives up after a while and returns an error. Once the "mount" succeeds, the client may access files in the remote file system using the same operations that apply to local files.
  • NFS should not be restricted to UNIX. Any operating system should be able to implement an NFS server or client. The protocol should not be dependent on any particular hardware. There should be simple recovery mechanisms from server or client crashes. Applications should be able to access remote files transparently, without using special pathnames or libraries and without recompiling. UNIX file system semantics must be maintained for UNIX clients. NFS performance must be comparable to that of a local disk. The implementation must be transport independent.
  • the single most important characteristic of the NFS protocol is that the server is stateless and does not need to maintain any information about its clients to operate correctly. Each request is completely independent of others and contains all the information required to process it. The server need not maintain any record of past requests from clients, except optionally for caching or statistics gathering purposes.
  • the NFS protocol does not provide requests to open or close a file, since that would constitute state information that the server must remember.
  • the READ and WRITE requests pass the starting offset as a parameter, unlike "read” and "write” operations on local files, which obtain the offset from the file description.
  • a stateless protocol makes crash recovery simple. No recovery is required when a client crashes, it simply remounts the file system when it reboots and the server neither knows nor cares. When a server crashes, the client discovers that requests are timing out and simply retransmits them. It continues to resend requests until the server finally answers after it reboots. The client has no way to determine if the server crashed and rebooted or was simply slow. Stateful protocols, however, require crash-recovery mechanisms. The server must detect client crashes and discard any state maintained for that client. When a server reboots, it must notify the clients so that they can rebuild their state on the server.
  • NFS Network File System Protocol Stack consists of several components or layers that define how file system operations are converted into packets over a network protocol .
  • the network transport layer Conventionally under NFS, this consists of the UDP (Unreliable Datagram Protocol) internet transport; however, modern implementations also support the TCP (Transmission Control Protocol) internet protocol .
  • the next layer of the NFS protocol stack is SUN Microsystems' XDR (Extended Data Representation) that provides a machine-independent method of encoding data to send over the network.
  • SUN Microsystems' RPC Remote Procedure Call
  • the next layer above this consists of three components; the NFS, MOUNT and PORTMAP protocols. These peer protocols define an API level interface to contact remote NFS, MOUNT and PORTMAP daemons (nfsd, mount and portmapper) via RPC respectively. Finally, the highest layer is the logical protocol that dictates the order of requests to the PORTMAP daemon (to obtain the ports of the MOUNT and NFS daemons) , the MOUNT daemon (to obtain a root file handle of an exported file system) and finally, the NFS daemon (using file handles from the MOUNT daemon or previous NFS replies) .
  • the lowest level of the NFS protocol stack is the Internet protocol used as a transport.
  • UDP protocol This is a connectionless transport mechanism that sends arbitrarily sized data packets between sockets over a network.
  • the RPC layer of the protocol stack implements a reliable datagram service by keeping track of unanswered requests and retransmitting them periodically until a response is received.
  • UDP was originally used as its implementation offered performance benefits of the reliable connection- oriented TCP; however, with ever improving implementations this difference no longer exists.
  • UDP is still the default for most NFS implementations, many support TCP/IP as an alternative and recent WebNFS specifications require support for TCP/IP as a transport.
  • XDR Extended Data Representation
  • the XDR standard defines a machine-independent representation for data transmission over a network. It defines several basic data types (such as int , char and string) and rules for constructing complex data types (such as fixed and variable length arrays, structures and unions) . This standard handles issues such as byte ordering, word sizes and string formats that may otherwise be incompatible between heterogeneous computers and operating systems at either end of a network connection.
  • the SUN RPC protocol specifies the format of communications between clients and servers.
  • the client sends RPC requests to the server, which processes them and returns the results in an RPC reply.
  • the protocol addresses issues such as message format, transmission and authentication, which do not depend upon a specific application of service.
  • SUN RPC uses synchronous requests. When a client makes an RPC request, it blocks until it receives a response. This makes the behavior of RPC similar to that of a local procedure call.
  • RPC specifies the format of request and reply packets using XDR encoding.
  • An RPC request packet contains a transmission ID, the fact that the packet is a request, the program identifier and program version for which the packet is intended, the procedure within the program to be executed, client authentication information
  • An RPC reply packet contains the transmission ID of the request to which it is replying, the fact that the packet is a reply, whether the operation was executed, server authentication information (if any) and procedure specific results.
  • the unique transmission ID allows the client to identify the request for which the response has arrived and allows the server to detect duplicate requests (caused by retransmissions from the client) .
  • the program identifier and program version allows a single application (or socket) to service multiple program requests and simultaneously support multiple protocol versions.
  • RPC uses five authentication mechanisms to identify the caller to the server: AUTH_NULL (no authentication) ,
  • AUTH TNIX UNIX-style credentials, including client machine name, a user ID and one or more group IDs
  • AUTH_DES Data Encryption Standard authentication
  • AUTH_KERB Kerberos authentication
  • AUTH_SHORT is that once a client has been authenticated using AUTH_UNIX credentials, the server generates a short token or cookie that can be used by that client in future
  • This AUTH_SHORT can be deciphered very quickly to identify known clients, providing faster authentication .
  • Layer 4A Portmap (rpcbind) Protocol
  • the first server process (daemon) of the NFS protocol stack is the RPC portmap daemon (also known as rpcbind) .
  • This server process provides directory services mapping program identification and program version numbers to BSD-style port numbers for creating socket connections.
  • RPC requests are sent to the server to locate a particular service (such as NFS version 3) on the remote machine, or to register (and unregister) a service on the local machine.
  • This port mapping service means that only the port of the portmap daemon (usually port 111) need be known in advance by a client.
  • the client then interrogates this server to determine whether a mount daemon and NFS daemon are running, and if so their port numbers.
  • a server typically contacts the portmap daemon when it starts up, to inform it of the port number on which it is awaiting requests, and also as the server is shutting down to unregister itself.
  • Layer 4B Mount Protocol
  • the next server process (daemon) of the NFS protocol stack is the mount daemon.
  • the MOUNT protocol is separate from, but related to, the NFS protocol. It provides operating system specific services, such as looking up server path names, validating user identity, and checking access permissions.
  • the mount protocol is kept separate from the NFS protocol to make it easy to implement new access checking and validation methods without changing the NFS protocol .
  • Mount also requires directory path names, where as the NFS protocol is independent of operating system dependent directory syntax. NFS clients must use the MOUNT protocol to get the first file handle, which allows them entry into the remote file system.
  • the mount daemon may also be queried to determine the list of currently exported file systems.
  • NFS Protocol The main and final server process (daemon) of the NFS protocol stack is the NFS daemon itself. This stateless server is responsible for handling all file operation requests, such as read, write and delete.
  • the first public version of the protocol was NFS version 2, which was released in SunOS 2.0 in 1985, and is supported by all NFS implementations.
  • NFS version 3 was announced and is currently supported by most implementations. (Interestingly, at the time of writing, the current Linux NFS server and kernel implementations only support NFS version 2) .
  • NFS version 3 provides several minor changes that increase performance and enable support for file systems larger than 4Gbytes.
  • NFSv2 All of the procedures in the NFSv2 protocol are assumed to be synchronous, when control returns to the client only after the operation is completed and any data associated with the request is committed to stable storage. In NFSv3 this requirement is relaxed for WRITE requests allowing the client and server to negotiate the use of a COMMIT request, allowing writes to complete much faster. Additionally, NFSv3 returns file attributes after most operations and when reading directories, eliminating the need for many GETATTR calls required when using NFSv2.
  • NFS Network File System Protocol Specification The NFSv2 protocol specifies 15 procedures (operations or methods) exported by an NFS server.
  • NFSv3 protocol specifies 21 procedures exported by an NFS server. Most of these procedures have identical semantics as those in version 2, however because file attributes are now returned after most operations and some fields are now larger, the exact types of the arguments and results are slightly different . /* NFS version 3 protocol API */
  • READDIR3res READDIR(READDIR3args), ⁇ proo 16 */
  • the SMB protocol is currently being revised as the Common Internet File System (CIFS) , which is likely to become a significant standard protocol over the next few years.
  • CIFS Common Internet File System
  • Microsoft's Server Message Block is the file sharing protocol used by MS-Net, LAN Manager and Windows Networking. This protocol is the native file-sharing protocol of Microsoft Windows 9x, Windows NT and OS/2 operating systems. Instead of the SUN XDR and RPC layers used in layers 2 and 3 of the NFS protocol stack, SMB used NetBIOS as its middle layer. NetBIOS started as a high-level programming language interface to IBM PC- Network broadband LANs, but has evolved as a "wire- protocol" over several underlying transport mechanisms including Token-ring, TCP/IP, IPX/SPX. The currently preferred transport is TCP/IP, and UDP/IP (as described in Internet RFCs 1001 and 1002) making layer 1 identical between NFS and SMB.
  • SMB Server Message Block
  • SMB broadcasts requests to NetBIOS name server (such as Microsoft WINS) to locate remote file servers.
  • NetBIOS name server such as Microsoft WINS
  • the name server replies the IP address of the server supporting the named file system.
  • An SMB client then contacts the file services on this host using the NetBIOS session manager and creates a session connection much like NFS over TCP/IP after contacting a MOUNT daemon. Packets are then sent and received using TCP/IP identically to NFS in all but the format of the messages sent between machines .
  • a virtual file server may provide a virtual SMB file system to Windows-based PCs on a network. (13) Biological Sequence Database Management
  • bioinformatics sites maintain a number of database searching software, including programs such as Blast, FASTA and GCG.
  • programs such as Blast, FASTA and GCG.
  • This diversity results in most bioinformatics sites maintaining major databases in multiple file formats such as the original flat files, FASTA format, GCG/PIR format, Blast compressed format and indices, and SRS indices.
  • Each additional representation typically requires tens of gigabytes additional file storage for its databases.
  • the next issue is that of database sub- and super-setting.
  • the present invention is specifically designed to address and alleviate the above-identified deficiencies in the art.
  • the present invention is directed to a virtual file server that, by using standard protocol means, provides an efficient method of managing databases that require far less disk space (i.e., memory) , and that further provides for a novel method of delivering computational data.
  • the present invention is particularly well suited to address the aforementioned problems of biological sequence database management.
  • the virtual file server essentially comprises a process by which the contents of a file from a remote file system can be generated and returned in response to a file system request.
  • the virtual file server is designed to simulate a remote file system, providing "virtual" files and directories to a machine making a request on a local area network via the network interface.
  • the virtual network file system operates to receive and reply to file system requests from the network as though such virtual network file systems were retrieving and storing files on a physical storage media (i.e., hard disk) .
  • the virtual network file server In operation, once the virtual network file server receives a file read request, for example, the virtual network file server generates the contents of a specified "virtual" file, the contents of which may either be generated algorithmically from its file name and environment, or by transforming a stored physical file by encryption, decompression, and the like. To client applications, the virtual file server appears as a normal directory hierarchy containing the appropriate files in the appropriate formats .
  • the virtual network file server does not involve the client operating system, but uses its native mechanisms to access a remote machine.
  • NFS or SMB the virtual file server does not require that specialized network software be written for the clients and will thus allow existing software to work with the virtual file server without modification.
  • NFS client software is distributed with UNIX and is available for virtually every operating system including Microsoft Windows, Apple Macintosh and VAX/VMS .
  • Microsoft SMB clients are included in Microsoft Windows NT, Windows 95 and Windows 98.
  • the virtual file server is able to maintain the subject databases internally in a single format. Upon file requests, the virtual file server is able to perform sub- and supersetting operations and then the appropriate reformatting. Because only one format of the database is being maintained, caching on the server is far more effective. Many sequence database format conversions may be implemented very efficiently (for example, using finite state machines) resulting in negligible performance loss. Indeed, the server is free to internally represent the database in a very efficient compressed format, for example, removing duplicate sequences, Huffman or bit-wise encoding of residues, and representing sequences that are subsequences of another as a reference to the location within the parent. Another potential application is that individual sequence database entries can be exported as individual sequence files.
  • the virtual file server architecture is also applicable to storage management of structural databases and integration of external computational chemistry applications.
  • One major application is in the storage and maintenance of the Brookhaven Protein Databank, PDB (and also the Rutgers University nucleic acid structure database NDB) .
  • PDB Brookhaven Protein Databank
  • NDB Rutgers University nucleic acid structure database
  • the virtual file server provides a convenient mechanism for providing computational chemistry services.
  • the virtual file server could perform file format conversion by exporting Sybyl Mol2, XPLOR PDB and other file formats.
  • the server could also provide DSSP or Stride secondary structure assignments in each PDB file, reconstruct backbone and/or sidechain co-ordinates from alpha carbon only files, generate crystallographic symmetries, select representative NMR models or perform property calculations .
  • FIG. 1 is a block diagram of the communication format for accessing a logical file or directory, the latter being located on a local physical storage media or on a remote machine;
  • FIG. 2 is a flow chart of a continual loop program by which the virtual network file server processes and returns file system requests for remote file systems;
  • FIG. 3 illustrates the flow chart of FIG. 2 wherein such program further provides for an isolation of the virtual file system of the present invention from the virtual network file server itself;
  • FIG. 4 is a diagram of specified requests converted by the server of the present invention to independent files or directories that are forwarded by the network file server to process remote file system requests;
  • FIG. 5 depicts a flow chart for the READ function of a virtual file system "plug-in" for generating and returning the contents of a virtual file to the virtual network file server.
  • the present invention is directed to a virtual network file server that, in response to a request to a computer's operating system involving a remote file system, generates the contents of a specified file and returns the same to the computer from which the request was made via the network interface between the computer from which the request was made and the server machine receiving such request.
  • the server machine receiving such request via its operating system, passes such request onto the virtual network file server, the latter running as a user process.
  • a user application or process 10 running on a computer makes a request to the operating system 20 on that machine to access a logical file system or directory 30.
  • the logical filename (and directory) specified in the request is interpreted by the operating system' s file services as belonging to a remote file system, rather than being stored on a local storage device 40.
  • the operating system 20 uses its conventional remote file system mapping to determine the location on the network of the file server for requested file.
  • the operating system 20 then generates a TCP/IP request to the network file server via the network file server's network interface 50.
  • the network file server may be on the same machine, where the network interface simply copies the request packet to the server process, or on a remote machine, where the network interface 50 transmits the request packet over a local area network 60.
  • the server machine receives the packet via its network interface 70, and the operating system 80 passes the request on to a virtual network file server 90 running as a user process .
  • the virtual network file server 90 emulates a file system, providing "virtual" files and directories to the machines on the local network. On receiving a file read request, it generates the contents of a specified "virtual" file.
  • the file contents may either be generated algorithmically from its filename and environment or by transforming a stored physical file by encryption, decompression or non-trivial translation. The distinction is made between trivial and non-trivial translation.
  • a number of existing file servers may be configured to translate line termination characters before exporting files to a remote machine.
  • the mechanisms described here apply to translation of data into different formats, such as images between image file formats or bioinformatics databases between common representations.
  • Such translation capabilities may further advantageously be utilized to rapidly convert text files existing in one particular word processing format or program to another type of word processing format.
  • Such translation properties can enable rapid conversion from one encrypted file to another, as well as data stored in one particular type of compressed format to another.
  • the contents of the virtual file once the contents of the virtual file have been generated, the same can be sent as a reply packet back across the network to the requesting user process.
  • the server process 100 once started 110 on a machine, initializes the server 120 and enters a continual loop 130 waiting for file system requests 140 directed to remote machines or systems, decoding the requests 150, determining the response 160, namely, generating the requested data or performing the requested action, encoding the reply 170 and then transmitting 180 (i.e., returning) the results to requesting process, as depicted in FIG. 2.
  • the "decode request" 150 and "encode reply” 170 steps perform the mapping of the native file system requests into and from, respectively, the internal data structures and routines used by the virtual network file server. This allows the virtual file server to support multiple remote file system protocols including UNIX NFS, Microsoft LanManager, AppleShare, etc.
  • the current implementation makes use of multiple threads (or processes) allowing multiple file system requests to be implemented concurrently, and for the virtual server to perform processing to keep the contents of virtual file systems up to date without receiving a file system request.
  • One variant 190 of the previous flow chart, as depicted in FIG. 3, is the implementation where the contents and behavior of the virtual file system is isolated from the virtual network file server itself.
  • the virtual network file server of the present invention allows multiple uses (or implementations) to be determined at run-time. This is achieved using dynamic shared object technology, often referred to as plug-ins. These plug- ins typically take the form of shared libraries on UNIX machines, DLLs under Microsoft Windows, and CodeFragments on the Apple Macintosh.
  • the server When the server first starts up 200, it locates and dynamically links in virtual file system "plug-ins" 210.
  • the plug- ins represent and encode the user-defined behavior of the virtual file system.
  • these plug- ins form independent files or directories on the remote file system, as conceptually illustrated in FIG. 4.
  • the network file server Each time a request is received, the network file server initializes 220 and determines which of the loaded plug- ins should handle the request and dispatches, decodes and waits for the request appropriately as per steps 230, 240. To the extent such request is not directed to the file system 260, the server then generates a reply 270 and converts the resulting data into the native format of the requesting system and transmits 280 it back to the request-ing machine.
  • the virtual network file server is also advantageously able to handle such file system "housekeeping" requests 260 by selectively choosing 290 and calling 300 a plug-in and thereafter encoding a reply 320 therefrom, thus freeing other plug- ins of the task of implementing trivial or common functionality.
  • each virtual file system plug-in hides the complexities of the remote file system encoding and decoding from the plug-in, and also simplifies its operation.
  • the behavior of each virtual file system plug-in is then to handle a simplified set of remote file system requests, shown conceptually in FIG. 4.
  • Such requests include reading data from a file (READ) 340, writing data to a file (WRITE) 360, changing the security protection and permission on a file (CHMOD) 380, creating a new file (CREATE) 400, and determining the contents of a directory or folder (READDIR) 420.
  • the virtual network file server maintains a table of the routines within that plug-in for each remote file system request. Once the virtual network file server has decoded a request and determined which of the plug- ins need respond to it, it looks up the required function within the appropriate plug- in' s "function dispatch" table and then calls that function.
  • FIG. 5 represents the simplified flow chart for the READ function 340, to decode the file name 460, generate virtual file contents 480, and return the contents of a virtual file 500.
  • the plug-in' s read function is called with a file identifier, a location within the file and the amount of the data to be read 460.
  • the plug-in is then free to choose what the contents of that file should be 480, potentially based upon the start of the server, the user and/or machine requesting the data or other factors. For example, the plug- in could state that the contents of the requested file "date.txt" is always the current time and date, i.e. "Wed Aug 12 11:28:43 MDT 1998".
  • the virtual file server prototype currently implements both versions 2 and 3 of the NFS protocol and versions 1 and 3 of the MOUNT protocol over the UDP/IP transport protocol.
  • This implementation described below, is the presently preferred embodiment of the virtual file server, but does not in any way restrict the scope of the invention to the NFS protocol or the UNIX operating system.
  • the example "embodiment” is referred to as a virtual NFS server or "vnfsd” in the following sections, which describe the UNIX version of
  • the virtual NFS server (vnfsd) may be started from the UNIX command line, by simply typing "vnfsd".
  • the server does not require super-user privileges to run, and hence need not be started by "root”.
  • the virtual NFS daemon should not be killed, but only interrupted.
  • the daemon catches the interrupt signal and closes down, gracefully closing and flushing any appropriate files and unregistering itself from the RPC portmap daemon.
  • mount -t nfs -o port 21069
  • soft server /vnfs /vnfs
  • an entry may be added to the "/etc/fstab" file on the client machine specifying the server, remote directory and mount options for the local nfs.
  • the /vnfs directory may be unmounted from the client file system using the UNIX command: umount /vnfs All processes should have closed any open files on the virtual file system and no process should have any subdirectory of the mount point as a current working directory. If the file system is currently in use, the umount command will fail. If client machines do not successfully unmount the filesystem before the server is terminated, they run the risk of hanging waiting for a response when they next try to access the virtual file system.
  • the first task performed by the vnfsd daemon is to contact the portmap daemon on the local machine to determine whether it is currently running conventional NFS and mount daemons. By default, if the portmap daemon indicates that neither of these is not currently running, it registers itself with the portmap daemon as the real nfs and mount daemons on the local machine. As the server terminates, it contacts the portmap daemon once again to determine if it is still the registered NFS and MOUNT daemon on the system. If so, it unregisters itself so that other programs are aware that NFS and MOUNT services are no longer provided by the server machine.
  • This interaction with the RPC portmapper may be turned off using the "-noreg" command line option when the server is first started. This should slightly improve the startup and shutdown performance when it is known in advance that conventional NFS is running on the server machine .
  • the first request from client may be an NFS request with a
  • the virtual NFS daemon supports this operational mode by treating any unrecognized file handle as the root file handle of the system.
  • the UNIX make(l) utility is a program development tool that simplifies the task of compiling and linking large applications.
  • the "make" program stores the list of commands necessary to create an application and the dependencies (or ordering information) in a Makefile. This universally accepted mechanism for specifying how files are generated by application can be used to integrate arbitrary external programs into the virtual file server.
  • Each directory of the Makefile file system contains a Makefile that informs the virtual NFS daemon which files are exported and which programs to execute to generate their contents.
  • a file system need not delete or remove a file from the server at the time a client issues a "rm” or “del” command. Instead, it could temporarily move the file to a "trash” or “recycle” area until it is automatically deleted after a suitable period elapses. This allows common user mistakes to be corrected by recovering the files from the "trash” . Such trash areas may be stored compressed and automatically garbage collected when the disk's free space drops below a certain threshold. (d) Revision Control
  • File Systems are often used to store multiple revisions or versions of a particular file. Much like the generation number is appended to file names in the VMS file system. If the file system knows that a set of files have similar contents or are modifications of an existing file, the virtual network file server is able to maintain the differences (or edits) between files, rather than their entire contents. This avoids the large disk space requirements for maintaining previous versions of regularly modified documents.
  • NFSWeb could allow WWW pages to be accessed via files on the local file system.
  • access to a file such as "/http/www. microsoft.com/index.htm” would result in the appropriate HTTP request and the returned contents exported as the file contents.
  • the virtual file server described above essentially allows developers to implement virtual file systems as shared libraries, which are linked by the vnfsd daemon at run-time.
  • the vnfsd server takes care of all the low- level TCP/IP-based sockets, connection management and Sun Microsystems' XDR, RPC, MOUNT and NFS wire protocols.
  • This file system library need only implement a much simpler functional API of approximately twelve subroutine entry points. Many of these subroutines are optional depending upon the type of file system. This allows single-file read-only file systems to be implemented using a minimum of two functions, and multiple-file readonly file systems using a minimum of nine.
  • file systems there are two types of file systems. These are single-file file systems, that describe only a single file, and multiple- file file systems that describe an arbitrary number of files and subdirectories. The principal distinction between the two is that the root inode, the zero-inode, is a regular file for the former and the directory for the latter.
  • the single-file file system is a simplification of the virtual NFS API that allows a plug- in to be defined by only two subroutines, but must use pluginfs dynamic linking and cannot be linked statically to the vnfsd server.
  • the virtual file system developer simply writes implementations of these required subroutines that describe the contents of the file system. If all subroutines are implemented, the file system object may either be statically linked into the vnfsd directly or linked at run-time as dynamic shared objects by the provided "pluginfs" file system. If not all of the functions are implemented, the pluginfs must be used and will provide default implementations for the missing entry points. In a production environment, dynamically linked pluginfs solution is preferred but statically linking is useful for development and debugging.
  • the pluginfs requires that shared libraries have a name of the form "*fs.so" and be placed in the vnfsd plug-ins directory.
  • the virtual file system API makes use of the concepts of an inode and a directory cookie .
  • An inode is a 32bit signed long, that is used to distinguish every file and directory on the file system. Only the lower 28bits are significant allowing any single file system to export a maximum of 268 million individually named files or subdirectories. Multiple-file file systems must map inode 0 as the root directory of the file system and single-file file systems must map inode 0 as the virtual file. Inodes need not be uniquely named within a file system. This allows several files (or directories) to have identical contents.
  • a directory cookie is a 32bit signed integer that conceptually represents a logical position in a list of directory entries .
  • a directory cookie need only be unique to its own directory.
  • the zero-cookie has special significance representing either the position before the first directory entry or the position after the last entry.
  • the zero-cookie is only ever passed to or returned from the "mxINodeDirNext " function.
  • the pluginfs and UNIX operating system place additional constraints upon directory cookies.
  • cookie 1 must have local name " . " and represent the current directory
  • cookie 2 must have local name " .. " the parent of the current directory [or the root directory when the current directory is the root directory] .
  • cookies need not be sequential and may be returned by "mxINodeDirNext" in any order until the zero-cookie.
  • the virtual NFS API contains a single initialization and a single clean-up function. Both of the functions are optional in both types of virtual file system. mxINodelnitialize char* mxINodelnitialize ( void ) ;
  • the mxINodelnitialize function is used to allow the plug-in to initialize any required data structures to their initial state.
  • This optional routine has no arguments and returns a null-terminated C string.
  • This string is used to name the file system. This name is ignored when linking statically, but is used as the directory name that contains the file system when using the plug-in filesystem. Conventionally, these names are the prefix of the system library name prior to the "fs.so" suffix. For example, the demonstration file system in "demofs.so" returns the string "demo".
  • This function is only ever called once, before any of the other functions, when the vnfsd server is first started- up.
  • the mxINodeCleanUp function is used to allow the plug-in to deallocate any allocated memory or system resources before the vnfsd server terminates. This function takes no arguments and returns no results. This function is only ever called once, and none of the other functions are ever called again afterwards. (10) General Functions
  • the virtual NFS API contains two functions that are independent of the file system types of their inode arguments. Hence these functions have inode arguments that may be either files or directories . mxINodelsValid int mxINodelsValid ( long inode );
  • This function is used to check the validity of an inode value. It takes a signal long as an argument denoting the inode, and returns a non-zero integer if the inode is valid within the file system and a zero otherwise. This return value uses the conventional encoding of Boolean values in the C programming language. The zero-inode must always be valid. It should be safe to assume that no other function will be called with an inode that is flagged as invalid by this function. This function must be implemented for multiple- file systems. For single-file file systems, the default behavior is that the zero-inode is the only valid inode.
  • mxINodeType int mxINodeType ( long inode ) ;
  • This function is used to determine the "type" of a file system inode. It takes a signed long as an argument denoting the inode, and returns one of three integer values defined as macros in the "filesys.h” include file. These values are MX INODETYPE_FILE for inodes that are regular files, MX_INODE_DIRECTORY for inodes that are directories and MX_INODE_NOTFOUND should the inode be invalid.
  • INODE_DIRECTORY If implemented for single-file file systems, the default (and required) implementation is to return MX_INODE_FILE for the zero-inode.
  • the virtual NFS API contains two functions for accessing regular files within a virtual file system. Hence these functions have inode arguments that must be files. mxINodeFileLen unsigned long mxINodeFileLen ( long inode ) ;
  • the mxINodeFileLen function is used to determine the length of a file. This function has a single long argument representing the file inode and returns an unsigned long denoting the length of the file in bytes. This restriction currently limits each virtual file to a maximum size of 4Gbytes . Inodes that are determined to be invalid or directories should return a value of zero. It must be possible to read all of the specified bits of the file with the mxINodeFileData function. If mxINodeFileLen returns a value larger than can be read by mxINodeFileData, most clients will loop continually attempting to read past the end of the virtual file. This function must be implemented for both types of file systems.
  • mxINodeFileData int mxINodeFileData long inode, unsigned char *ptr, unsigned long off, int len ) ;
  • the mxINodeFileData function is used to retrieve the contents of a regular file. This function takes four arguments; a long representing the file inode, a pointer to buffer of unsigned characters to receive the data, an unsigned long representing the offset within the file from which to read an integer representing the number of bytes to read. This function returns an integer, which is the number of bytes actually placed in the buffer. Should the inode be invalid or a directory, the function should return zero and leave the buffer unmodified.
  • the function should return zero and leave the buffer unmodified.
  • the function should never fill the buffer with more than the requested number of bytes.
  • the function should never place more characters in the buffer than are remaining in the file, i.e., if the return value is greater than zero, this value plus the file offset is less than the file length.
  • the virtual NFS API contains six functions for accessing directories (or folders) within a virtual file system. Hence these functions have inode arguments that must be directories. Four of these functions also have directory cookie arguments. These functions are used for traversing the contents of a directory. mxINodeDirEntry long mxINodeDirEntry ( long inode, unsigned char *ptr, int len ) ;
  • the mxINodeDirEntry function is used to locate a directory entry by name.
  • the function takes three arguments; a long representing the directory inode, a pointer to a string of characters holding the filename and integer holding the length of the filename argument.
  • the function returns a long, which denotes either the inode of the located directory entry (file or subdirectory) or the value MX_INODE_INVALID.
  • the value MX_INODE_INVALID should be returned if the inode argument is not a valid directory inode or if the filename is not found.
  • the filename parameter is not (may not) be a null terminated string and the implementation should never inspect more than the specified number of bytes. All implementations must recognize the directory entries " . " and " .. " returning the argument inode or the inode of its parent respectively. Implementations are allowed to recognize "hidden" filenames that do not correspond to directory cookies .
  • the mxINodeDirSubdirs function issued to efficiently determine the number of subdirectories in a directory.
  • the function takes a single long argument holding the directory inode to be inspected and returns an integer containing the number of subdirectory entries. If the argument is not a valid directory inode, or the implementation does not wish to report the number of subdirectories, it should return the value zero.
  • the mxINodeDirNext function is used to traverse the contents of a directory. This function takes two arguments, a long holding the directory inode and an integer holding the current directory cookie, and returns an integer representing the next cookie in sequence. If the inode argument is not a valid directory inode the function should return the value zero.
  • the vnfsd server starts the sequence by calling this function with the zero-cookie. This function is called repeatedly with the returned cookie until the function returns a zero-cookie indicating the end of the sequence. This function should only ever be called with either a zero-cookie, or a cookie returned by a previous call with the same directory inode.
  • a non-zero cookie can never be guaranteed to be the result of the previous call to this function.
  • This function should return the value zero, if presented with an unrecognized cookie value for the specified directory.
  • An implementation is free to choose its own internal representation of cookies .
  • the sequence need not be continuous or monotonic, but the same value must not be visited twice in a sequence.
  • the cookie sequence should also include the value 1 (representing the current directory ".") and the value 2 (representing the parent directory "..”), but these values may appear at any position in the sequence.
  • the mxINodeDirName function is used to find out the name of a directory entry found during a directory traversal. This function takes three arguments, a long holding the directory inode, an integer holding a directory cookie, and a pointer to a buffer for returning the file name. The function returns an integer containing the length of the filename (the number of bytes placed in the specified buffer) . If the inode argument is not a valid directory, or the cookie is not a recognized cookie for the given directory, the function should return the value zero and leave the buffer unmodified. No more than 256 bytes should ever be written to the specified buffer, which limits the maximum size of a filename. The string is allowed to be null- terminated but the return value should not include the trailing zero byte.
  • This routine should never be called with a zero-cookie.
  • the cookie 1 For a valid directory inode, the cookie 1 should result in the first byte of the buffer being set to ⁇ . ' and a return value of one, and the cookie 2 should result in the first two bytes of the buffer being set to " .. " and the return value 2.
  • This function is required for multiple-file file systems.
  • the mxINodeDirNameLen function is used to determine the length of a filename of a directory entry found during a directory traversal .
  • This function is similar to mxINodeDirName but is used to determine the filename's length before retrieving it.
  • This function takes two arguments, a long holding the directory inode and an integer holding a directory cookie and returns an integer containing the length of the filename. If the inode argument is not a valid directory, or the cookie is not a valid cookie of the given directory, the function should return the value zero. This function should return the same value as mxINodeDirName for the same inode and cookie arguments. This routine should never be called with a zero-cookie.
  • the cookie value 1 should return the value 1 and the cookie value 2 should return the value 2.
  • This function is required for multiple-file file systems. mxINodeDirlNode long mxINodeDirlNode ( long inode, int cookie );
  • the mxINodeDirlnode function is used to find out the inode of a directory entry found during a directory traversal. This function takes two arguments, a long holding the directory inode and an integer holding a directory cookie and returns an integer containing the length of the filename. If the inode argument is not a valid directory, or the cookie is not a valid cookie for the given directory, the function should return the value MX INODE INVALID. For a valid directory inode and the cookie value 1, this function should return the directory inode argument. For a zero-inode and the cookie value 2, this function should return zero. For a valid non-zero directory inode and the cookie value 2, this function should return the inode of this directory's parent. This function is required for multiple-file file systems.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

Serveur de fichiers virtuels servant à générer des données de contenu en réponse aux demandes d'un système d'exploitation informatique comprenant un système de fichiers à distance. Selon un mode de réalisation préféré, ce serveur de fichiers virtuels reçoit la demande (figure 2) éventuellement par l'intermédiaire d'un protocole d'une variété de protocoles normalisés. Les données de contenu sont générées ou extraites et traduites dans le format spécifié par la demande. Il n'est pas nécessaire de conserver le contenu du fichier virtuel sous forme de fichier physique mémorisé dans le format demandé. Les contenus demandés de ce fichier virtuel sont codés en fonction du protocole par lequel la demande a été reçue initialement. Une fois qu'il est codé, le contenu demandé du fichier virtuel est transmis en réponse à la demande.
PCT/US1999/019243 1998-09-08 1999-08-20 Serveur de fichiers virtuels Ceased WO2000014632A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
AU57829/99A AU5782999A (en) 1998-09-08 1999-08-20 Virtual file server
JP2000569312A JP5019669B2 (ja) 1998-09-08 1999-08-20 仮想ネットワーク・ファイル・サーバ
EP99945151A EP1112537A4 (fr) 1998-09-08 1999-08-20 Serveur de fichiers virtuels

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US9942598P 1998-09-08 1998-09-08
US60/099,425 1998-09-08
US09/323,333 1999-06-01
US09/323,333 US6356863B1 (en) 1998-09-08 1999-06-01 Virtual network file server

Publications (1)

Publication Number Publication Date
WO2000014632A1 true WO2000014632A1 (fr) 2000-03-16

Family

ID=26796087

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1999/019243 Ceased WO2000014632A1 (fr) 1998-09-08 1999-08-20 Serveur de fichiers virtuels

Country Status (5)

Country Link
US (1) US6356863B1 (fr)
EP (1) EP1112537A4 (fr)
JP (1) JP5019669B2 (fr)
AU (1) AU5782999A (fr)
WO (1) WO2000014632A1 (fr)

Cited By (32)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2365556A (en) * 2000-08-04 2002-02-20 Hewlett Packard Co Gateway device for remote file server services
SG91903A1 (en) * 2000-03-30 2002-10-15 Ibm File system locking
JP2002318719A (ja) * 2001-04-24 2002-10-31 Hitachi Ltd 高信頼計算機システム
WO2002017140A3 (fr) * 2000-08-18 2003-12-31 Apple Computer Procede et systeme permettant d'acceder de maniere transparente a des fichiers stockes a distance
US6922708B1 (en) 1999-02-18 2005-07-26 Oracle International Corporation File system that supports transactions
US7058648B1 (en) 2000-12-01 2006-06-06 Oracle International Corporation Hierarchy-based secured document repository
JP2006244493A (ja) * 2005-02-28 2006-09-14 Microsoft Corp データベース内で表現されるファイル・システム
KR100728517B1 (ko) * 2006-12-28 2007-06-15 메크로비젼 코오포레이션 동적으로 연결 가능한 실행 가능 이미지들의 진정성을증명하는 시스템 및 방법
US7280995B1 (en) 1999-08-05 2007-10-09 Oracle International Corporation On-the-fly format conversion
EP1898322A1 (fr) * 2006-08-25 2008-03-12 QNX Software Systems GmbH & Co. KG Système de fichier multimédia ayant une représentation unifiée de contenu de dispositifs multimédia divers
WO2008048388A3 (fr) * 2006-10-13 2008-06-19 Spansion Llc Contrôleur virtuel de carte mémoire
US7418435B1 (en) 1999-08-05 2008-08-26 Oracle International Corporation Multi-model access to data
WO2008102159A1 (fr) * 2007-02-23 2008-08-28 Quantel Limited Système de serveur de fichiers
US7627547B2 (en) 2004-11-29 2009-12-01 Oracle International Corporation Processing path-based database operations
US7827177B2 (en) 2006-10-16 2010-11-02 Oracle International Corporation Managing compound XML documents in a repository
US7873683B2 (en) 2005-07-01 2011-01-18 Qnx Software Systems Gmbh & Co. Kg File system having transaction record coalescing
US7908276B2 (en) 2006-08-25 2011-03-15 Qnx Software Systems Gmbh & Co. Kg Filesystem having a filename cache
US7921076B2 (en) 2004-12-15 2011-04-05 Oracle International Corporation Performing an action in response to a file system event
US7958112B2 (en) * 2008-08-08 2011-06-07 Oracle International Corporation Interleaving query transformations for XML indexes
US7970803B2 (en) 2005-07-01 2011-06-28 Qnx Software Systems Gmbh & Co. Kg Optimized startup verification of file system integrity
US8131766B2 (en) 2004-12-15 2012-03-06 Oracle International Corporation Comprehensive framework to integrate business logic into a repository
WO2012136977A2 (fr) 2011-04-07 2012-10-11 Quantel Limited Perfectionnements relatifs à des systèmes de fichier
US8356053B2 (en) 2005-10-20 2013-01-15 Oracle International Corporation Managing relationships between resources stored within a repository
US8694510B2 (en) 2003-09-04 2014-04-08 Oracle International Corporation Indexing XML documents efficiently
US8949455B2 (en) 2005-11-21 2015-02-03 Oracle International Corporation Path-caching mechanism to improve performance of path-related operations in a repository
US8959125B2 (en) 2005-07-01 2015-02-17 226008 Ontario Inc. File system having inverted hierarchical structure
US9183321B2 (en) 2006-10-16 2015-11-10 Oracle International Corporation Managing compound XML documents in a repository
EP3309697A1 (fr) * 2016-10-11 2018-04-18 Petagene Ltd. Système et procédé de de mise en mémoire et d'accès à des données
US10019448B2 (en) 2011-08-05 2018-07-10 Quantel Limited Methods and systems for providing file data for media files
WO2018215634A1 (fr) * 2017-05-24 2018-11-29 Petagene Ltd. Système et procédé de traitement de données
US10321167B1 (en) 2016-01-21 2019-06-11 GrayMeta, Inc. Method and system for determining media file identifiers and likelihood of media file relationships
US10719492B1 (en) 2016-12-07 2020-07-21 GrayMeta, Inc. Automatic reconciliation and consolidation of disparate repositories

Families Citing this family (151)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000013379A1 (fr) * 1998-08-31 2000-03-09 Fujitsu Limited Appareil d'affectation de service
US6763370B1 (en) * 1998-11-16 2004-07-13 Softricity, Inc. Method and apparatus for content protection in a secure content delivery system
US7017188B1 (en) * 1998-11-16 2006-03-21 Softricity, Inc. Method and apparatus for secure content delivery over broadband access networks
US7370071B2 (en) 2000-03-17 2008-05-06 Microsoft Corporation Method for serving third party software applications from servers to client computers
US7730169B1 (en) 1999-04-12 2010-06-01 Softricity, Inc. Business method and system for serving third party software applications
US6938096B1 (en) * 1999-04-12 2005-08-30 Softricity, Inc. Method and system for remote networking using port proxying by detecting if the designated port on a client computer is blocked, then encapsulating the communications in a different format and redirecting to an open port
US7200632B1 (en) 1999-04-12 2007-04-03 Softricity, Inc. Method and system for serving software applications to client computers
US8099758B2 (en) 1999-05-12 2012-01-17 Microsoft Corporation Policy based composite file system and method
US7035880B1 (en) * 1999-07-14 2006-04-25 Commvault Systems, Inc. Modular backup and retrieval system used in conjunction with a storage area network
US7395282B1 (en) 1999-07-15 2008-07-01 Commvault Systems, Inc. Hierarchical backup and retrieval system
US7389311B1 (en) * 1999-07-15 2008-06-17 Commvault Systems, Inc. Modular backup and retrieval system
US6629127B1 (en) 1999-07-26 2003-09-30 Microsoft Corporation Methods and systems for processing HTTP requests
US6584497B1 (en) * 1999-07-28 2003-06-24 International Business Machines Corporation Method, system, and program for returning a file requested through a network connection
US6785822B1 (en) * 1999-09-16 2004-08-31 International Business Machines Corporation System and method for role based dynamic configuration of user profiles
US6895591B1 (en) * 1999-10-18 2005-05-17 Unisys Corporation Virtual file system and method
US6718372B1 (en) * 2000-01-07 2004-04-06 Emc Corporation Methods and apparatus for providing access by a first computing system to data stored in a shared storage device managed by a second computing system
US7155481B2 (en) 2000-01-31 2006-12-26 Commvault Systems, Inc. Email attachment management in a computer system
US7003641B2 (en) 2000-01-31 2006-02-21 Commvault Systems, Inc. Logical view with granular access to exchange data managed by a modular data and storage management system
US6658436B2 (en) * 2000-01-31 2003-12-02 Commvault Systems, Inc. Logical view and access to data managed by a modular data and storage management system
US6735623B1 (en) * 2000-02-09 2004-05-11 Mitch Prust Method and system for accessing a remote storage area
US6714968B1 (en) 2000-02-09 2004-03-30 Mitch Prust Method and system for seamless access to a remote storage server utilizing multiple access interfaces executing on the remote server
US6570593B1 (en) * 2000-02-24 2003-05-27 International Business Machines Corporation Management graphical user interface for a network file system
US20040105122A1 (en) * 2000-03-20 2004-06-03 Schaeffer Richard J. Printer control and document management system
US6654794B1 (en) * 2000-03-30 2003-11-25 International Business Machines Corporation Method, data processing system and program product that provide an internet-compatible network file system driver
GB2365554B (en) * 2000-05-31 2004-09-01 Ibm Virtual machine support for multiple aplications
GB2362969B (en) * 2000-05-31 2004-09-22 Ibm Message transformation selection tool and method
US7076534B1 (en) * 2000-06-30 2006-07-11 Microsoft Corporation Server-side scripting that enables creation of customized documents for clients
US20040236798A1 (en) * 2001-09-11 2004-11-25 Sudhir Srinivasan Migration of control in a distributed segmented file system
US7406484B1 (en) 2000-09-12 2008-07-29 Tbrix, Inc. Storage allocation in a distributed segmented file system
US7836017B1 (en) 2000-09-12 2010-11-16 Hewlett-Packard Development Company, L.P. File replication in a distributed segmented file system
US8935307B1 (en) 2000-09-12 2015-01-13 Hewlett-Packard Development Company, L.P. Independent data access in a segmented file system
US6782389B1 (en) * 2000-09-12 2004-08-24 Ibrix, Inc. Distributing files across multiple, permissibly heterogeneous, storage devices
US20060288080A1 (en) * 2000-09-12 2006-12-21 Ibrix, Inc. Balanced computer architecture
US6795824B1 (en) * 2000-10-31 2004-09-21 Radiant Data Corporation Independent storage architecture
US6611836B2 (en) * 2000-12-26 2003-08-26 Simdesk Technologies, Inc. Server-side recycle bin system
US7171494B2 (en) * 2001-01-31 2007-01-30 Hewlett-Packard Development Company, L.P. Extending a standard-based remote file access protocol and maintaining compatibility with a standard protocol stack
US6877081B2 (en) * 2001-02-13 2005-04-05 International Business Machines Corporation System and method for managing memory compression transparent to an operating system
US7653710B2 (en) 2002-06-25 2010-01-26 Qst Holdings, Llc. Hardware task manager
US20020174247A1 (en) * 2001-04-02 2002-11-21 Bo Shen System and method for dynamic routing to service providers
US6714953B2 (en) * 2001-06-21 2004-03-30 International Business Machines Corporation System and method for managing file export information
US20030018657A1 (en) * 2001-07-18 2003-01-23 Imation Corp. Backup of data on a network
WO2003012578A2 (fr) * 2001-08-01 2003-02-13 Actona Technologies Ltd. Reseau de partage de fichier virtuel
US7743109B2 (en) * 2001-08-01 2010-06-22 Cisco Technology, Inc. Reducing round trips across a wide area network for resource locking by extended locking and delayed unlocking
JP2003131924A (ja) * 2001-10-19 2003-05-09 Fujitsu Ltd リモートアクセスプログラム、リモートアクセス要求処理プログラム、およびクライアントコンピュータ
US20030145230A1 (en) * 2002-01-31 2003-07-31 Huimin Chiu System for exchanging data utilizing remote direct memory access
US7398503B2 (en) * 2002-01-31 2008-07-08 Cadence Design Systems, Inc Method and apparatus for pre-tabulating sub-networks
US6968345B1 (en) * 2002-02-27 2005-11-22 Network Appliance, Inc. Technique to enable support for symbolic link access by windows clients
US7464125B1 (en) * 2002-04-15 2008-12-09 Ibrix Inc. Checking the validity of blocks and backup duplicates of blocks during block reads
US7124171B1 (en) * 2002-05-23 2006-10-17 Emc Corporation In a networked computing cluster storage system and plurality of servers sharing files, in the event of server unavailability, transferring a floating IP network address from first server to second server to access area of data
AU2003240558A1 (en) * 2002-06-06 2003-12-22 Vizx Labs, Llc Biological results evaluation method
US7249174B2 (en) * 2002-06-12 2007-07-24 Bladelogic, Inc. Method and system for executing and undoing distributed server change operations
US20040019640A1 (en) * 2002-07-25 2004-01-29 Bartram Linda Ruth System and method for distributing shared storage for collaboration across multiple devices
US7224185B2 (en) * 2002-08-05 2007-05-29 John Campbell System of finite state machines
US7519910B2 (en) * 2002-10-10 2009-04-14 International Business Machines Corporation Method for transferring files from one machine to another using adjacent desktop displays in a virtual network
US7353538B2 (en) * 2002-11-08 2008-04-01 Federal Network Systems Llc Server resource management, analysis, and intrusion negation
US7376732B2 (en) * 2002-11-08 2008-05-20 Federal Network Systems, Llc Systems and methods for preventing intrusion at a web host
US7254696B2 (en) * 2002-12-12 2007-08-07 Alacritech, Inc. Functional-level instruction-set computer architecture for processing application-layer content-service requests such as file-access requests
JP4567293B2 (ja) * 2003-01-21 2010-10-20 株式会社日立製作所 ファイルサーバ
JP2004280283A (ja) * 2003-03-13 2004-10-07 Hitachi Ltd 分散ファイルシステム、分散ファイルシステムサーバ及び分散ファイルシステムへのアクセス方法
JP4320195B2 (ja) * 2003-03-19 2009-08-26 株式会社日立製作所 ファイルストレージサービスシステム、ファイル管理装置、ファイル管理方法、ｉｄ指定型ｎａｓサーバ、および、ファイル読出方法
US7712034B2 (en) 2003-03-24 2010-05-04 Microsoft Corporation System and method for shell browser
US7421438B2 (en) * 2004-04-29 2008-09-02 Microsoft Corporation Metadata editing control
US7823077B2 (en) * 2003-03-24 2010-10-26 Microsoft Corporation System and method for user modification of metadata in a shell browser
US7769794B2 (en) 2003-03-24 2010-08-03 Microsoft Corporation User interface for a file system shell
US7627552B2 (en) 2003-03-27 2009-12-01 Microsoft Corporation System and method for filtering and organizing items based on common elements
US7240292B2 (en) 2003-04-17 2007-07-03 Microsoft Corporation Virtual address bar user interface control
US7925682B2 (en) 2003-03-27 2011-04-12 Microsoft Corporation System and method utilizing virtual folders
US7650575B2 (en) * 2003-03-27 2010-01-19 Microsoft Corporation Rich drag drop user interface
US7526483B2 (en) * 2003-03-27 2009-04-28 Microsoft Corporation System and method for virtual folder sharing including utilization of static and dynamic lists
US7454569B2 (en) 2003-06-25 2008-11-18 Commvault Systems, Inc. Hierarchical system and method for performing storage operations in a computer network
JP4349871B2 (ja) * 2003-09-09 2009-10-21 株式会社日立製作所 ファイル共有装置及びファイル共有装置間のデータ移行方法
US20050086192A1 (en) * 2003-10-16 2005-04-21 Hitach, Ltd. Method and apparatus for improving the integration between a search engine and one or more file servers
US8024335B2 (en) 2004-05-03 2011-09-20 Microsoft Corporation System and method for dynamically generating a selectable search extension
US7546324B2 (en) 2003-11-13 2009-06-09 Commvault Systems, Inc. Systems and methods for performing storage operations using network attached storage
US20050131960A1 (en) * 2003-12-15 2005-06-16 Reed Benjamin C. Method and system of accessing at least one target file in a computer system with an operating system with file locking implemented at file-open time
US7380246B2 (en) * 2003-12-15 2008-05-27 Lenovo (Singapore) Pte. Ltd. Method and system of accessing at least one target file in a computer system with an operating system with file locking implemented with byte-range locking
US7698361B2 (en) * 2003-12-31 2010-04-13 Microsoft Corporation Lightweight input/output protocol
US7383463B2 (en) * 2004-02-04 2008-06-03 Emc Corporation Internet protocol based disaster recovery of a server
JP4575689B2 (ja) * 2004-03-18 2010-11-04 株式会社日立製作所 記憶システム及びコンピュータシステム
JP4448719B2 (ja) * 2004-03-19 2010-04-14 株式会社日立製作所 ストレージシステム
US7464405B2 (en) * 2004-03-25 2008-12-09 International Business Machines Corporation Method for preventing loading and execution of rogue operating systems in a logical partitioned data processing system
US7657846B2 (en) 2004-04-23 2010-02-02 Microsoft Corporation System and method for displaying stack icons
US7694236B2 (en) 2004-04-23 2010-04-06 Microsoft Corporation Stack icons representing multiple objects
US8707209B2 (en) * 2004-04-29 2014-04-22 Microsoft Corporation Save preview representation of files being created
US7707618B1 (en) * 2004-05-28 2010-04-27 Netapp, Inc. System and method for implementing access controls using file protocol rule sets
US20060004890A1 (en) * 2004-06-10 2006-01-05 International Business Machines Corporation Methods and systems for providing directory services for file systems
JP4500118B2 (ja) * 2004-07-06 2010-07-14 株式会社日立製作所 ストレージ装置
WO2006061251A1 (fr) * 2004-12-11 2006-06-15 Smapper Technologies Gmbh Procede et dispositif pour le traitement de donnees et programme informatique
US20060129745A1 (en) * 2004-12-11 2006-06-15 Gunther Thiel Process and appliance for data processing and computer program product
CN100405365C (zh) * 2004-12-21 2008-07-23 鸿富锦精密工业（深圳）有限公司 在文件目录下寻找文件的方法
US7568220B2 (en) * 2005-04-19 2009-07-28 Cisco Technology, Inc. Connecting VPN users in a public network
US7614016B2 (en) 2005-04-21 2009-11-03 Microsoft Corporation Multiple roots in navigation pane
US7849165B2 (en) 2005-04-21 2010-12-07 Fiducci Thomas E Data backup, storage, transfer, and retrieval system, method and computer program product
US8126990B2 (en) 2005-04-21 2012-02-28 Fiducci Thomas E Data backup and transfer system, method and computer program product
US8195646B2 (en) 2005-04-22 2012-06-05 Microsoft Corporation Systems, methods, and user interfaces for storing, searching, navigating, and retrieving electronic information
US8732220B2 (en) * 2005-06-15 2014-05-20 International Business Machines Corporation Virtualized file system
US7809777B2 (en) * 2005-07-01 2010-10-05 Qnx Software Systems Gmbh & Co. Kg File system having deferred verification of data integrity
US7665028B2 (en) 2005-07-13 2010-02-16 Microsoft Corporation Rich drag drop user interface
US20070027929A1 (en) * 2005-08-01 2007-02-01 Whelan Gary J System, method, and/or computer program product for a file system interface
US7805602B1 (en) 2005-11-10 2010-09-28 Cisco Technology, Inc. Prioritized call admission control for internet key exchange
US7845008B2 (en) * 2005-12-07 2010-11-30 Lenovo (Singapore) Pte. Ltd. Virus scanner for journaling file system
US8996586B2 (en) * 2006-02-16 2015-03-31 Callplex, Inc. Virtual storage of portable media files
US10303783B2 (en) * 2006-02-16 2019-05-28 Callplex, Inc. Distributed virtual storage of portable media files
US20070214233A1 (en) * 2006-03-07 2007-09-13 Daryl Cromer System and method for implementing a hypervisor for server emulation
US20070255677A1 (en) * 2006-04-28 2007-11-01 Sun Microsystems, Inc. Method and apparatus for browsing search results via a virtual file system
US7925681B2 (en) * 2006-04-28 2011-04-12 Microsoft Corporation Bypass of the namespace hierarchy to open files
JP5121280B2 (ja) * 2006-05-31 2013-01-16 株式会社リコー 情報処理装置、プロセス制御方法、及びプロセス制御プログラム
US20080022392A1 (en) * 2006-07-05 2008-01-24 Cisco Technology, Inc. Resolution of attribute overlap on authentication, authorization, and accounting servers
US8990270B2 (en) * 2006-08-03 2015-03-24 Hewlett-Packard Development Company, L. P. Protocol virtualization for a network file system
US20080059510A1 (en) * 2006-08-31 2008-03-06 Daniel Cardamore Multimedia system framework having layer consolidating access to multiple media devices
US20080147747A1 (en) * 2006-12-14 2008-06-19 Dan Cardamore Media system having synchronization with preemptive prioritization of synchronization order
US8768898B1 (en) * 2007-04-26 2014-07-01 Netapp, Inc. Performing direct data manipulation on a storage device
US8600953B1 (en) 2007-06-08 2013-12-03 Symantec Corporation Verification of metadata integrity for inode-based backups
US8209365B2 (en) * 2007-07-23 2012-06-26 Hewlett-Packard Development Company, L.P. Technique for virtualizing storage using stateless servers
US7933976B2 (en) * 2007-10-25 2011-04-26 International Business Machines Corporation Checkpoint and restart of NFS version 2/version 3 clients with network state preservation inside a workload partition (WPAR)
US9135270B2 (en) * 2007-12-26 2015-09-15 Oracle International Corporation Server-centric versioning virtual file system
US8954443B1 (en) * 2007-12-27 2015-02-10 Emc Corporation Multi-protocol data object scanning by a storage virtualization system
US20110060859A1 (en) * 2008-04-21 2011-03-10 Rishabhkumar Shukla Host-to-host software-based virtual system
US8285759B2 (en) * 2008-04-22 2012-10-09 Oracle International Corporation Techniques to support disparate file systems
US8819011B2 (en) * 2008-07-16 2014-08-26 Cleversafe, Inc. Command line interpreter for accessing a data object stored in a distributed storage network
US8332593B2 (en) * 2008-12-24 2012-12-11 Nuon, Inc. Memory space management and mapping for memory area network
CN101853254B (zh) * 2009-03-31 2013-08-14 国际商业机器公司 挂载文件或目录到本地或远程主机的方法和装置
US9239840B1 (en) 2009-04-24 2016-01-19 Swish Data Corporation Backup media conversion via intelligent virtual appliance adapter
US9087066B2 (en) * 2009-04-24 2015-07-21 Swish Data Corporation Virtual disk from network shares and file servers
JP5635760B2 (ja) 2009-10-16 2014-12-03 キヤノン株式会社 情報処理システム、情報処理方法、およびコンピュータプログラム
EP2526494B1 (fr) 2010-01-21 2020-01-15 SVIRAL, Inc. Procédé et appareil pour un système universel multicoeur permettant de mettre en oeuvre des calculs reposant sur des flux
WO2011133144A1 (fr) 2010-04-20 2011-10-27 Hewlett-Packard Development Company, L.P. Dispositif d'augmentation de luminescence auto-ajustable pour luminescence augmentée en surface
US9183560B2 (en) 2010-05-28 2015-11-10 Daniel H. Abelow Reality alternate
US9279767B2 (en) 2010-10-20 2016-03-08 Hewlett-Packard Development Company, L.P. Chemical-analysis device integrated with metallic-nanofinger device for chemical sensing
WO2012054024A1 (fr) 2010-10-20 2012-04-26 Hewlett-Packard Development Company, L.P. Dispositif à nanodoigts métalliques pour détection chimique
US8341114B2 (en) * 2010-11-12 2012-12-25 Blackboard Inc. System for updating information stored on a remote device
US9021198B1 (en) 2011-01-20 2015-04-28 Commvault Systems, Inc. System and method for sharing SAN storage
US9922046B2 (en) 2011-04-26 2018-03-20 Zettaset, Inc. Scalable distributed metadata file-system using key-value stores
US20120284317A1 (en) * 2011-04-26 2012-11-08 Dalton Michael W Scalable Distributed Metadata File System using Key-Value Stores
US8756509B2 (en) * 2011-07-27 2014-06-17 International Business Machines Corporation Visually representing and managing access control of resources
US8984617B1 (en) 2011-08-04 2015-03-17 Wyse Technology L.L.C. Client proxy operating in conjunction with server proxy
US9734160B1 (en) * 2012-01-11 2017-08-15 Amazon Technologies, Inc. Virtual file system for hosted network sites
US9800455B1 (en) 2012-02-08 2017-10-24 Amazon Technologies, Inc. Log monitoring system
CN103577210B (zh) * 2012-08-06 2017-11-28 广州三星通信技术研究有限公司 移动终端之间挂载的系统和方法
US9921884B1 (en) * 2012-11-01 2018-03-20 Amazon Technologies, Inc. Local and remote access to virtual machine image filesystems
US9130904B2 (en) * 2013-05-08 2015-09-08 Texas Instruments Incorporated Externally and internally accessing local NAS data through NSFV3 and 4 interfaces
US9641614B2 (en) 2013-05-29 2017-05-02 Microsoft Technology Licensing, Llc Distributed storage defense in a cluster
US10404520B2 (en) * 2013-05-29 2019-09-03 Microsoft Technology Licensing, Llc Efficient programmatic memory access over network file access protocols
JP6326909B2 (ja) 2014-03-28 2018-05-23 富士通株式会社 データアクセスシステム及びデータアクセス方法
US9591489B2 (en) 2015-07-09 2017-03-07 International Business Machines Corporation Controlling application access to applications and resources via graphical representation and manipulation
US10838920B2 (en) * 2017-05-05 2020-11-17 Esoptra NV Plug-in function platform and methods
US10735514B2 (en) * 2017-08-29 2020-08-04 Western Digital Technologies, Inc. Remote application configuration on network-attached storage
US10579277B1 (en) * 2017-10-27 2020-03-03 EMC IP Holding Company LLC Non-disruptive insertion of virtualized storage appliance
US10552081B1 (en) * 2018-10-02 2020-02-04 International Business Machines Corporation Managing recall delays within hierarchical storage
US10922375B2 (en) * 2019-02-04 2021-02-16 Citrix Systems, Inc. File portability across SaaS applications
US20210365416A1 (en) * 2020-05-25 2021-11-25 Hewlett Packard Enterprise Development Lp Mount parameter in file systems

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5163131A (en) * 1989-09-08 1992-11-10 Auspex Systems, Inc. Parallel i/o network file server architecture
US5454098A (en) * 1992-09-28 1995-09-26 Conner Peripherals, Inc. Method of emulating access to a sequential access data storage device while actually using a random access storage device
US5463772A (en) * 1993-04-23 1995-10-31 Hewlett-Packard Company Transparent peripheral file systems with on-board compression, decompression, and space management
US5636371A (en) * 1995-06-07 1997-06-03 Bull Hn Information Systems Inc. Virtual network mechanism to access well known port application programs running on a single host system

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4887204A (en) 1987-02-13 1989-12-12 International Business Machines Corporation System and method for accessing remote files in a distributed networking environment
JPS63231545A (ja) * 1987-03-20 1988-09-27 Toshiba Corp フアイル転送システム
US5109515A (en) 1987-09-28 1992-04-28 At&T Bell Laboratories User and application program transparent resource sharing multiple computer interface architecture with kernel process level transfer of user requested services
CA1323448C (fr) 1989-02-24 1993-10-19 Terrence C. Miller Structure de fichiers transparente et methode et appareil correspondants
US5165030A (en) 1989-03-10 1992-11-17 International Business Machines Corporation Method and system for dynamic creation of data stream based upon system parameters and operator selections
CA2067633C (fr) 1991-07-24 1996-10-01 Eric Jonathan Bauer Methode et dispositif d'acces a un systeme d'archivage informatise
JPH06168135A (ja) * 1992-11-30 1994-06-14 Hitachi Ltd ファイル転送終了後の利用者プログラム起動方式
EP0629960B1 (fr) * 1993-06-17 2000-05-24 Sun Microsystems, Inc. Système de fichiers extensibles
JPH0765032A (ja) * 1993-08-27 1995-03-10 Toshiba Corp データベース言語変換機能を持つ情報処理システム
US5600833A (en) * 1993-09-17 1997-02-04 Digital Equipment Corp. Attribute portion based document retrieval system with system query language interface
US5584023A (en) * 1993-12-27 1996-12-10 Hsu; Mike S. C. Computer system including a transparent and secure file transform mechanism
JPH07306839A (ja) * 1994-05-11 1995-11-21 Hitachi Ltd ネットワークファイルのアクセス高速化方法
US5603019A (en) 1994-07-25 1997-02-11 International Business Machines Corporation Takeover technique for networked virtual filesystems
US5701463A (en) 1994-09-09 1997-12-23 Cheyenne Advanced Technology Limited Method of replacing the identity of a file with another as part of a file open request in a computer system
JPH08137728A (ja) * 1994-09-14 1996-05-31 Toshiba Corp 携帯ファイルシステム及びファイルデータ処理方法
US5634127A (en) * 1994-11-30 1997-05-27 International Business Machines Corporation Methods and apparatus for implementing a message driven processor in a client-server environment
JPH08314787A (ja) * 1995-05-12 1996-11-29 Nec Corp ファイルロケーション管理方式
US5859972A (en) * 1996-05-10 1999-01-12 The Board Of Trustees Of The University Of Illinois Multiple server repository and multiple server remote application virtual client computer
JPH10133924A (ja) * 1996-10-28 1998-05-22 Ricoh Co Ltd データ処理装置
US5963958A (en) * 1997-07-18 1999-10-05 Electronic Data Systems Corporation Method and system for generating object definitions
US6085199A (en) 1997-11-24 2000-07-04 International Business Machines Corporation Method for distributing a file in a plurality of different file formats

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5163131A (en) * 1989-09-08 1992-11-10 Auspex Systems, Inc. Parallel i/o network file server architecture
US5355453A (en) * 1989-09-08 1994-10-11 Auspex Systems, Inc. Parallel I/O network file server architecture
US5802366A (en) * 1989-09-08 1998-09-01 Auspex Systems, Inc. Parallel I/O network file server architecture
US5931918A (en) * 1989-09-08 1999-08-03 Auspex Systems, Inc. Parallel I/O network file server architecture
US5454098A (en) * 1992-09-28 1995-09-26 Conner Peripherals, Inc. Method of emulating access to a sequential access data storage device while actually using a random access storage device
US5463772A (en) * 1993-04-23 1995-10-31 Hewlett-Packard Company Transparent peripheral file systems with on-board compression, decompression, and space management
US5636371A (en) * 1995-06-07 1997-06-03 Bull Hn Information Systems Inc. Virtual network mechanism to access well known port application programs running on a single host system

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
BRORSSON M.: "A Decentralized Virtual Memory Scheme Implemented on an Emulated Multiprocessor, Architecture Track", PROCEEDINGS OF THE TWENTY-SECOND ANNUAL HAWAII INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES,, vol. 1, 1989, pages 286 - 295, XP002923282 *
FINN N. AND MASON T.: "ATM LAN Emulation", IEEE COMMUNICATIONS MAGAZINE,, vol. 346, June 1996 (1996-06-01), pages 96 - 100, XP002923284 *
See also references of EP1112537A4 *
SVENSSON A.: "Software Primitives for Emulation of Multiprocessor Architectures", PROCEEDINGS ON THE TWENTY-THIRD ANNUAL HAWAII INTERNATIONAL CONFERENCE ON SYSTEM SCIENCES., 1990, pages 48 - 56, XP002923283 *

Cited By (47)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6922708B1 (en) 1999-02-18 2005-07-26 Oracle International Corporation File system that supports transactions
US8065320B2 (en) 1999-08-05 2011-11-22 Oracle International Corporation Multi-model access to data
US7418435B1 (en) 1999-08-05 2008-08-26 Oracle International Corporation Multi-model access to data
US7620620B1 (en) 1999-08-05 2009-11-17 Oracle International Corporation Basing directory contents on a query that is associated with a file identifier
US7280995B1 (en) 1999-08-05 2007-10-09 Oracle International Corporation On-the-fly format conversion
SG91903A1 (en) * 2000-03-30 2002-10-15 Ibm File system locking
GB2365556A (en) * 2000-08-04 2002-02-20 Hewlett Packard Co Gateway device for remote file server services
GB2365556B (en) * 2000-08-04 2005-04-27 Hewlett Packard Co Gateway device for remote file server services
WO2002017140A3 (fr) * 2000-08-18 2003-12-31 Apple Computer Procede et systeme permettant d'acceder de maniere transparente a des fichiers stockes a distance
US8321483B2 (en) 2000-08-18 2012-11-27 Apple Inc. Method and system for seamlessly accessing remotely stored files
US6842770B1 (en) 2000-08-18 2005-01-11 Apple Computer, Inc. Method and system for seamlessly accessing remotely stored files
US7693962B2 (en) 2000-08-18 2010-04-06 Apple Inc. Method and system for seamlessly accessing remotely stored files
US7058648B1 (en) 2000-12-01 2006-06-06 Oracle International Corporation Hierarchy-based secured document repository
JP2002318719A (ja) * 2001-04-24 2002-10-31 Hitachi Ltd 高信頼計算機システム
US8694510B2 (en) 2003-09-04 2014-04-08 Oracle International Corporation Indexing XML documents efficiently
US7627547B2 (en) 2004-11-29 2009-12-01 Oracle International Corporation Processing path-based database operations
US8176007B2 (en) 2004-12-15 2012-05-08 Oracle International Corporation Performing an action in response to a file system event
US7921076B2 (en) 2004-12-15 2011-04-05 Oracle International Corporation Performing an action in response to a file system event
US8131766B2 (en) 2004-12-15 2012-03-06 Oracle International Corporation Comprehensive framework to integrate business logic into a repository
JP2006244493A (ja) * 2005-02-28 2006-09-14 Microsoft Corp データベース内で表現されるファイル・システム
US8959125B2 (en) 2005-07-01 2015-02-17 226008 Ontario Inc. File system having inverted hierarchical structure
US7873683B2 (en) 2005-07-01 2011-01-18 Qnx Software Systems Gmbh & Co. Kg File system having transaction record coalescing
US7970803B2 (en) 2005-07-01 2011-06-28 Qnx Software Systems Gmbh & Co. Kg Optimized startup verification of file system integrity
US8356053B2 (en) 2005-10-20 2013-01-15 Oracle International Corporation Managing relationships between resources stored within a repository
US8949455B2 (en) 2005-11-21 2015-02-03 Oracle International Corporation Path-caching mechanism to improve performance of path-related operations in a repository
US9898545B2 (en) 2005-11-21 2018-02-20 Oracle International Corporation Path-caching mechanism to improve performance of path-related operations in a repository
EP1898322A1 (fr) * 2006-08-25 2008-03-12 QNX Software Systems GmbH & Co. KG Système de fichier multimédia ayant une représentation unifiée de contenu de dispositifs multimédia divers
US7908276B2 (en) 2006-08-25 2011-03-15 Qnx Software Systems Gmbh & Co. Kg Filesystem having a filename cache
US8566503B2 (en) 2006-08-25 2013-10-22 Qnx Software Systems Limited Multimedia filesystem having unified representation of content on diverse multimedia devices
WO2008048388A3 (fr) * 2006-10-13 2008-06-19 Spansion Llc Contrôleur virtuel de carte mémoire
US10650080B2 (en) 2006-10-16 2020-05-12 Oracle International Corporation Managing compound XML documents in a repository
US7827177B2 (en) 2006-10-16 2010-11-02 Oracle International Corporation Managing compound XML documents in a repository
US9183321B2 (en) 2006-10-16 2015-11-10 Oracle International Corporation Managing compound XML documents in a repository
KR100728517B1 (ko) * 2006-12-28 2007-06-15 메크로비젼 코오포레이션 동적으로 연결 가능한 실행 가능 이미지들의 진정성을증명하는 시스템 및 방법
WO2008102159A1 (fr) * 2007-02-23 2008-08-28 Quantel Limited Système de serveur de fichiers
US7958112B2 (en) * 2008-08-08 2011-06-07 Oracle International Corporation Interleaving query transformations for XML indexes
GB2489932B (en) * 2011-04-07 2020-04-08 Quantel Ltd Improvements relating to file systems
GB2489932A (en) * 2011-04-07 2012-10-17 Quantel Ltd File generation on request
US11714858B2 (en) 2011-04-07 2023-08-01 Grass Valley Limited Methods and systems for providing file data from a file system
WO2012136977A2 (fr) 2011-04-07 2012-10-11 Quantel Limited Perfectionnements relatifs à des systèmes de fichier
US10019448B2 (en) 2011-08-05 2018-07-10 Quantel Limited Methods and systems for providing file data for media files
US10321167B1 (en) 2016-01-21 2019-06-11 GrayMeta, Inc. Method and system for determining media file identifiers and likelihood of media file relationships
US11176103B2 (en) 2016-10-11 2021-11-16 Petagene Ltd System and method for storing and accessing data
EP3309697A1 (fr) * 2016-10-11 2018-04-18 Petagene Ltd. Système et procédé de de mise en mémoire et d'accès à des données
US10719492B1 (en) 2016-12-07 2020-07-21 GrayMeta, Inc. Automatic reconciliation and consolidation of disparate repositories
US11443833B2 (en) 2017-05-24 2022-09-13 Petagene Ltd. Data processing system and method
WO2018215634A1 (fr) * 2017-05-24 2018-11-29 Petagene Ltd. Système et procédé de traitement de données

Also Published As

Publication number Publication date
JP2002524793A (ja) 2002-08-06
US6356863B1 (en) 2002-03-12
AU5782999A (en) 2000-03-27
EP1112537A4 (fr) 2006-04-05
EP1112537A1 (fr) 2001-07-04
JP5019669B2 (ja) 2012-09-05

Similar Documents

Publication Publication Date Title
US6356863B1 (en) Virtual network file server
Braam The Lustre storage architecture
US5623666A (en) Distributed computing system
US6470345B1 (en) Replacement of substrings in file/directory pathnames with numeric tokens
US9087076B2 (en) Automated filer technique for use in virtualized appliances and applications
JP3968242B2 (ja) 共有データにアクセスするための方法と装置
US7890689B2 (en) Virtual appliance management
US8606886B2 (en) System for conversion between physical machines, virtual machines and machine images
KR101544717B1 (ko) 소프트웨어 정의 네트워크 연결 저장 시스템 및 방법
US6895400B1 (en) Dynamic symbolic link resolution
US9087066B2 (en) Virtual disk from network shares and file servers
US8285817B1 (en) Migration engine for use in a logical namespace of a storage system environment
Chen et al. vNFS: Maximizing NFS performance with compounds and vectorized I/O
US9569443B1 (en) Method and apparatus for providing access to data in unsupported file systems and storage containers
Van Hensbergen et al. Grave Robbers from Outer Space: Using 9P2000 Under Linux.
US7167867B1 (en) Self-describing file system
US20080065698A1 (en) Method and apparatus for emulating alternate data streams across heterogeneous file systems
Krzyzanowski Distributed file systems design
Minnich 9.2. u: A user-mode private name space system for unix
Forsyth The ubiquitous file server in Plan 9
CA2524549C (fr) Systeme permettant la conversion entre des machines materielles, des machines virtuelles et des images machine
Fan et al. EDDE: Container Deployment Framework Beyond the Cloud
Ballesteros et al. ZX: A network file system for high‐latency networks
Baker Server virtualization
Stangel A prototype implementation of a virtual file system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
REEP Request for entry into the european phase

Ref document number: 1999945151

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 1999945151

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2000 569312

Country of ref document: JP

Kind code of ref document: A

WWP Wipo information: published in national office

Ref document number: 1999945151

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642