IP Library Granted Patent US 8,015,215
Granted Patent B2
US 8,015,215 · App. 11/510,110 · Granted Sep 6, 2011

Delegation in a file system with distributed components

Assignee: Oracle America, Inc.
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,015,215
App. No.
11/510,110
Granted
Sep 6, 2011
Kind
B2
Abstract

Various systems and methods of a distributed file system architecture are disclosed. A method for creating a file may include receiving a message to open or create a file with a given name from a file system call handler. Once the message has been received a determination may then be made as to whether a file with the given name exists. If no file with the given name exists, then a new file with the given name may be created and assigned a globally unique file number.

Claims (38)

1. A computer-implemented method for creating a file comprising:

receiving a request message to open or create a file with a given name from a file system call handler;

determining if a file with the given name exists;

creating a new file with the given name, if no file with the given name exists;

assigning, to the new file, a globally unique file number that identifies the file;

generating an intent log record to ensure that file creation is completed in the event of a system failure;

allowing a directory manager to use a distribution manager to create a file manager for the new file; and

initializing the file manager with the appropriate default attributes for the new file, wherein the default attributes for the new file are based at least in part on a creating process's credentials and arguments to the request message.

2. The method of claim 1 , further comprising adding a pointer to the new file in a directory once the new file has been initialized.

3. The method of claim 1 , further comprising:

verifying that a buffer passed by an application is readable; and locking the buffer to a physical address.

4. The method of claim 1 , further comprising:

allocating a backing store by contacting a storage manager; and receiving a new object for the file.

5. The method of claim 4 , further comprising:

receiving a storage layout containing information about a storage manager;

and caching the storage layout with the file.

6. The method of claim 4 , further comprising updating file size and timestamp.

7. A computer-implemented method comprising:

receiving a request from a requesting device for a message port address associated with a file manager responsible for a file being requested by the requesting device;

determining which file manager is responsible for the file;

returning to the requesting device the message port of the file manager which was determined to be responsible for the file;

sending a new file manager request to an input/output node if it was determined that no file manager was responsible for the file;

initializing a new file manager by assigning a message port, wherein the new file manager is responsible for the file; and returning the message port of the new file manager to the requesting device.

8. The method of claim 7 , wherein determining which file manager is responsible for the file comprises examining tables containing information about file association with file managers.

9. The method of claim 7 , wherein the request is received through a message port.

10. A computer-readable storage medium containing a set of instructions causing one or more processors to:

receive a request message to open or create a file with a given name from a file system call handler;

determine if a file with the given name exists;

create a new file with the given name, if no file with the given name exists;

assign, to the new file, a globally unique file number that identifies the file;

initialize the file manager with default attributes for the new file, wherein the default attributes for the new file are based at least in part on a creating process's credentials and arguments to the request message;

and allow a directory manager to use a distribution manager to create a file manager for the new file.

11. The computer-readable storage medium of claim 10 , further comprising instructions to cause one or more processors to generate an intent log to ensure that file creation is completed in the event of a system failure.

12. The computer-readable storage medium of claim 10 further comprising instructions to cause one or more processors to add a pointer to the new file in a directory once the new file has been initialized.

13. The computer-readable storage medium of claim 10 , further comprising instructions to cause one or more processors to:

verify that a buffer passed by an application is readable; and lock the buffer to a physical address.

14. The computer-readable storage medium of claim 10 , further comprising instructions to cause one or more processors to:

locate a backing store by contacting a storage manager; and receive a new object for the file.

Assignments (2)
MERGER AND CHANGE OF NAME Recorded Dec 16, 2015
From: ORACLE USA, INC.; SUN MICROSYSTEMS, INC.; ORACLE AMERICA, INC.
To: ORACLE AMERICA, INC.
Reel/Frame 037311/0121 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 24, 2006
From: COVERSTON, HARRIET G.; RANG, ANTON B.
To: SUN MICROSYSTEMS, INC.
Reel/Frame 018258/0111 →
Continuity (1)
Related Publication 20080065583A1 · Mar 13, 2008