US5668958A
Expired / Lapsed
US
⏱️ 0.0 years remaining
Heterogeneous filing system with common API and reconciled file management rules
Assignee: International Business Machines Corp
•
Filing: 1995-09-12
•
Granted: 1997-09-16
•
Expires: 2015-09-12
Abstract
Abstract A computer system manages first and second different file systems. The system comprises first and second, different file managers having first and second different APIs for the first and second file systems, respectively. The system also comprises a hybrid file manager for managing the second file system based on requests made using the first API. The hybrid manager applies rules from both APIs to control atomicity of requests, access concurrency, and data consistency rules. The hybrid rules prevent violation of the rules of either API.
Inventors
- 👤 Edward Joseph Bendert
- 👤 Robert Bradley Bennett
- 👤 Eve Suzanne Berman
- 👤 Susan Marie Farrell
- 👤 Eugene Johnson
- 👤 Robert Michael Nugent
- 👤 Mary Ellen Vendryes
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-02 00:33
CPC Classifications
G; G06; G06F; G06F16/00; G06F16/10
Claims Analysis
Total Claims: 28
Claim 1
Independent Claim
99 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively; and hybrid means for controlling atomicity of said second file system based on requests made using said first API, at least one request permitted under said second API for access to said second file system not being permitted with concurrent access to said second file system using said first API such that said one request does not violate file management rules of said second API.
Claim 2
Dependent Claim
99 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively; and hybrid means for controlling atomicity of said second file system based on requests made using said first API, at least one request permitted under said second API for access to said second file system not being permitted with concurrent access to said second file system using said first API such that said one request does not violate file management rules of said second API.
Claim 3
Dependent Claim
22 words
A computer system as set forth in claim 1 wherein said plurality of updates are made to a respective plurality of files.
Claim 4
Dependent Claim
71 words
A computer system as set forth in claim 2 wherein said hybrid means supports a plurality of explicit update requests to a same file and execution of said plurality of update requests before said combined close and commit request but does not support another plurality of explicit update requests to a plurality of files and execution of said other plurality of explicit update requests before a combined close and commit request.
Claim 5
Dependent Claim
63 words
A computer system as set forth in claim 1 wherein when said second file system is open for write from said second API said second API permits an open for read from said second API but when said second file system is open for write from said first API, said hybrid means does not permit an open for read from said second API.
Claim 6
Dependent Claim
74 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively; and hybrid means for managing said second file system based on requests made using said first API, said hybrid means applying rules from both APIs to control access concurrency, said rules being the more restrictive rules of said second API.
Claim 7
Dependent Claim
74 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively; and hybrid means for managing said second file system based on requests made using said first API, said hybrid means applying rules from both APIs to control access concurrency, said rules being the more restrictive rules of said second API.
Claim 8
Dependent Claim
65 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively; and hybrid means for controlling data change consistency of said second file based on requests made using said first API, said requests not violating file management rules of said second API.
Claim 9
Dependent Claim
65 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively; and hybrid means for controlling data change consistency of said second file based on requests made using said first API, said requests not violating file management rules of said second API.
Claim 10
Dependent Claim
165 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively, said first API supporting an explicit commit request following an explicit close request and execution of said close request and a combined close and commit request following an explicit update request and execution of said update request, said first API not committing updates pursuant to an explicit update request, said second API, in response to an explicit update request, executing said update request and automatically committing resultants updates if successful; and hybrid means for managing said second file system based on requests made using said first API, said hybrid means supporting an explicit, combined close and commit request following an explicit update request and execution of said update request and supporting an explicit rollback request following an explicit update request but not supporting an explicit close request without combined commit request.
Claim 11
Dependent Claim
165 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively, said first API supporting an explicit commit request following an explicit close request and execution of said close request and a combined close and commit request following an explicit update request and execution of said update request, said first API not committing updates pursuant to an explicit update request, said second API, in response to an explicit update request, executing said update request and automatically committing resultants updates if successful; and hybrid means for managing said second file system based on requests made using said first API, said hybrid means supporting an explicit, combined close and commit request following an explicit update request and execution of said update request and supporting an explicit rollback request following an explicit update request but not supporting an explicit close request without combined commit request.
Claim 12
Dependent Claim
45 words
A computer system as set forth in claim 7 wherein said first API and said first file manager support a plurality of explicit update requests and execution of said plurality of update requests followed by an explicit, commit request for said plurality of updates collectively.
Claim 13
Dependent Claim
125 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively, said first API does not present committed updates to a concurrent reader until after said concurrent reader closes the respective file and reopens said respective file, said second API presents updates to a concurrent reader after said updates are committed and before said concurrent reader closes the respective file; and hybrid means for managing said second file based on requests made using said first API, said hybrid means does not present committed updates to a concurrent reader until after said concurrent reader closes the respective file and reopens said respective file.
Claim 14
Dependent Claim
125 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively, said first API does not present committed updates to a concurrent reader until after said concurrent reader closes the respective file and reopens said respective file, said second API presents updates to a concurrent reader after said updates are committed and before said concurrent reader closes the respective file; and hybrid means for managing said second file based on requests made using said first API, said hybrid means does not present committed updates to a concurrent reader until after said concurrent reader closes the respective file and reopens said respective file.
Claim 15
Dependent Claim
55 words
A computer system as set forth in claim 9 wherein when said second file system is open for write from said first API, said hybrid means does not permit an open for read from said second API, whereby there are no readers from said second API currently available to read updates from said first API.
Claim 16
Dependent Claim
89 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively, said first API serializing requests to open for write at a file level, said second API permitting concurrent opens for write at a file level; and hybrid means for managing said second file system based on requests made using said first API, said hybrid means serializing requests to open for write at a file level.
Claim 17
Dependent Claim
89 words
A computer system for managing first and second different file systems, said system comprising: first and second different file managers having first and second different APIs for said first and second file systems, respectively, said first API serializing requests to open for write at a file level, said second API permitting concurrent opens for write at a file level; and hybrid means for managing said second file system based on requests made using said first API, said hybrid means serializing requests to open for write at a file level.
Claim 18
Dependent Claim
46 words
A computer system as set forth in claim 11 wherein said first file manager and said first API support concurrent opens for read at a file level and an open for read at a file level concurrent with an open for write at a file level.
Claim 19
Dependent Claim
37 words
A computer system as set forth in claim 12 wherein said first file manager and said first API support concurrent opens for read at a file level concurrent with an open for write at a file level.
Claim 20
Dependent Claim
43 words
A computer system as set forth in claim 11 wherein said second file manager and said second API support concurrent opens for read concurrent with an open for read at a file level concurrent with an open for write at a file level.
Claim 21
Dependent Claim
37 words
A computer system as set forth in claim 14 wherein said second file manager and said second API support concurrent opens for read at a file level concurrent with an open for write at a file level.
Claim 22
Dependent Claim
37 words
A computer system as set forth in claim 11 wherein when said second file system is open for write from said first API, said hybrid means does not permit an open for read from said second API.
Claim 23
Dependent Claim
35 words
A computer system as set forth in claim 16 wherein when said second file system is open for write from said first API, said hybrid means permits an open for read from said first API.
Claim 24
Dependent Claim
37 words
A computer system as set forth in claim 17 wherein when said second file system is open for write from said first API, said hybrid means permits a plurality of opens for read from said first API.
Claim 25
Dependent Claim
37 words
A computer system as set forth in claim 11 wherein when said second file system is open for read from said first API, said hybrid means permits a plurality of opens for read from said second API.
Claim 26
Dependent Claim
37 words
A computer system as set forth in claim 19 wherein when said second file system is opened for read from said first API, said hybrid means permit a plurality of opens for read from said first API.
Claim 27
Dependent Claim
49 words
A computer system as set forth in claim 11 wherein when a file in said second file system is requested to be opened from said first API and there is an outstanding token for a same file issued via said second API, then said hybrid means invalidates said token.
Claim 28
Dependent Claim
41 words
A computer system as set forth in claim 11 wherein when said second file system is requested to be opened from said first API, then said hybrid means prevents awards of tokens for said second file system via said second API.
References Cited (Backward Citations)
US4825354A
Cited
US4780821A
Cited
US4887204A
Cited
US5142674A
Cited
US5313646A
Cited
US5163131A
Cited
US5355453A
Cited
US5276879A
Cited
US5253359A
Cited
US5287453A
Cited
US5263155A
Cited
US5303375A
Cited
US5305461A
Cited
EP0566895A2
Cited
US5418945A
Cited
US5414839A
Cited
GB2269920A
Cited
EP0588502A2
Cited
US5403639A
Cited
US5561797A
Cited
US5434994A
Cited
US5596748A
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2000-09-15 | 2001-03-17 | 2001-09-16 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2004-09-15 | 2005-03-17 | 2005-09-16 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2008-09-15 | 2009-03-17 | 2009-09-16 | $7700.00 | Window Closed / Lapsed |