Method and system for computer file management, including file migration, special handling, and associating extended attributes with files

• US 5,991,753 A
• Filed: 06/14/1995
• Issued: 11/23/1999
• Est. Priority Date: 06/16/1993
• Status: Expired due to Term

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: Lachman Technology, Inc.
• Inventors: Wilde, Michael J.
• Primary Examiner(s): Choules, Jack M.
• Application Number:
  US08/490,137
• Time in Patent Office: 1,623 Days
• Field of Search: 395/620, 395/621, 395/488, 395/489, 395/444, 707/1, 707/2, 707/204, 707/205, 711/161, 711/162, 711/154
• US Class Current: 1/1
• CPC Class Codes: G06F 16/10 File systems; File servers
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99953 Recoverability

Abstract

A file management system and method for implementing special handling of files, useful for such applications as migration, compression, encryption, and logging access to files. A layer is superimposed between an underlying file system and programs'"'"' requests to access files. The layer initiates special handling in response to a file'"'"'s normal attributes or information in the contents of the file and then passes the request to the underlying file system for normal proceeding. In the preferred embodiment, a file is recognized as a representation of a migrated file if the length attribute has a predetermined value and the file contains a unique pattern of bits.

Claims

1. A file management system, comprising,

a layer that intercepts at least one code path by which a program requests access to a first file from an underlying file system;

a file management procedure that performs special handling on a file;

a branch in said layer that branches to a first call in said layer to said file management procedure based on a decision made by examining at least one normal attribute of the file referenced in the intercepted access request by examining the file itself;

a second call in said layer to said accessing procedure of said underlying file system.

2. The file management system of claim 1, wherein said file management procedure comprises a procedure for reloading a migrated file.

3. The file management system of claim 1, wherein said file management procedure comprises a decompression procedure.

4. The file management system of claim 1, wherein said file management procedure comprises a decryption procedure.

5. The file management system of claim 1, wherein said at least one normal attribute comprises the length of the file.

6. The file management system of claim 1, wherein said at least one normal attribute comprises a timestamp for the file.

7. The file management system of claim 1, wherein said at least one normal attribute comprises an owner identification.

8. The file management system of claim 1, wherein said branch branches to said first call based on a decision made by examining the contents of the file.

9. A file management method comprising the steps of,

intercepting at least one code path by which a program requests access to a first file from an underlying file system;

examining at least one normal attribute of the file that is referenced by said request by examining the file itself;

responding to said examining step by conditionally calling a file management procedure;

calling said accessing procedure of said underlying file system.

10. The method of claim 9, wherein said examining step comprises determining the length of a data block of the file.

11. The method of claim 9, wherein said responding step calls said file management procedure only if said normal attribute has a preselected value.

12. The method of claim 9, wherein said at least one normal attribute comprises a timestamp for the file.

13. The method of claim 9, wherein said at least one normal attribute comprises the length of the file.

14. The method of claim 13, wherein said preselected value of said attribute is the length of a data block of said file.

15. The method of claim 13, wherein said examining step further comprises determining whether the file contains a unique pattern of bits.

16. The method of claim 12, wherein said file management procedure comprises a procedure for reloading a migrated file.

17. The method of claim 16, wherein said reloading procedure copies a migrated file from a first repository to a second repository and wherein said first and second repositories are both local to the same computer.

18. The method of claim 16, wherein said reloading procedure copies a migrated file from a first repository to a second repository and wherein said second repository is local to a computer and said first repository is accessible to said computer via a remote connection.

19. A file migration method comprising the steps of,

examining at least one normal attribute of a first file by examining the file itself;

and

responding to said examining step by calling a file reloading procedure only if each of said at least one normal attributes has a predetermined value;

wherein said file reloading procedure uses information stored in the first file to reload a migrated file corresponding to the file.

20. The file method of claim 19 wherein said at least one normal attribute comprises length.

21. A file management system comprising:

means for intercepting at least one code path by which a program requests access to a first file from an underlying file system;

means for examining at least one normal attribute of the file that is referenced by said request by examining the file itself;

means for responding to said examining step and for conditionally calling a file management procedure;

means for calling said accessing procedure of said underlying file system.

22. A system for storing and retrieving information, comprising:

a computer having a first data storage repository and access to a second data storage repository;

a file system accessible to said computer that includes a procedure for accessing files stored on said first repository;

said computer further having a layer that intercepts calls to said file system'"'"'s procedure for accessing files;

a first file stored on said second repository; and

a second file stored on said first repository that has some of the attributes of said first file and at least one normal attribute of the file itself signifying that said second file contains information identifying the location of said first file.

23. The system of claim 22 wherein said layer comprises a procedure for determining whether an intercepted file access request requires access to data contained in said first file and not in said second file.

24. A method of migrating files, comprising the steps of:

copying the contents of an original file from a first repository to a second repository and

transforming said original file to an alternate representation comprising a file having a last data block of a predetermined size and including therein information identifying the location of said copy.

25. The method of claim 24, wherein said transformed file further comprises a residency map.

26. The method of claim 24, wherein said transformed file further comprises information identifying at least one extended attribute of said original file.

27. The method of claim 24, wherein said transforming step further comprises the steps of:

storing in said transformed file a value indicative of the size of said original file before transformation; and

preserving the rest of the attributes of said original file.

28. The method of claim 24, wherein said transforming step further comprises storing in said transforming file a unique pattern of bits.

29. The method of claim 24, further comprising,

reloading onto said first repository at least a portion of said copy of said file.

30. The method of claim 29, further comprising,

entering in a database a key identifying said reloaded file and a value identifying the location of said file on said second repository,

deleting said transformed file, and

transferring attributes of said transformed file to attributes of said reloaded file.

31. The method of claim 29, wherein said reloading step occurs in response to a request to read a portion of said original file, said portion not contained in said truncated file.