# US 2005/0240628 A1 · Delegation of metadata management in a storage system by leasing of free file system blocks from a file system owner

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2005/0240628 A1
- Document ID: US20050240628A1
- Status: Published application
- Kind: A1
- Application number: 11/168,136
- Filed: 2005-06-27
- Published: 2005-10-27
- Earliest claimed: 1999-03-03
- Assignees: EMC Corporation
- Inventors: Xiaoye Jiang; Gang Ma; Uresh Vahalia
- Web page: https://patentgrep.com/patent/US20050240628A1

## CPC

- G06F 16/10: File systems; File servers
- Y10S 707/99956: File allocation
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

Metadata management in a file server or storage network is delegated from a primary data processor to a secondary data processor in order to reduce data traffic between the primary data processor and the secondary data processor. The primary data processor retains responsibility for managing locks upon objects in the file system that it owns, and also retains responsibility for allocation of free blocks and inodes of the file system. By leasing free blocks and inodes to the secondary and granting locks to the secondary, the secondary can perform the other metadata management tasks such as appending blocks to a file, truncating a file, creating a file, and deleting a file.

## Claims

### Claim 1

A method of operating a primary data processor and a secondary data processor for access to a file system in data storage, said method comprising:
the primary data processor managing locks upon files in the file system, and managing allocation of free blocks of the file system; and
appending new data to a file in the file system by the secondary data processor obtaining an allocation of at least one free block from the primary data processor, the secondary data processor writing the new data to the free block, the secondary data processor obtaining a lock on the file from the primary data processor, and the secondary data processor updating metadata of the file.

### Claim 2 (depends on 1)

The method of claim 1, wherein the secondary data processor updates metadata of the file by writing new metadata of the file directly to the file system in data storage by bypassing the primary data processor.

### Claim 3 (depends on 1)

The method of claim 1, wherein the secondary data processor sends a request to the primary data processor for a lock on the file, and thereafter writes the data for the file to the free block, and thereafter receives an indication of a grant of the lock on the file.

### Claim 4 (depends on 3)

The method as claimed in claim 3, wherein the secondary data processor receives from the primary data processor an inode number of an inode of the file with the indication of a grant of the lock on the file, and the secondary data processor uses the inode number of the file to update the metadata of the file.

### Claim 5

A method of operating a primary data processor and a secondary data processor for access to a file system in data storage, said method comprising:
the primary data processor managing locks upon files in the file system, and managing allocation of free blocks of the file system; and
the secondary data processor appending new data to a file in the file system by obtaining an allocation of at least one free block from the primary data processor, writing the new data to the free block, obtaining a lock on the file from the primary data processor, and linking the free block to the file.

### Claim 6 (depends on 5)

The method of claim 5, wherein the secondary data processor links the free block to the file by writing new metadata of the file directly to the file system in data storage by bypassing the primary data processor.

### Claim 7 (depends on 5)

The method of claim 5, wherein the secondary data processor sends a request to the primary data processor for a lock on the file, and thereafter writes the data for the file to the free block, and thereafter receives an indication of a grant of the lock on the file.

### Claim 8 (depends on 7)

The method as claimed in claim 7, wherein the secondary data processor receives from the primary data processor an inode number of an inode of the file with the indication of a grant of the lock on the file, and the secondary data processor uses the inode number of the file to link the free block to the file.

### Claim 9 (depends on 5)

The method of claim 5, wherein the primary data processor maintains a record of free blocks allocated to the secondary data processor.

### Claim 10 (depends on 5)

The method of claim 5, which further includes the secondary data processor truncating blocks from files of the file system.

### Claim 11 (depends on 10)

The method of claim 10, which further includes the secondary data processor returning the truncated blocks to a pool of free blocks in the file system in the data storage.

### Claim 12 (depends on 5)

The method of claim 5, which further includes the secondary data processor obtaining a lock on a specified directory from the primary data processor, and then the secondary data processor writing to the specified directory in the data storage.

### Claim 13

A storage system comprising:
data storage containing a file system;
a primary data processor linked to the data storage for access to metadata of the file system for locking files of the file system and allocating free blocks in the file system; and
a secondary data processor linked to the data storage for access to data and metadata of the file system over a data path that bypasses the primary data processor, and linked to the primary data processor for requesting and obtaining locks on the files in the file system and requesting and obtaining allocations of free blocks in the file system;
wherein the secondary data processor is programmed for writing data to a specified file in the file system by obtaining an allocation of at least one free block from the primary data processor, writing data to said at least one free block, obtaining a lock on the specified file from the primary data processor, and appending said at least one free block to the specified file by writing new metadata for the specified file to the file system in the data storage over the data path that bypasses the primary data processor.

### Claim 14 (depends on 13)

The storage system as claimed in claim 13, wherein the data storage is in a cached disk array, the primary data processor is a file manager computer, and the secondary data processor is a client in a data network linking the client to the cached disk array and the primary data processor.

### Claim 15 (depends on 13)

The storage system as claimed in claim 13, wherein the data storage is a cached disk array in a network file server, the primary data processor is a first data mover computer in the network file server, and the secondary data processor is a second data mover computer in the network file server.

### Claim 16 (depends on 13)

The storage system as claimed in claim 13, wherein the secondary data processor is programmed to send a request to the primary data processor for a lock on the specified file, and thereafter write data for the specified file to said at least one free block while the primary data processor is responding to the request for the lock on the specified file.

### Claim 17 (depends on 16)

The storage system as claimed in claim 16, wherein the secondary data processor is programmed to receive from the primary data processor an inode number of an inode of the specified file with an indication of a grant of the lock on the specified file, and to use the inode number of the specified file to link said at least one free block to the specified file.

### Claim 18 (depends on 17)

The storage system as claimed in claim 17, wherein the secondary data processor is programmed to truncate blocks from files of the file system by writing new metadata of the files to the file system in the data storage over the data path that bypasses the primary data processor.

### Claim 19 (depends on 18)

The storage system as claimed in claim 18, wherein the secondary data processor is further programmed to return the truncated blocks to a pool of free blocks in the file system in the data storage.

### Claim 20 (depends on 13)

The storage system as claimed in claim 13, wherein the secondary data processor is programmed to write to a specified directory of the file system by obtaining a lock on the specified directory from the primary data processor, and writing to the specified directory in the data storage over the data path that bypasses the primary data processor.
