EP0780778A2 - Système et méthode pour monter automatiquement et accéder à des systèmes de fichiers éloignés dans Microsoft Windows dans un environnement en réseau - Google Patents

Système et méthode pour monter automatiquement et accéder à des systèmes de fichiers éloignés dans Microsoft Windows dans un environnement en réseau Download PDF

Info

Publication number
EP0780778A2
EP0780778A2 EP96309359A EP96309359A EP0780778A2 EP 0780778 A2 EP0780778 A2 EP 0780778A2 EP 96309359 A EP96309359 A EP 96309359A EP 96309359 A EP96309359 A EP 96309359A EP 0780778 A2 EP0780778 A2 EP 0780778A2
Authority
EP
European Patent Office
Prior art keywords
storage device
logical storage
file system
virtual logical
remote
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.)
Withdrawn
Application number
EP96309359A
Other languages
German (de)
English (en)
Other versions
EP0780778A3 (fr
Inventor
Joseph E. Provino
Philip M. Rosenzweig
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.)
Sun Microsystems Inc
Original Assignee
Sun Microsystems Inc
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 Sun Microsystems Inc filed Critical Sun Microsystems Inc
Publication of EP0780778A2 publication Critical patent/EP0780778A2/fr
Publication of EP0780778A3 publication Critical patent/EP0780778A3/fr
Withdrawn legal-status Critical Current

Links

Images

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

Definitions

  • the invention relates generally to the field of digital computer systems and more specifically to a system and method for facilitating the automounting and accessing of remote mass storage subsystem storage devices for use in connection with the Microsoft Windows operating system in a networking environment.
  • a number of personal computers, workstations, and other devices such as mass storage subsystems, network printers and interfaces to the public telephony system, are typically interconnected in a computer network.
  • the personal computers and workstations are used by individual users to perform processing in connection with data and programs that may be stored in the network mass storage subsystems.
  • the personal computers/workstations operating as clients, download the data and programs from the network mass storage subsystems for process.
  • the personal computers or workstations will enable processed data to be uploaded to the network mass storage subsystems for storage, to a network printer for printing, to the telephony interface for transmission over the public telephony system, or the like.
  • the network mass storage subsystems, network printers and telephony interface operate as servers, since they are available to service requests from all of the clients in the network.
  • the servers are readily available for use by all of the personal computers/workstations in the network.
  • Such a network may be spread over a fairly wide area, with the personal computers/workstations being interconnected by communication links such as electrical wires or optic fibers.
  • GUI graphical user interface
  • File systems used with modern operating systems are typically organized into a number of directories, with each file that is accessible through the file system being associated with a directory.
  • the directories themselves are generally organized in a tree structure.
  • the directory tree structure for a file system normally includes an upper level "root” directory, which has one or more child directories.
  • Each of the root directories' child directories may also have one or more child directories, and so on down the tree.
  • Each directory is essentially a file (a "directory file") that contains information including the location(s) in the mass storage subsystem of files in the directory and pointers to directory files for its child directories and also a pointer to the directory file for its parent directory, that is, the directory of which it is a child.
  • directory file a file that contains information including the location(s) in the mass storage subsystem of files in the directory and pointers to directory files for its child directories and also a pointer to the directory file for its parent directory, that is, the directory of which it is a child.
  • the directory files along the path from the root directory to the directory containing the file are searched to locate the successive directory files along the path, until the directory file is located for the directory containing the file to be accessed.
  • the location information in the directory file is used to find the location of the file to be accessed.
  • a file system Before a file system, or a portion of a file system, can be accessed (that is, before a file in the file system or portion thereof can be accessed) it must be “mounted.” Mounting among other things conditions the pointers in the directory files so that the path through the file system's directory structure can be traversed.
  • Some operating systems such as Unix, provide a uniform file system to each particular computer user, without respect to the particular mass storage subsystems or devices on which the files are stored; that is, the file system that is available to a user may extend across a number of devices.
  • directories and files on the storage device may be added to the file system by "mounting" the storage device, which makes its directory on the storage device available to the users in a seamless manner.
  • the directories and files on the storage device will be deleted from the file system (although they may still reside on the storage device being removed), in which case they will not be available to the users.
  • the MS-DOS and Windows operating systems also allow for a file system having a tree-structured directory structure.
  • the file systems are intimately related to a "device," which may be, for example, a particular physical storage device or a local device which may be a subset of the physical device.
  • access to a file requires identifying a particular device, thus each device essentially defines at least one file system, and to access a file on a device's file system a file specifier requires specification of a particular device as well as the path along the directory structure on the device to the particular file to be accessed.
  • the invention provides a new and improved system and method for facilitating the automounting and accessing of remote file systems in a networking environment for use in connection with the Microsoft MS-DOS and Windows operating systems in a networking environment.
  • the invention provides a virtual file system accessing subsystem for use in connection with a computer system connected in a computer network.
  • the computer system runs a selected operating system, such as Microsoft's MS-DOS and Windows operating systems.
  • the virtual file system accessing subsystem facilitates the accessing of a virtual logical storage device that is identified by a virtual logical storage device identifier and that has a virtual logical storage device file system that includes at least a portion of a remote file system maintained by another device connected in the computer network.
  • the virtual file system accessing subsystem comprises an operating system request redirector for enabling the operating system to direct access requests from an application program which identify the virtual logical storage device to a remote access element for processing.
  • the remote access element initiates access operations in connection with the portion of the remote file system which is included in the virtual logical storage device file system in response to an access request that is generated by an application program which identifies the virtual logical storage device identifier, which access request has been transferred thereto by the operating system. If the portion of the remote file system being accessed has not previously been mounted, the remote access element enables an automounting element to initiate a mounting operation in connection with the remote file system to mount the portion, after which the remote access element can perform the access operation.
  • the virtual logical storage device identified by a single identifier, can be used to identify portions of a number of remote file systems, so that an application program can access a number of remote file systems using a single device identifier.
  • the invention provides a virtual file system accessing subsystem for use in connection with a computer system connected in a computer network.
  • the computer system runs a selected operating system, such as Microsoft's MS-DOS and Windows operating systems.
  • the virtual file system accessing subsystem facilitates accessing of a plurality of virtual logical storage devices, each identified by a virtual logical storage device identifier.
  • Each virtual logical storage device has a virtual logical storage device file system that includes at least a portion of a remote file system maintained by another device connected in the computer network, at least some virtual logical storage device file systems including a hierarchical directory system defining a plurality of possible paths each having a path identifier.
  • At least one of the virtual logical storage device file systems that include hierarchical directory systems has an associated default path comprising one of the possible paths.
  • the virtual file system accessing subsystem includes an operating system request redirector for enabling the operating system to direct access requests received from an application program which identify a the virtual logical storage device to the remote access element.
  • the operating system receiving access requests from a the application program and provides, to a remote access element, those access requests which include the virtual logical storage device identifier.
  • the operating system provides to the remote access element, for the access requests received from the application program which do not include a path identifier, a path identifier for the default path for the virtual logical storage device identified by the virtual logical storage device.
  • a remote access element initiates an access operation in connection with the virtual logical storage device file system maintained by the virtual logical storage device in response to access requests received from the operating system which include the virtual logical storage device identifier and a the path identifier.
  • the remote access element accesses the portion of the remote file system that is included in the virtual logical storage device file system along the path identified by the path identifier.
  • the invention provides a virtual file system accessing subsystem for use in connection with a computer system connected in a computer network.
  • the computer system runs a selected operating system, such as Microsoft's MS-DOS and Windows operating systems.
  • the virtual file system accessing subsystem facilitates accessing of a virtual logical storage device that is identified by a virtual logical storage device identifier and that has a virtual logical storage device file system that includes an identifier identifying at least a portion of a remote file system maintained by another device connected in the computer network.
  • the virtual file system accessing subsystem comprises an operating system request redirector for enabling the operating system to direct access requests which identify the virtual logical storage device to a remote access element.
  • the remote access element initiates an access operation in connection with the virtual logical storage device file system maintained by the virtual logical storage device in response to an access request that the remote access element receives from the operating system which includes the virtual logical storage device identifier. During the access operation, the remote access element accesses the portion of the remote file system identified by the remote file system portion identifier.
  • FIG. 1 is a schematic diagram of a computer network including a system for automounting mass storage subsystem storage devices in Microsoft windows, constructed in accordance with the invention.
  • computer network 10 includes a plurality of computers 11(1) through 11(N) (generally identified by reference numeral 11(n)) and 12 which are interconnected by a communication link 13.
  • computers 11(n) are in the form of personal computers or computer workstations, each of which includes a system unit, a video display unit and operator input devices such as a keyboard and mouse.
  • the computer 12 also includes a system unit, and may also include a video display unit and operator input devices.
  • the computers 11(n) and 12 are of the conventional stored-program computer architecture.
  • a system unit generally includes processing, memory, mass storage devices such as disk and/or tape storage elements and other elements (not separately shown), including network interface devices 14(n), 15 for interfacing the respective computer to the communication link 13.
  • a video display unit permits the computer to display processed data and processing status to the user, and an operator input device enable the user to input data and control processing by the computer.
  • the computers 11(n) and 12 transfer information, in the form of messages, through their respective network interface devices 14(n), 15 among each other over the communication link 13.
  • the network 10 is organized in a "client-server" configuration, in which at least one computer, namely, computer 12, operates as a server, and the other computers 11(n) operate as clients.
  • the servers include large-capacity mass storage devices which can store copies of programs and data which are available for retrieval by the client computers over the communication link 13 for use in their processing operations.
  • a client computer 11(n) may also store data on the server computer 12, which may be later retrieved by it (the client computer that stored the data) or other client computers for use in their processing operations.
  • the server computers may be generally similar to the client computers 11(n), including a system unit, video display unit and operator input devices and may be usable by an operator for data processing operations in a manner similar to a client computer.
  • the server computers may include only processing, memory, mass storage and network interface elements for receiving and processing retrieval or storage requests from the client computers, and generating responses thereto.
  • the communication link 13 interconnecting the client computers 11(n) and server computer 12 in the network 10 may, as is conventional, comprise wires, optical fibers or other media for carrying signals representing information among the computers 11(n) and 12.
  • each of the computers 11(n) typically includes a network interface device (represented by respective arrows 14(n) and 15), which connects the respective computer to the communications link 13.
  • the computers 11(n) use the Microsoft WindowsTM operating system program ("Windows"), and the server computer 12 uses the Microsoft Windows-NT operating system program.
  • Windows provides a number of conventional operating system services in connection with the computers 11(n), including initializing the computers when they are powered-up or reinitialized.
  • Windows provides a number of conventional operating system services to applications programs that are processed by the computers, including providing a graphical user interface ("GUI").
  • GUI graphical user interface
  • MS-DOS and Windows also facilitate accessing files (that is, reading of data from and storage of data in the files) in file systems maintained in the system 10.
  • MS-DOS and Windows enable a computer 11(n) to access local file systems provided by the computer system's local mass storage subsystem(s), and also to access remote file systems which are maintained by other computer systems 11(n') (n' ⁇ n) and the server computer 12.
  • the invention provides a system and method for use with, for example, the Microsoft MS-DOS and Microsoft WindowsTM operating systems, to provide for automounting of virtual logical storage devices to facilitate ready access by a computer 11(n).
  • a virtual logical storage device may comprise one or more directories or directory sub-trees that are associated with a single device specifier.
  • a virtual logical device may be formed from directories that are located on a single mass storage subsystem or on a number of mass storage subsystems, with all of the directories forming the virtual logical device being aggregated for reference by a single device identifier.
  • One or more of the directories may be located on a local mass storage subsystem, that is, a mass storage subsystem located on the computer system 11(n).
  • Other directories on the virtual logical storage device may be located on a mass storage subsystem maintained by another computer system, including any of the computer systems 11(n') (n' ⁇ n) connected in the network, and still other directories may be located on mass storage subsystems maintained by the server computer 12.
  • MS-DOS and Windows can access files that are in the directories in the same manner that they access files in file systems that are on a device that is specified by a device identifier that identifies a real storage device in the mass storage subsystem maintained for the computer system 11(n).
  • a remote mass storage subsystem that is, a mass storage subsystem maintained by another computer system 11(n') (n' ⁇ n) or by the server computer 12
  • MS-DOS and Windows access the files in those directories by performing a remote access operation.
  • a remote access operation by transferring messages over the communication link 14 in a conventional manner.
  • allowing the operator or application programs to access file systems on a number of physical devices by use of a virtual logical storage device identifier without needing to know the actual physical locations of the physical devices or network protocols required to access the file systems, simplifies file access by the operator or application programs.
  • FIG. 2 depicts a detailed functional diagram of computer system 11(n) for use in connection with the invention.
  • the computer system 11(n) processes application programs generally identified by reference numeral 20, in connection with the MS-DOS and Windows operating systems generally identified by reference numeral 21.
  • application programs With particular reference to accessing of a file in a file system that is maintained by either one of the computer system's local storage device 22 or virtual logical storage devices, the application programs will issue access requests "ACC REQ," to the MS-DOS/Windows operating systems 21.
  • the access request will generally be of the form DEV-ID: ⁇ PATH ⁇ FILENAME ⁇ , where DEV-ID identifies a particular storage device (which may be either a local device 22 or a virtual logical storage device), ⁇ PATH ⁇ identifies a path through the device's directory structure, and ⁇ FILENAME ⁇ is a filename identifying a file in the directory identified by the path identifier ⁇ PATH ⁇ . If the storage device is a currently-selected default device, the access request need not include the device identifier DEV-ID. Similarly, if the storage device and path are a currently-selected default device and path, the access request need not explicitly include the device identifier DEV-ID and path identifier ⁇ PATH ⁇ .
  • the MS-DOS/Windows operating system 21 When the MS-DOS/Windows operating system 21 receives the access request ACC REQ from the application program 20, it initially determines whether the device to be accessed is a local device 22 or a virtual logical storage device. If the MS-DOS/Windows operating system 21 determines that the access request ACC REQ is for a local device 22, it initiates a local access operation LOC ACC in connection with the local device 22. It will be appreciated that the particular operation to be performed will depend on the type of operation specified in the ACC REQ, including, for example, opening and closing of the particular file ⁇ FILENAME ⁇ , storing data in the file or retrieving data therefrom, or the like.
  • the MS-DOS/Windows operating system 21 determines that the access request ACC REQ is for a virtual logical storage device, it issues a remote access REM ACC to a network file system client module 23.
  • the network file system client module 23 handles certain message transfers over the network communication link 14, with specific reference to the invention initiating the access operation in connection with the actual physical device which contains the portion of virtual logical storage device's file system which contains the path ⁇ PATH ⁇ and file ⁇ FILENAME ⁇ identified in the access request ACC REQ.
  • the network file system client module 23 Prior to initiating the access operation, the network file system client module 23 will determine whether the portion of the virtual logical storage's device file system containing the file ⁇ FILENAME ⁇ to be accessed has been mounted. If the network file system client module 23 determines that the portion of the virtual logical storage device containing the file ⁇ FILENAME ⁇ to be accessed has been mounted, it can initiate the access operation through a network interface 24. In that operation, the network file system client module 23 and, for example, the server control module 31 of the server computer 12 which maintains the physical storage device 32 whose file system contains the portion of the virtual logical storage device's file system as defined by the access request ACC REQ, will exchange messages through their respective network interfaces 24 and 33 to enable the server control module 31 to perform the access operation.
  • the network file system client module 23 determines that the portion of the virtual logical storage device containing the file ⁇ FILENAME ⁇ to be accessed has not been mounted, it (the network file system client module 23) provides an automount request AUTOMNT REQ to an automounter module 25.
  • the automounter module 25 will initiate a mounting operation in connection with (continuing with the previous example) the server control module 31 of the server computer 12 which maintains the physical storage device 32 whose file system contains the portion of the virtual logical storage device's file system as defined by the access request ACC REQ.
  • the automounter module 25 and server control module 31 will exchange messages through their respective network interfaces 24 and 33 over the network 14.
  • the automounter module 25 updates various data structures, will be described below.
  • the data structures contain information for each file system which has been mounted by the automounter module 25, which is used by the network file system client module 23 in processing an access request for an access operation for the respective file system.
  • the network file system client module 23 can use the new information to process the access request as described above.
  • the automounter 25 will automatically mount remote file systems or portions thereof as they are needed by access requests ACC REQ from the application programs 20 to the virtual logical storage device(s) maintained by the computer system 11(n).
  • the network file system client 23 can also keep track of the access requests for the various mounted remote file systems, and for those remote file systems which have not been accessed within a predetermined amount of time, initiate unmounting. If the network file system client module 23 has unmounted a remote file system, it may be later remounted by the automounter 25 in the same manner as described above.
  • the network file system client module 23 and automounter 25 make use of several items of information in identifying virtual logical storage device(s) and the remote file systems which form the file system(s) of the respective virtual logical storage device(s), which will be described in connection with FIG. 3.
  • the computer system's initialization file 40 includes a number of fields containing automount information used by the network file system client module 23 and automounter 25, including a virtual device identifier field 41, a maximum automounts field 42, an automount timeout field 43 and a map file identifier field 44.
  • the initialization file 40 is used by the MS-DOS/Windows operating system module 21 to initialize the computer system 11(n), and may comprise, for example, an ".INI” initialization file which contains initialization and environment information used to define the processing environment under Windows.
  • an ".INI” initialization file which contains initialization and environment information used to define the processing environment under Windows.
  • a Windows file with the complete file name of the form "XXX.INI” file has "XXX" as a file name, and "INI” as the file extension.
  • the ".INI” file extension identifies the file as an initialization file.
  • the virtual device identifier field 41 of initialization file 40 contains information to identify virtual logical storage device(s), in particular providing the specific device identifier(s) DEV-ID for the virtual logical storage device(s). If the virtual device identifier field 41 is empty, a selected device identifier is used as a default virtual device identifier, in particular a device identifier that is selected as a "last device” identifier for the computer system 11(n).
  • a "last device” identifier may be specified in, for example a system configuration file identified by filename "CONFIG.SYS.” It will be appreciated that the virtual device identifier field 41 may contain a single device identifier or a number of device identifiers; if the virtual device identifier field 41 contains a number of device identifiers, each different device identifier may individually identify a virtual logical storage device.
  • the maximum automounts field 42 contains a value which identifies the maximum number of remote file systems which can be mounted.
  • the automount timeout field 43 contains a timeout value which identifies the maximum time, following issuance by the automounter module 25 of an automount request AUTOMNT REQ, that the automounter module 25 will wait for an acknowledgment that the requested remote file system has been mounted.
  • the map file identifier field 44 contains a pointer to a file containing an automount master map, which is identified in FIG. 3 by reference numeral 50.
  • the automount master map contains information which identifies the various file systems that are to be automounted and accessed using the virtual logical storage device identifiers in the device identifier field 41.
  • the same automount master map 50 is used for all device identifiers if the device identifier field 41 contains multiple device identifiers, although it will be appreciated that a separate automount master map 50 may be provided for each device identifier. As shown in FIG.
  • the automount master map 50 includes one or more entries 51(1) through 51(N) (generally identified by reference numeral 51(n)), each of which is associated with a high-level directory in the file system associated with the virtual logical storage device(s).
  • Each entry 51(n) includes a number of fields, including a directory name field 52(n), an automount subdirectory name field 53(n), and an options field 54(n).
  • Each of the directory name fields 52(n) contains a directory name, which will be used as the name of the topmost directory in a directory tree.
  • Subdirectories under the top level directory, along with pointers to remote file systems, or portions thereof, forming the respective sub-directories, are identified in an automount subdirectory map file identified by reference numeral 60, which will be described below.
  • the automount subdirectory name field 53(n) identifies the automount subdirectory map file 60 that is to be associated with the directory identified in field.
  • the options field 54(n) contains values for a number of optional parameters which may control mounting of the remote file system and accessing of files, including whether the file system can be read, written or both, whether files can be locked, a mount timeout value and a mount attempt retry value, and the like.
  • an automount subdirectory map file 60 identifies the components of the file system under the top level directory.
  • an automount subdirectory map file 60 may contain subdirectory identifiers, or alternatively it may contain explicit identifiers for a remote computer system 11(n') (n' ⁇ n) or the server computer 12 and path thereon.
  • an automount subdirectory map file 60 contains an explicit identifier for a remote computer system 11(n') (n' ⁇ n) or the server computer 12 and path thereon, that may be indicated by an appropriate indication in the options field 54(n) of the entry 51(n) of the automount master map 50 which points thereto, in one particular embodiment, an option "HOST" is used to identify such a map 60.
  • a pointer to a remote file system or portion thereof is provided which forms the respective subdirectory.
  • the automount subdirectory map file 60 includes a number of entries 61(1) through 61(M) (generally identified by reference numeral 61(m)) each of which is associated with a subdirectory under the top level directory whose automount subdirectory name field 53(n) points to the automount subdirectory map file 60.
  • Each entry 61(m) includes two fields, namely, a subdirectory name field 62(m) and a remote file system pointer field 63(m).
  • the subdirectory name field 62(m) contains a subdirectory name which identifies the subdirectory under the top level directory, or the explicit identifier of a remote computer system 11(n') (n' ⁇ n) or the server computer 12 and path thereon.
  • the remote file system pointer field 63(m) contains a pointer to the remote file system, or portion thereof, (identified by reference numeral 64) which is to be mounted for the subdirectory identified in subdirectory name field 62(m).
  • the remote file system pointer field 63(m) contains, for example, the name of a remote computer system 11(n') (n' ⁇ n) or server computer 12.
  • the automount subdirectory map files 60 that are pointed to by the automounter master map file 50 effectively define the mount points for the virtual logical storage device(s); that is, they define the various subdirectories under the respective directories identified in the automount master map file 50, and in addition identify the particular elements of the remote file systems which comprise the portions of the file system of computer system 11(n) mounted at those mount points.
  • the computer system 11(n) is provided with a single automount master map 50, which is pointed to by the map file identifier field 44 in the initialization file 40.
  • the device identifiers field 41 contains identifiers for a number of virtual logical storage devices, all of the virtual logical storage devices will have the same top-level directory or directories, which are set forth in the map automount master map 50, and will also have the same subdirectories as identified in the automount subdirectory map file 60. It will be appreciated, however, that different computer system 11(n) may have different sets of virtual logical storage devices, since the map file identifier fields 44 in their respective initialization files 40 may differ.
  • FIG. 4 depicts operations performed to initialize the automounter module 25, including generation of an automount control block which contains information that is provided to the network file system client module 23 and establishment of a connection used by the automounter module 25 for communicating with the network file system client module 23.
  • FIG. 4 depicts operations performed to initialize the automounter module 25, including generation of an automount control block which contains information that is provided to the network file system client module 23 and establishment of a connection used by the automounter module 25 for communicating with the network file system client module 23.
  • FIG. 5 depicts operations performed by the network file system client module 23 in connection with remote access requests REM ACC from the MS-DOS/Windows operating system 21, including determining whether the portion of a virtual logical storage device's file system referenced in the remote access request has been mounted and, if not, issuing automount requests AUTOMNT REQ to the automounter module 25 to enable it (the automounter module 25) to perform the mount operation.
  • FIG. 6 depicts operations performed by the automounter module 25 in response to automount requests AUTOMNT REQ which the network file system client module 23 may issue if the portion of the remote file system to be accessed has not been mounted.
  • a socket is created which serves to provide communications between the automounter module 25 and the network file system client module 23, and the automounter module 25 binds itself to one port of the socket.
  • a socket is a conventional communications structure and will not be described herein.
  • information is obtained from the various structures described above in connection with FIG. 3 and used in generating the automount control block, and a pointer to the automount control block is passed to the network file system client module 23.
  • the MS-DOS/Windows operating system 21 is notified of the identifiers of the virtual logical storage devices and enabled to direct access requests which include the virtual logical storage device identifiers to the network file system client module 23. (Enabling the MS-DOS/Windows operating system 21 to redirect access requests is a conventional operation.)
  • the automounter module 25 first issues a request to the MS-DOS/Windows operating system 21 requesting establishment of a socket (step 100). If the MS-DOS/Windows operating system 21 establishes a suitable socket, it (the MS-DOS/Windows operating system 21) will provide a return value which is a socket identifier which the automounter module 25 may use in communicating with the network file system client module 23. On the other hand, if the MS-DOS/Windows operating system 21 is unable to establish a socket, it will provide a return value that corresponds to an error code. Accordingly, following step 100, the automounter module 25 will examine the return value to determine whether it is a socket identifier or an error code (step 101).
  • step 101 If the automounter module 25 determines in step 101 that the return value is an error code, it will terminate with an appropriate message (step 102). On the other hand, if the automounter module 25 determines in step 101 that the return value is a socket identifier, it will use the socket identifier to retrieve selected information about the socket and bind itself to the socket (step 103).
  • the automounter module 25 will initialize the automount control block and pass the information therein to the network file system client module 23. In that operation, the automounter module 25 retrieves the contents of the automount master map 50 and loads it into the automount control block (step 104). In addition, the automounter module 25 determines whether the initialization file 40 includes a virtual logical storage device identifier field 41 (step 105) and if so copies the virtual logical storage device identifier values from the field 41 into the automount control block (step 106).
  • the automounter module 25 determines in step 105 that the initialization file 40 does not include a virtual logical storage device identifier field 41, the automounter module 25 will make a call to the MS-DOS/Windows operating system 21 to determine the last drive identifier (step 107), which it will then copy into the automount control block as the virtual logical storage device identifier (step 108).
  • the automounter module 25 will determine whether the initialization file 40 includes a maximum automount field 42 or an automount timeout field 43 (step 109), and if so will copy the contents of the respective fields into the automount control block (step 110). On the other hand, if the automounter module 25 determines in step 109 that the initialization file 40 does not include either or both of fields 42 or 43, it will sequence to step 111 to load a predetermined default value or values in the automount control block (step 112).
  • the automounter module 25 will send a notification to the network file system client module 23, including the socket identifier for the socket established in steps 100-103 and a pointer to the automount control block (step 113).
  • the automounter module 25 will issue a request to the MS-DOS/Windows operating system 21 to redirect access requests for the virtual logical storage device(s) to the network file system client module 23 (step 114).
  • initialization will be complete and the automounter module 25 will wait until it receives an automount request AUTOMNT REQ from the network file system client module 23. Operations performed by the automounter module 25 in response to an automount request AUTOMNT REQ from the network file system client module 25 will be described below in connection with FIG. 6.
  • the network file system client module 23 will receive the socket identifier and pointer to the automount control block generated by the automounted module 25 during initialization as described above in connection with FIG. 4 (step 130). After receiving the pointer to the automount control block in step 130, the network file system client module 23 will use the information from the automount master map 50 which was loaded into the automount control block by the automounter module 25 during initialization (FIG. 4), along with the subdirectories listed in the automount subdirectory map files 60 to generate a directory tree for the virtual logical storage devices (step 131). An illustrative tree 70 is depicted in FIG. 7. With reference to FIG.
  • the directory tree 70 includes a series of entries 71(1) through 71(N) (generally identified by reference numeral 71(n)).
  • the first entry, identified as root entry 71(1) is pointed to by a root pointer 72.
  • Each entry 71(n) includes the identification of the virtual logical storage device directory identified in the correspondingly-indexed entry 51(n) in the automounter master map 50, as well as its children, which corresponds to the subdirectories identified in the automount subdirectory map file 60 identified by the entry 51(1), as well as two child pseudo-directories which are provided by the MS-DOS/Windows operating system 21. (The two child pseudo-directories are the ".” and "..” subdirectories. In FIG. 7, no real subdirectories are shown for the root entry 71(1) and entry 71(2)).
  • each entry 71(n) includes a "sibling" pointer to the entry 71(n+1) for the directory listed in the next entry 51(n+1) in the automount master map 50.
  • the "sibling" pointer for the last entry 71(N) will contain a null value, which will indicate that it is the last entry 71(N).
  • the entries 71(n) for the mountable subdirectories (that is, the real child subdirectories under each directory) provide mount information which is used by the network file system client module 23 in connection with remote accesses as will be described below.
  • the network file system client module 23 waits for remote access requests REM ACC from the MS-DOS/Windows operating system 21 (step 132).
  • the network file system client module 23 may perform selected housekeeping operations, such as enabling the automounter module 25 to unmounting remote file systems for which it (the network file system client module 23) has not received a remote access request REM ACC within a selected period of time.
  • the MS-DOS/Windows operating system 21 When the MS-DOS/Windows operating system 21 receives an access request ACC REQ from an application program 20 which either explicitly or implicitly identifies a virtual logical storage device, it (the MS-DOS/Windows operating system 21) will issue a remote access request REM ACC to the network file system client module 23.
  • the network file system client module 23 When the network file system client module 23 receives a remote access request REM ACC (step 133) it will initially verify that the device identified in the remote access request REM ACC is a virtual logical storage device and parse the request to verify that the directory path and filename specified in the request are valid (step 134).
  • the network file system client module 23 In verifying that the device identified in the remote access request REM ACC is a virtual logical storage device, the network file system client module 23 will compare the device identifier in the remote access request REM ACC to the virtual logical storage device identifier(s) in the automount control block to verify that the device identifier in the remote access request REM ACC corresponds to a virtual logical storage device identifier in the automount control block. Similarly, in determining whether the remote host or directory path and filename specified in the request are valid, the network file system client module 23 can use characteristics such as permitted naming conventions to verify that the name of each host or directory in the path and the filename in the remote access request are valid.
  • the network file system client module 23 If the network file system client module 23 makes a negative determination in step 134 (that is, if it determines that the device identifier in the remote access request REM ACC is not a virtual logical storage device identifier or that the host or subdirectory and file name are not valid), it provides a remote response REM RSP indicating an error (step 135).
  • the network file system client module 23 makes a positive determination in step 134 (that is, if it determines that the device identifier in the remote access request REM ACC is a virtual logical storage device identifier), it will reference the directory tree 70 to determine whether the high-level directory and next-level subdirectory in the remote access request REM ACC have been mounted (step 136). If the high-level directory and next-level subdirectory have been mounted, the directory tree 70 will contain a mount pointer to a mount structure for the remote file system corresponding to the portion of the virtual logical storage device's file system.
  • the network file system client module 23 If the network file system client module 23 makes a positive determination in step 136, it will use the information in the mount structure to initiate the remote access operation with the remote computer system 11(n') (n' ⁇ n) or server computer 12 (step 137).
  • the specific operations performed by the network file system client module 23 and the remote computer system 11(n') (n' ⁇ n) or server computer 12 in connection with the remote access operation will depend on the specific type of access operation. For example, if the access operation is a file open or close operation, the network file system client module 23 will generate, and the network interface 24 will transfer over communication link 14, one or more messages to the remote computer system 11(n') (n' ⁇ n) or server computer 12 to enable it to open or close the specified file.
  • the network file system client module 23 will generate, and network interface 24 will transfer, one or more messages to the remote computer system 11(n') (n' ⁇ n) or server computer 12 including a read request.
  • the remote computer system 11(n') (n' ⁇ n) or server computer 12 will read the information from the file as specified in the read request, and in one or more messages transferred over communication link 14 transfer the information to the network file system client module 23.
  • the network file system client module 23 may provide the information to the MS-DOS/Windows operating system 21, which, in turn, will provide the information to the requesting application program 20.
  • the network file system client module 23 will generate, and the network interface 24 will transfer one or more messages to the remote computer system 11(n') (n' ⁇ n) or server computer 12 including a write request and the data to be written.
  • the remote computer system 11(n') (n' ⁇ n) or server computer 12 will store the data in the file as specified in the write request.
  • the network file system client module 23 may initiate other access operations by generating and enabling the network interface 24 to transfer messages to the remote computer system 11(n') (n' ⁇ n) or server computer 12 in a similar manner.
  • the network file system client module 23 will return to step 132 to wait for the next remote access request REM ACC.
  • step 136 if the network file system client module 23 makes a negative determination in that step, that is, if it determines that the high-level directory and next-level subdirectory in the remote access request REM ACC have not been mounted, it will sequence to step 138 to enable the automounter module 25 to mount the remote file system required for the access. Communications between the network file system client module 23 and the automounter module 25 will be over the socket established in step 103 above. The operations performed by the automounter module 25 in connection with step 138 will be described in FIG. 6.
  • the automounter module 25 After the automounter module 25 has completed the mount operation, it (the automounter module 25) will provide a mount structure for the high-level directory and next-level subdirectory, which the network file system client module 23 can load into the directory tree 70. Following step 138, the network file system client module 23 can sequence to step 137 to initiate the remote access using the mount information it just loaded into the directory tree 70.
  • the network file system client module 23 When initiating an automount operation by the automounter module 25, the network file system client module 23 will provide a pointer to the directory tree 70. Accordingly, with reference to FIG. 6, the automounter module 25 will initially receive the directory tree pointer over the socket established in step 103 (FIG. 4), as well as the identification of the mount point (that is, the subdirectory) which is to be mounted (step 150). After receiving this information from the network file system client module 23, the automounter module 25 will initially perform a number of steps to verify that the mount point as provided by the network file system client module 23.
  • the automounter module 25 will parse the mount point provided by the network file system client module 23 to verify that the structure of the mount point identifier is valid and, if so, exchange one or more messages over the network with the remote computer system 11(n') (n' ⁇ n) or the server computer 12 which maintains the portion of the remote file system identified by the remote file system pointed to by the mount point identifier to perform the mount.
  • the automounter will first determine whether the options field 54(n) of the entry 51(n) of the automount master map file 50 contains the option "HOST" (step 151). As noted above, if the entry contains the option "HOST," each of the subdirectories identified in the subdirectory name fields 62(m) of the automounter subdirectory map file 60 contains a host name, that is, the identification of a remote computer system 11(n') (n' ⁇ n) or server computer 12, and a directory path.
  • the automounter module 25 will perform different operations to verify the validity of the mount point identifier's structure. Accordingly, if the automounter module 25 makes a positive determination in step 151, it will sequence to step 152 to parse the mount point identifier to identify the particular remote computer system 11(n') (n' ⁇ n) or server computer 12 as well as the remote path, that is directory name of the file system on the remote computer system 11(n') (n' ⁇ n) or server computer 12 which is to be mounted.
  • the automounter module 25 then verifies that the remote path is valid, which may require it to exchange messages with the remote computer system 11(n') (n' ⁇ n) or server computer 12 over the communication link 14 through the network interface 24 (step 153). If the automounter module 25 determines in step 153 that the path is invalid, it will return an error to the network file system client module 23.
  • step 151 if the automounter module 25 makes a negative determination in that step, the mount point identifier does not include a host name. In that case, the automounter module 25 will sequence to step 156 to parse the mount point identifier to verify that it conforms to the operating system's path- and filename structural requirements. If the automounter module 25 makes a negative determination in that step, it will sequence to step 157 to use the mount point identifier to identify an entry 51(n) in the automount master map 50 and an appropriate entry 61(m) in the automount subdirectory map file 60 to locate determine the appropriate remote file system identifier for the mount operation.
  • step 153 the automounter module 25 will sequence to step 160 to actually perform the mount operation in connection with the remote computer system 11(n') (n' ⁇ n) or server computer 12, and thereafter will return to the network file system client module 23.
  • the automounter module 25, using the network interface 24, will exchange messages over communication link 14 to enable the remote computer system 11(n') (n' ⁇ n) or the server computer 12 to perform the mount in a conventional manner and will update the mount structure pointed to by the directory tree 70.
  • step 161 the automounter module 25 will return to the network file system client module 23 (step 161), which, in turn, will perform the remote access operation as described above.
  • the automounter module will provide an appropriate message to the network file system client module 23, which, in turn, can initiate appropriate error recovery operations.
  • the invention provides a number of advantages. For example, it provides an arrangement for automounting remote file systems for use in connection with operating systems, such as the Microsoft MS-DOS and Windows operating systems, which require explicit identification of storage devices to identify a file system.
  • operating systems such as the Microsoft MS-DOS and Windows operating systems
  • device names can be automounted remote devices, it is readily apparent from device identifiers in the access requests ACC REQ which access requests from the application programs 20 are local requests and which are remote requests to be serviced by the network file system client module 23.
  • the invention provides an arrangement whereby, for example, entire file systems on remote computer systems 11(n') (n' ⁇ n) and/or the server computer 12 can be mounted and appear as subdirectories of one or more top-level directories for the computer system 11(n).
  • all or a selected subset of the file systems for remote computers system 11(n') (n' ⁇ n) and/or the server computer 12 can be mounted as a single automount drive.
  • MS-DOS and Windows for which the number of devices that a computer system 11(n) can access is limited (MS-DOS and Windows, for example, require that each device have a single alphabetical character "a,” "b,” etc., as their identifiers)
  • the remote devices that can be treated as subdirectories on a single device, namely, the virtual logical storage device, instead of separate devices.
  • the invention provides an arrangement by which a number of virtual logical storage devices, each having a unique identifier, can be used to identify the same physical mass storage subsystem or subsystems.
  • the individual virtual logical storage devices can have different current default paths and directories so that different parts of the same physical file system can be easily accessed using the default directories merely by selecting the appropriate virtual logical storage device.
  • virtual logical storage device file systems comprising remote file systems maintained on remote computer systems 11(n') (n' ⁇ n) or the server computer 12
  • the virtual logical storage device file systems may also include some or all of the local file system maintained by the computer system 11(n).
  • the process described above may be performed by a computer program running on a computer in the embodiment described.
  • a computer program can be recorded on a recording medium (for example a magnetic disc or tape, an optical disc or an electronic memory device, such as a ROM) in a way well known to those skilled in the art.
  • a suitable reading device such as a magnetic or optical disc drive
  • a signal is produced which causes a computer to perform the processes described.
  • the process may also be performed by electronic means.

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)
EP96309359A 1995-12-22 1996-12-20 Système et méthode pour monter automatiquement et accéder à des systèmes de fichiers éloignés dans Microsoft Windows dans un environnement en réseau Withdrawn EP0780778A3 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US577822 1995-12-22
US08/577,822 US5778384A (en) 1995-12-22 1995-12-22 System and method for automounting and accessing remote file systems in Microsoft Windows in a networking environment

Publications (2)

Publication Number Publication Date
EP0780778A2 true EP0780778A2 (fr) 1997-06-25
EP0780778A3 EP0780778A3 (fr) 1997-08-13

Family

ID=24310297

Family Applications (1)

Application Number Title Priority Date Filing Date
EP96309359A Withdrawn EP0780778A3 (fr) 1995-12-22 1996-12-20 Système et méthode pour monter automatiquement et accéder à des systèmes de fichiers éloignés dans Microsoft Windows dans un environnement en réseau

Country Status (3)

Country Link
US (1) US5778384A (fr)
EP (1) EP0780778A3 (fr)
JP (1) JPH1049423A (fr)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2320344A (en) * 1996-10-07 1998-06-17 Ibm Providing on-demand access to network services for Network Computers
EP0889400A1 (fr) * 1997-06-30 1999-01-07 Sun Microsystems, Inc. Système et méthode pour accès transparent et global aux dispositifs physics dans un système d'ordinateurs
ES2162537A1 (es) * 1998-07-29 2001-12-16 Univ Alcala Henares Terminal programable para la captura de datos.
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
EP1330738A4 (fr) * 2000-09-26 2006-05-17 Appstream Inc Procede et systeme pour executer des applications reseau continues
US7197570B2 (en) 1998-07-22 2007-03-27 Appstream Inc. System and method to send predicted application streamlets to a client device
EP1864230A4 (fr) * 2005-04-01 2009-04-08 Microsoft Corp Procede pour permettre a des developpeurs de trouver ou d'etendre facilement des emplacements bien connus sur un systeme
WO2009052465A3 (fr) * 2007-10-20 2009-06-25 Citrix Systems Inc Systèmes et procédés de redirection de dossier
US7606924B2 (en) 1998-07-22 2009-10-20 Symantec Corporation Method and apparatus for determining the order of streaming modules
EP1602037A4 (fr) * 2003-10-24 2010-02-03 Microsoft Corp Systeme et procede de gestion de donnees au moyen de listes statiques
EP2127171A4 (fr) * 2007-02-21 2012-02-01 Kid Group Llc Procédé et appareil pour fournir des jeux et un contenu
WO2014183917A1 (fr) * 2013-05-16 2014-11-20 Robert Bosch Gmbh Procédé permettant d'évaluer la consommation d'énergie d'une installation de chauffage ainsi que dispositif pour mettre en œuvre le procédé

Families Citing this family (97)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6279153B1 (en) * 1995-10-16 2001-08-21 Nec Corporation Multi-user flash ROM update
US5991542A (en) * 1996-09-13 1999-11-23 Apple Computer, Inc. Storage volume handling system which utilizes disk images
US5991763A (en) * 1996-10-29 1999-11-23 Sun Microsystems, Inc. Method and apparatus for embedding concatenated data files into object files during runtime in a virtual file system
WO1998024025A1 (fr) 1996-11-27 1998-06-04 1Vision Software, L.L.C. Repertoire de fichiers et systeme d'exploration correspondant
DE19708755A1 (de) * 1997-03-04 1998-09-17 Michael Tasler Flexible Schnittstelle
US6041376A (en) * 1997-04-24 2000-03-21 Sequent Computer Systems, Inc. Distributed shared memory system having a first node that prevents other nodes from accessing requested data until a processor on the first node controls the requested data
US6081807A (en) * 1997-06-13 2000-06-27 Compaq Computer Corporation Method and apparatus for interfacing with a stateless network file system server
US5991777A (en) * 1997-09-19 1999-11-23 Microsoft Corporation System and method for performing defined actions when grafting the name space of one storage medium into the name space of another storage medium
US6125373A (en) * 1997-09-19 2000-09-26 Microsoft Corporation Identifying a driver that is an owner of an active mount point
US6029168A (en) * 1998-01-23 2000-02-22 Tricord Systems, Inc. Decentralized file mapping in a striped network file system in a distributed computing environment
US6446206B1 (en) 1998-04-01 2002-09-03 Microsoft Corporation Method and system for access control of a message queue
US6529932B1 (en) 1998-04-01 2003-03-04 Microsoft Corporation Method and system for distributed transaction processing with asynchronous message delivery
US6205498B1 (en) * 1998-04-01 2001-03-20 Microsoft Corporation Method and system for message transfer session management
US6678726B1 (en) 1998-04-02 2004-01-13 Microsoft Corporation Method and apparatus for automatically determining topology information for a computer within a message queuing network
US6275912B1 (en) 1998-06-30 2001-08-14 Microsoft Corporation Method and system for storing data items to a storage device
US6202089B1 (en) 1998-06-30 2001-03-13 Microsoft Corporation Method for configuring at runtime, identifying and using a plurality of remote procedure call endpoints on a single server process
US6256634B1 (en) 1998-06-30 2001-07-03 Microsoft Corporation Method and system for purging tombstones for deleted data items in a replicated database
US6848108B1 (en) * 1998-06-30 2005-01-25 Microsoft Corporation Method and apparatus for creating, sending, and using self-descriptive objects as messages over a message queuing network
US9361243B2 (en) 1998-07-31 2016-06-07 Kom Networks Inc. Method and system for providing restricted access to a storage medium
US7392234B2 (en) * 1999-05-18 2008-06-24 Kom, Inc. Method and system for electronic file lifecycle management
US6976083B1 (en) * 1999-02-19 2005-12-13 International Business Machines Corporation Apparatus for providing direct data processing access using a queued direct input-output device
US6845395B1 (en) * 1999-06-30 2005-01-18 Emc Corporation Method and apparatus for identifying network devices on a storage network
US6389433B1 (en) * 1999-07-16 2002-05-14 Microsoft Corporation Method and system for automatically merging files into a single instance store
US6513051B1 (en) 1999-07-16 2003-01-28 Microsoft Corporation Method and system for backing up and restoring files stored in a single instance store
US6834386B1 (en) * 1999-07-16 2004-12-21 Microsoft Corporation Method and system for regulating background tasks using performance measurements
US6477544B1 (en) 1999-07-16 2002-11-05 Microsoft Corporation Single instance store for file systems
US6594675B1 (en) * 1999-08-26 2003-07-15 International Business Machines Corporation Method, system for using file name to access application program where a logical file system processes pathname to determine whether the request is a file on storage device or operation for application program
US6895591B1 (en) * 1999-10-18 2005-05-17 Unisys Corporation Virtual file system and method
US6453301B1 (en) * 2000-02-23 2002-09-17 Sony Corporation Method of using personal device with internal biometric in conducting transactions over a network
US6554444B2 (en) 2000-03-13 2003-04-29 Kansai Technology Licensing Organization Co., Ltd. Gazing point illuminating device
US7418439B2 (en) * 2000-03-17 2008-08-26 Twin Peaks Software, Inc. Mirror file system
WO2001071478A2 (fr) * 2000-03-22 2001-09-27 Sony Electronics Inc Interface utilisateur de saisie de donnees
US20020026419A1 (en) * 2000-08-24 2002-02-28 Sony Electronics, Inc. Apparatus and method for populating a portable smart device
US6850959B1 (en) 2000-10-26 2005-02-01 Microsoft Corporation Method and system for transparently extending non-volatile storage
JP2002135676A (ja) * 2000-10-27 2002-05-10 Canon Inc テレビジョン信号受信装置、その処理方法及び記録媒体
US7251633B2 (en) * 2000-12-11 2007-07-31 Sony Corporation Method or system for executing deferred transactions
US7765163B2 (en) * 2000-12-12 2010-07-27 Sony Corporation System and method for conducting secure transactions over a network
US20020124190A1 (en) * 2001-03-01 2002-09-05 Brian Siegel Method and system for restricted biometric access to content of packaged media
US20020183984A1 (en) * 2001-06-05 2002-12-05 Yining Deng Modular intelligent multimedia analysis system
JP2003131924A (ja) * 2001-10-19 2003-05-09 Fujitsu Ltd リモートアクセスプログラム、リモートアクセス要求処理プログラム、およびクライアントコンピュータ
US7024427B2 (en) * 2001-12-19 2006-04-04 Emc Corporation Virtual file system
US20030200314A1 (en) * 2002-04-19 2003-10-23 Gateway, Inc. Remote access to aggregated grouping of distributed content
US6799226B1 (en) * 2002-07-23 2004-09-28 Apple Computer, Inc. Hot unpluggable media storage device
US6947940B2 (en) * 2002-07-30 2005-09-20 International Business Machines Corporation Uniform name space referrals with location independence
US7814131B1 (en) * 2004-02-02 2010-10-12 Network Appliance, Inc. Aliasing of exported paths in a storage system
US7428556B2 (en) * 2004-06-17 2008-09-23 International Business Machines Corporation Method and system for identifying automounted file system resources
US7444359B2 (en) * 2004-06-17 2008-10-28 International Business Machines Corporation Method and system for checking availability of automounted file systems
US7441042B1 (en) * 2004-08-25 2008-10-21 Symanetc Corporation System and method for correlating network traffic and corresponding file input/output traffic
FI119664B (fi) * 2004-12-08 2009-01-30 Open Invention Network Llc Menetelmä elektronisissa laitteissa oleviin tiedostoihin pääsemiseksi
US8290901B2 (en) * 2005-03-07 2012-10-16 Novell, Inc. Techniques for remote resource mounting
US8032705B2 (en) * 2005-05-17 2011-10-04 Kid Group Llc Method and apparatus for providing games and content
US20070055740A1 (en) * 2005-08-23 2007-03-08 Luciani Luis E System and method for interacting with a remote computer
US7681053B2 (en) * 2005-11-29 2010-03-16 International Business Machines Corporation Thermal throttle control with minimal impact to interrupt latency
US20070124618A1 (en) * 2005-11-29 2007-05-31 Aguilar Maximino Jr Optimizing power and performance using software and hardware thermal profiles
US7386414B2 (en) * 2005-11-29 2008-06-10 International Business Machines Corporation Generation of hardware thermal profiles for a set of processors
US7395174B2 (en) * 2005-11-29 2008-07-01 International Business Machines Corporation Generation of software thermal profiles executed on a set of processors using thermal sampling
US7376532B2 (en) * 2005-11-29 2008-05-20 International Business Machines Corporation Maximal temperature logging
US7603576B2 (en) * 2005-11-29 2009-10-13 International Business Machines Corporation Hysteresis in thermal throttling
US7512513B2 (en) * 2005-11-29 2009-03-31 International Business Machines Corporation Thermal throttling control for testing of real-time software
US7512530B2 (en) * 2005-11-29 2009-03-31 International Business Machines Corporation Generation of software thermal profiles for applications in a simulated environment
US7698089B2 (en) * 2005-11-29 2010-04-13 International Business Machines Corporation Generation of software thermal profiles executed on a set of processors using processor activity
US7480586B2 (en) * 2005-11-29 2009-01-20 International Business Machines Corporation Thermal interrupt generation
US7490017B2 (en) * 2005-11-29 2009-02-10 International Business Machines Corporation Analytical generation of software thermal profiles
US7721128B2 (en) * 2005-11-29 2010-05-18 International Business Machines Corporation Implementation of thermal throttling logic
US7460932B2 (en) * 2005-11-29 2008-12-02 International Business Machines Corporation Support of deep power savings mode and partial good in a thermal management system
US7848901B2 (en) * 2005-11-29 2010-12-07 International Business Machines Corporation Tracing thermal data via performance monitoring
US20070162510A1 (en) * 2005-12-30 2007-07-12 Microsoft Corporation Delayed file virtualization
JP4912026B2 (ja) * 2006-04-27 2012-04-04 キヤノン株式会社 情報処理装置、情報処理方法
US8037893B2 (en) * 2006-05-03 2011-10-18 International Business Machines Corporation Optimizing thermal performance using thermal flow analysis
US7596430B2 (en) * 2006-05-03 2009-09-29 International Business Machines Corporation Selection of processor cores for optimal thermal performance
US7552346B2 (en) * 2006-05-03 2009-06-23 International Business Machines Corporation Dynamically adapting software for reducing a thermal state of a processor core based on its thermal index
US8433732B2 (en) * 2006-08-18 2013-04-30 Falconstor, Inc. System and method for storing data and accessing stored data
US7757159B1 (en) 2007-01-31 2010-07-13 Yazaki North America, Inc. Method of determining the projected area of a 2-D view of a component
US8027798B2 (en) 2007-11-08 2011-09-27 International Business Machines Corporation Digital thermal sensor test implementation without using main core voltage supply
US8145674B2 (en) * 2007-11-26 2012-03-27 International Business Machines Corporation Structure based storage, query, update and transfer of tree-based documents
US8176084B2 (en) * 2007-11-26 2012-05-08 International Business Machines Corporation Structure based storage, query, update and transfer of tree-based documents
JP2009251791A (ja) * 2008-04-03 2009-10-29 Nec Corp 分散ファイルシステム、データ書き込み方法、及びプログラム
US20100042719A1 (en) * 2008-08-12 2010-02-18 Junji Kinoshita Content access to virtual machine resource
US8793339B2 (en) * 2008-08-29 2014-07-29 Red Hat, Inc. Facilitating client server interaction
US8793398B2 (en) * 2008-08-29 2014-07-29 Red Hat, Inc. Facilitating client server interaction
US8326802B2 (en) * 2009-06-11 2012-12-04 International Business Machines Corporation File system location verification using a sentinel
US9454441B2 (en) 2010-04-19 2016-09-27 Microsoft Technology Licensing, Llc Data layout for recovery and durability
US10318477B2 (en) * 2010-05-26 2019-06-11 Red Hat, Inc. Managing and archiving system and application log files
MY175092A (en) * 2011-01-21 2020-06-05 Interdigital Ce Patent Holdings Method for backward-compatible aggregate file system operation performance improvement. and respective apparatus
US9778856B2 (en) * 2012-08-30 2017-10-03 Microsoft Technology Licensing, Llc Block-level access to parallel storage
US8924443B2 (en) * 2012-10-05 2014-12-30 Gary Robin Maze Document management systems and methods
US11422907B2 (en) 2013-08-19 2022-08-23 Microsoft Technology Licensing, Llc Disconnected operation for systems utilizing cloud storage
US9811531B2 (en) 2013-08-26 2017-11-07 Vmware, Inc. Scalable distributed storage architecture
US10747475B2 (en) 2013-08-26 2020-08-18 Vmware, Inc. Virtual disk blueprints for a virtualized storage area network, wherein virtual disk objects are created from local physical storage of host computers that are running multiple virtual machines
US11016820B2 (en) 2013-08-26 2021-05-25 Vmware, Inc. Load balancing of resources
US9887924B2 (en) 2013-08-26 2018-02-06 Vmware, Inc. Distributed policy-based provisioning and enforcement for quality of service
US9798631B2 (en) 2014-02-04 2017-10-24 Microsoft Technology Licensing, Llc Block storage by decoupling ordering from durability
CN106576078B (zh) 2014-08-26 2020-06-23 Ctera网络有限责任公司 用于在云存储系统中路由数据流的方法和系统
US9936023B2 (en) * 2015-09-04 2018-04-03 Dell Products L.P. System and method to attach a local file system to a remote disk stack
CN106933872A (zh) * 2015-12-30 2017-07-07 阿里巴巴集团控股有限公司 一种通过传统文件系统接口访问云存储服务的方法及装置
JP7155836B2 (ja) * 2018-10-03 2022-10-19 京セラドキュメントソリューションズ株式会社 情報処理システム及び情報処理方法
CN111061692A (zh) * 2018-10-16 2020-04-24 阿里巴巴集团控股有限公司 一种数据访问方法、设备、系统及存储介质

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5247638A (en) * 1990-06-18 1993-09-21 Storage Technology Corporation Apparatus for compressing data in a dynamically mapped virtual data storage subsystem
US5627996A (en) * 1992-08-19 1997-05-06 At&T Method and apparatus for accessing the same computer file using different file name formats
US5581724A (en) * 1992-10-19 1996-12-03 Storage Technology Corporation Dynamically mapped data storage subsystem having multiple open destage cylinders and method of managing that subsystem
US5537585A (en) * 1994-02-25 1996-07-16 Avail Systems Corporation Data storage management for network interconnected processors
US5689701A (en) * 1994-12-14 1997-11-18 International Business Machines Corporation System and method for providing compatibility between distributed file system namespaces and operating system pathname syntax

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6757729B1 (en) 1996-10-07 2004-06-29 International Business Machines Corporation Virtual environment manager for network computers
GB2320344B (en) * 1996-10-07 2001-05-30 Ibm Virtual environment manager for network computers
GB2320344A (en) * 1996-10-07 1998-06-17 Ibm Providing on-demand access to network services for Network Computers
CN1085917C (zh) * 1996-10-07 2002-05-29 国际商业机器公司 为网络上运行的应用程序提供对网络服务的访问的方法
EP0889400A1 (fr) * 1997-06-30 1999-01-07 Sun Microsystems, Inc. Système et méthode pour accès transparent et global aux dispositifs physics dans un système d'ordinateurs
US6163806A (en) * 1997-06-30 2000-12-19 Sun Microsystems, Inc. System and method for transparent, global access to physical devices on a computer cluster
US7197570B2 (en) 1998-07-22 2007-03-27 Appstream Inc. System and method to send predicted application streamlets to a client device
US7606924B2 (en) 1998-07-22 2009-10-20 Symantec Corporation Method and apparatus for determining the order of streaming modules
ES2162537A1 (es) * 1998-07-29 2001-12-16 Univ Alcala Henares Terminal programable para la captura de datos.
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
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
US8321483B2 (en) 2000-08-18 2012-11-27 Apple Inc. Method and system for seamlessly accessing remotely stored files
EP1330738A4 (fr) * 2000-09-26 2006-05-17 Appstream Inc Procede et systeme pour executer des applications reseau continues
EP1602037A4 (fr) * 2003-10-24 2010-02-03 Microsoft Corp Systeme et procede de gestion de donnees au moyen de listes statiques
EP1864230A4 (fr) * 2005-04-01 2009-04-08 Microsoft Corp Procede pour permettre a des developpeurs de trouver ou d'etendre facilement des emplacements bien connus sur un systeme
EP2127171A4 (fr) * 2007-02-21 2012-02-01 Kid Group Llc Procédé et appareil pour fournir des jeux et un contenu
WO2009052465A3 (fr) * 2007-10-20 2009-06-25 Citrix Systems Inc Systèmes et procédés de redirection de dossier
US8782021B2 (en) 2007-10-20 2014-07-15 Citrix Systems, Inc. Systems and methods for folder redirection
US9798730B2 (en) 2007-10-20 2017-10-24 Citrix Systems, Inc. Systems and methods for folder redirection
WO2014183917A1 (fr) * 2013-05-16 2014-11-20 Robert Bosch Gmbh Procédé permettant d'évaluer la consommation d'énergie d'une installation de chauffage ainsi que dispositif pour mettre en œuvre le procédé

Also Published As

Publication number Publication date
EP0780778A3 (fr) 1997-08-13
US5778384A (en) 1998-07-07
JPH1049423A (ja) 1998-02-20

Similar Documents

Publication Publication Date Title
US5778384A (en) System and method for automounting and accessing remote file systems in Microsoft Windows in a networking environment
US7035931B1 (en) Volume location service for a distributed file system
US6038379A (en) Data backup and restore system for a computer network having generic remote file system agents for providing backup and restore operations
US7676526B1 (en) System, method and computer program product for multi-level file-sharing by concurrent users
US5465365A (en) Apparatus and methods for making a portion of a first name space available as a portion of a second name space
JP3968242B2 (ja) 共有データにアクセスするための方法と装置
EP1039380B1 (fr) Procédé pour l'échange de données entre une base de données de système Java et un répertoire LDAP
US7530115B2 (en) Access to content addressable data over a network
US5751962A (en) Object-based systems management of computer networks
US7003641B2 (en) Logical view with granular access to exchange data managed by a modular data and storage management system
EP0838056B1 (fr) Procede, appareil et medium electronique de memorisation de gestion de demandes adressees a de multiples serveurs et de reponses collationnees
US5740362A (en) Management of network distributed agents in a distributed computing environment
US5758334A (en) File system remount operation with selectable access modes that saves knowledge of the volume path and does not interrupt an executing process upon changing modes
US7330862B1 (en) Zero copy write datapath
US7475199B1 (en) Scalable network file system
US20020138501A1 (en) Method and apparatus to improve file management
US20050216532A1 (en) System and method for file migration
JPS62119664A (ja) コンピユ−タ　ネツトワ−ク内での遠隔プロセス実行法
US8627446B1 (en) Federating data between groups of servers
WO2004015522A2 (fr) Virtualisation du stockage par disposition en couches d'objets sur disque virtuel dans un systeme de fichier
JPH04230567A (ja) 計算システムのための分散型構成プロフィル
JP2003216474A (ja) ネットワークストレージ仮想化方法
US8762434B1 (en) Aliasing of exported paths in a storage system
US7634453B1 (en) Distributed file data location
US7293030B2 (en) Methods, functional data, and systems to represent a storage environment

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): DE FR GB IT NL

PUAL Search report despatched

Free format text: ORIGINAL CODE: 0009013

AK Designated contracting states

Kind code of ref document: A3

Designated state(s): DE FR GB IT NL

17P Request for examination filed

Effective date: 19980212

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20030604