System for accessing extended object attribute (EA) data through file name or EA handle linkages in path tables

• US 5,367,671 A
• Filed: 09/25/1990
• Issued: 11/22/1994
• Est. Priority Date: 09/25/1990
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Feigenbaum, Barry A., Miro, Felix
• Primary Examiner(s): Lee, Thomas C.
• Assistant Examiner(s): WANG, PETER
• Application Number:
  US07/587,813
• Time in Patent Office: 1,519 Days
• Field of Search: 395/600, 395/700, 395/650
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: Y10S 707/99931 Database or file accessing

Abstract

An adaptation of a computer operating system manages storage of EA (extended attribute) data in association with object names, the latter representing paths in direct access storage devices (e.g. directories and sub-directories), and data files stored in such paths. EA data stored in association with a data file name can be accessed either jointly with or separate from the respective data file. EA data comprises one or more variable length sets of bytes stored in disk drive sectors assigned by the operating system. The location of each set is determinable by means of an EA handle that is stored in a path table containing the respective object name. Function calls from application programs to the operating system use either a file name or EA handle to access EA data. Function calls specifying only an EA handle allow EA information to be stored, modified or read without specific association to or linkage with file data. Function calls specifying a file name allow EA information to be stored, modified or read either separately from or jointly with associated file data ("jointly with" meaning for instance that a call to copy or delete a named file could be used to effect copying or deletion of both file data and associated EA data).

Claims

1. For a computer system containing an operating system and a memory subsystem, and having one or more direct access storage devices attached thereto, an arrangement for adapting said operating system to store, modify and read extended attribute (EA) data associated with named objects contained in said storage devices;

said arrangement comprising;

one or more path tables under exclusive control of said operating system tables being stored in said storage devices, and in said memory subsystem when said computer system is communicating with the respective storage device;

each said path table containing locations therein reserved for storing names of objects associated with the respective storage device and EA handle information for locating EA data stored in association with respective said objects;

first means under exclusive control of said operating system, said first means being responsive to first function calls, each designating a storage device and an EA handle, for causing EA data to be transferred to or from storage locations in respectively designated storage devices;

each said storage location being found only by means of the EA handle designated in the respective first function call, and

second means under exclusive control of said operating system, said second means being responsive to second function calls, each designating a device and an object name, for causing EA data associated with respectively designated object names to be transferred to or from storage locations in designated devices;

wherein each said storage location is determined by referring to a said path table containing the respective object name and using an associated EA handle stored in said path table for locating a storage position in the respectively designated device relative to which said EA data is to be transferred wherein said named objects include directory and subdirectory paths in said devices, and said file data stored in said paths, and wherein each said path table is associated with a single path in a single device and contains spaces for storing entries representing the respective path and any data files stored in that path;

each said entry space containing a position therein reserved for optionally storing said EA handle when EA data is stored in the respective device in association with the respective object name represented by the entry.

2. The arrangement of claim 1 wherein said second means comprises:

means responsive to object names assigned to sets of file data, which object names are designated in said second function calls, for jointly handling transfers of file data sets and EA data relative to devices designated in respective second calls.

3. The arrangement of claim 1 wherein EA data associated with a single said device and a single said object name includes plural sets of EA data stored at a plurality of discretely separate locations in the associated device.

4. The arrangement of claim 3 including:

a master table of EA pointers associated with each said storage device, each EA pointer in each said master table pointing to the storage location in the respective device of a single set of EA data;

wherein;

each said EA handle points to a single EA pointer in one of said master tables, and is thereby useful by said second means for locating a storage position in the respective device allocated for handling of a single respective set of EA data.

5. A method of adapting a computer operating system to manage storage, modification and retrieval of extended attribute (EA) data associated with named objects, wherein said operating system is exclusively responsible for directing storage of and access to information associated with said EA data and named objects in direct access storage devices:

said method comprising;

in response to requests from programs using said operating system, storing EA data in said direct access storage devices and storing EA handle functions in the same devices in path tables accessible exclusively to said operating system;

said EA handle functions being useful by said operating system for locating storage positions of respective said EA data;

each said EA handle function stored in a said path table being stored in association with an object name;

in response to first function calls from said programs using said operating system, each first function call designating a device and an object name, directing access to a respectively designated device for reading, writing or modifying EA data;

said access being implemented by using a respectively designated object name to locate a path table containing an EA handle associated with the designated name, and by using said EA handle in said located path table to determine a storage location in said device at which to read, write or modify EA data associated with the respectively designated object name; and

in response to second function calls from said programs using said operating system, each said second function call designating a storage device and an EA handle, directing access to a said designated storage device for reading, writing or modifying EA data at a location in the respectively designated device determined only by means of said respectively designated EA handle;

i.e. without reference to any said associated object name or path table wherein some of said object names represent directory and subdirectory paths on respective said devices and other said object names represent file data stored in said paths; and

each of said path tables contains an entry including a name of a said directory or subdirectory path, and zero, one, or more other entries containing names representing zero, one, or more associated sets of file data stored in the path defined by the respective directory or subdirectory name entry.

6. The method of claim 5 including:

in conjunction with said step of reading or modifying EA data, and in response to some of said program requests, selectively reading or modifying file data associated with object names designated in said some requests.

7. The method of claim 5 wherein said step of storing said EA data and EA handles includes:

storing a plurality of discrete sets of EA data associated with a single object name, at various different locations in a said storage device;

storing a single EA handle associated with said single object name in a path table entry assigned to said object name; and

establishing a predetermined link between said single EA handle and all of EA data sets allowing for location of any of said data sets by means of said single EA handle.

8. The method of claim 7 wherein said step of establishing said predetermined link comprises:

relative to each storage device containing stored EA data, maintaining a master table of pointers to said EA data, said list structured so that it begins at a predetermined location associatable with all EA handles, and contains linked pointer entries designating storage locations of individual said EA data sets associated with any of said object names.

9. For a computer system containing an operating system and a memory subsystem, and having one or more direct access storage devices attached thereto, an arrangement for adapting said operating system to exclusively direct access to said direct access storage devices for managing information objects in association with specific object names and for managing storage of and access to extended attribute (EA) data in association with said specific object names;

said information objects including directory and subdirectory paths in said direct access storage devices, and data files stored in said paths;

said arrangement comprising;

one or more path tables Under exclusive control of said operating system, said path tables being stored in said direct access storage devices, wherein each said path table is associated with a single path in a single device and in said memory subsystem when said computer system is communicating with the respective storage device;

each said path table operating system, and each said table containing locations therein reserved for storing names of information objects associated with the respective device and EA handle information useful as pointers for locating EA data associated with respective said names;

first means under exclusive control of said operating system, said first means being responsive to first function calls, each designating a storage device and an EA handle, for causing EA data to be transferred to or from storage locations in respectively designated storage devices;

wherein said first means operates to find said storage locations for said EA data transfers only by means of the EA handles designated in the respective first function calls;

i.e. without reference to any said path tables; and

second means responsive to second function calls, each designating a device and an object name, for linking the designated object names to EA handles via said path tables, and, using said linked EA handles as pointers, causing EA data to be transferred to or from designated devices at locations indirectly indicating said linked EA handles;

said second means including;

means responsive to object names assigned to said data files, which object names are designated in said second function calls, for jointly handling transfers of associated data files and EA data relative to devices designated in respective said second function calls.

10. The arrangement of claim 9 wherein EA data associated with a single said device and a single said object name includes plural sets of EA data stored at a plurality of discretely separate locations in the associated device;

and said arrangement includes;

a master table of EA pointers associated with each said storage device, and stored in said memory subsystem when the system is communicating with the respective storage device;

each EA pointer in each said master table pointing to a storage location in the respective device at which a single said set of EA data is stored;

said arrangement being characterized in that;

each said EA handle points to a single EA pointer in a single said master table, and each EA pointer in each master table is thereby useful by said second means for locating a storage position in the respective device at which a single associated set of EA data is stored.