File system block reservation manager

• US 7,418,465 B1
• Filed: 10/24/2003
• Issued: 08/26/2008
• Est. Priority Date: 08/18/2000
• Status: Expired due to Term

• Current Assignee: Network Appliance Incorporated (NetApp, Inc.)
• Original Assignee: Network Appliance Incorporated (NetApp, Inc.)
• Inventors: Lewis, Blake, Patel, Kayuri, Chen, Ray
• Primary Examiner(s): Le; Miranda
• Application Number:
  US10/693,326
• Time in Patent Office: 1,768 Days
• Field of Search: 707 1- 10, 707200-205, 707100-102, 707/104.1, 711/129, 711/170, 711/114, 709217-219, 709/203
• US Class Current: 1/1
• CPC Class Codes: G06F 2003/0697 device management, e.g. handlers, drivers, I/O schedulers
• CPC Class Codes: G06F 3/0601 Interfaces specially adapted for storage systems
• CPC Class Codes: G06F 3/0604 Improving or facilitating administration, e.g. storage management
• CPC Class Codes: G06F 3/0631 by allocating resources to storage systems
• CPC Class Codes: G06F 3/064 Management of blocks
• CPC Class Codes: G06F 3/0656 Data buffering arrangements
• CPC Class Codes: G06F 3/0674 Disk device
• CPC Class Codes: Y10S 707/99931 Database or file accessing
• CPC Class Codes: Y10S 707/99956 File allocation

Abstract

A system that manages a file system for a file server. A file operation is received that signals a reservation operation for a file having a file size. Preferably, the file system uses a write anywhere file system layout, the file operation that signals the reservation operation is a zero length write request, and the file operation that signals the reservation operation includes a parameter that specifies the file size. A number of blocks needed to be reserved to accommodate the file is computed. Preferably, computing the number of blocks needed to be reserved to accommodate the file includes determining a total number of direct and indirect blocks needed to accommodate the file size, and subtracting a total number of blocks already allocated for the file and a total number of cached unallocated blocks for the file from the total number of direct and indirect blocks needed to accommodate the file size. A number of unallocated blocks is reserved in the file system, with the number of reserved blocks equal to the number of blocks needed to be reserved to accommodate the file. Reserving the number of blocks preferably includes setting a flag in an inode for the file that indicates blocks have been reserved for the file, and incrementing a reserved block count in a file system information block by the number of blocks needed.

Claims

1. A computerized method of managing a file system for a file server, comprising:

receiving a file operation that signals a reservation operation for reserving an additional number of blocks for storing a file of the file system, the file having a file size;

computing a first number of blocks needed to accommodate the file size;

subtracting from the first number of blocks a second number of blocks already allocated for the file and a third number of delayed allocated blocks for the file to obtain a fourth number of unallocated blocks needed to accommodate the file size; and

using the fourth number of blocks to perform a reservation of unallocated blocks for the file for later allocation, wherein said using the fourth number of blocks to perform a reservation of unallocated blocks for the file for later allocation comprises;

checking that a number of available blocks in the file system is greater than the fourth number of blocks, wherein an error is returned in a case that the number of available blocks is less than the fourth number of blocks,

wherein the number of available blocks in the file system is determined by subtracting a number of allocated blocks, a number of cached unallocated blocks, and a number of reserved blocks from a total number of blocks in the file system, and adding a number of reserved cached unallocated blocks;

wherein the file system uses a write anywhere file system layout characterized in that data to be written are written to new blocks instead of being written to blocks previously allocated for said data.

2. A method as in claim 1, wherein the file operation that signals the reservation operation is a zero length write request.

3. A method as in claim 1, wherein the file operation that signals the reservation operation includes a parameter that specifies the file size.

4. A method as in claim 1, wherein computing comprises:

determining a total number of direct and indirect blocks needed to accommodate the file size.

5. A method as in claim 1, further comprising:

setting a flag in an inode for the file that indicates blocks have been reserved for the file.

6. A method according to claim 1, wherein said using the fourth number of blocks to perform a reservation of unallocated blocks for the file for later allocation comprises:

checking that a fifth number of blocks does not exceed a remainder of a quota for an owner of the file, wherein an error is returned in a case that the fifth number of blocks exceeds the remainder of the quota, wherein the fifth number of blocks comprises a difference between the first number of blocks and the second number of blocks.

7. A method as in claim 1, further comprising releasing reservation of blocks as blocks are written to storage.

8. A method as in claim 7, wherein releasing reservation of blocks further comprises decrementing the number of reserved unallocated blocks by a number of released blocks.

9. A method according to claim 1, further comprising:

caching one or more blocks of the file in a buffer;

writing the one or more blocks to storage; and

decrementing the number of unallocated blocks by the number of blocks written to the storage.

10. A method according to claim 9, further comprising setting a caching flag for each block cached in the buffer.

11. A file server comprising:

a memory storing a computer program,

a processor capable of executing the program, and

a storage device capable of storing files of a file system under control of the processor,

wherein the computer program comprises;

instructions to cause the processor to receive a file operation that signals a reservation operation for a file of the file system, the file having a file size;

instructions to cause the processor to compute a first number of blocks needed to accommodate the file size;

instructions to cause the processor to subtract from the first number of blocks a second number of blocks already allocated for the file and a third number of delayed allocated blocks for the file to obtain a fourth number of unallocated blocks to be reserved to accommodate the file size; and

instructions to cause the processor to use the fourth number of blocks to perform a reservation of unallocated blocks for the file for later allocation,

wherein the instructions to cause the processor to use the fourth number of blocks to perform a reservation of unallocated blocks for the file for later allocation program comprise instructions to cause the processor to check whether a number of available blocks in the file system is greater than the fourth number of blocks, and return an error in a case that the number of available blocks is less than the fourth number of blocks

wherein the processor determines the number of available blocks in the file system by subtracting a number of allocated blocks, a number of cached unallocated blocks, and a number of reserved blocks from a total number of blocks in the file system, and adding a number of reserved cached unallocated blocks;

wherein the file system uses a write anywhere file system layout characterized in that data to be written are written to new blocks instead of being written to blocks previously allocated for said data.

12. A file server according to claim 11, wherein the file operation that signals the reservation operation is a zero length write request.

13. A file server according to claim 11, wherein the file operation that signals the reservation operation includes a parameter that specifies the file size.

14. A file server according to claim 11, wherein the instructions to cause the processor to compute comprise instructions to cause the processor to determine a total number of direct and indirect blocks needed to accommodate the file size.

15. A file server according to claim 11, wherein the program further comprises instructions to cause the processor to set a flag in an inode for the file, the flag indicating that blocks have been reserved for the file.

16. A file server according to claim 11, wherein the program further comprises instructions to cause the processor to check whether a fifth number of blocks does not exceed a remainder of a quota for an owner of the file, and return an error if the fifth number of blocks exceeds the remainder of the quota, wherein the fifth number of blocks comprises a difference between the first number of blocks and the second number of blocks.

17. A file server according to claim 11, wherein the program further comprises instructions to cause the processor to release reservation of blocks as blocks are written to storage.

18. A file server according to claim 17, wherein the instructions to cause the processor to release comprise instructions to cause the processor to decrement the number of the reserved unallocated blocks by a number of released blocks.

19. A method comprising:

receiving at a storage server a request for a space reservation for a data set managed by the storage server; and

in response to the request,

computing a number of blocks needed to be reserved for the data set,

reserving for later allocation a number of unallocated blocks equal to the computed number of blocks, such that a subsequent write operation associated with the reservation can complete the write request without prevention of completion of the write operation due to insufficient memory; and

performing a write operation to write data to the data set by

determining whether a space reservation has been performed for the data set, and

in response to determining that a space reservation has been performed for the data set, allocating one or more blocks for said data without determining whether enough blocks are available for completing the write operation, and

in response to determining that a space reservation has not been performed for the data set, determining whether enough blocks are available for completing the write operation prior to allocating any blocks for said data;

wherein the storage server employs a methodology in which data to be written are written to new blocks instead of being written to blocks previously allocated for said data.

20. A method as recited in claim 19, wherein the request comprises a zero length write request.

21. A method as recited in claim 19, wherein said computing the number of blocks comprises:

computing a first number of blocks representing a number of blocks needed to accommodate a size of the data set;

computing a second number of blocks representing a number of blocks already allocated for the data set;

computing a third number of blocks representing a number of delayed allocated blocks for the data set; and

subtracting the second number of blocks and the third number of blocks from the first number of blocks to produce a fourth number of blocks representing the number of blocks needed to be reserved for the data set.

22. A method as recited in claim 19, wherein said reserving for later allocation the number of unallocated blocks comprises:

setting a flag in a first metadata container associated with the data set, that indicates blocks have been reserved for the data set.

23. A method as recited in claim 22, further comprising:

examining the flag during a subsequent write operation to determine whether blocks have been reserved for the data set.

24. A method as recited in claim 22, wherein said reserving for later allocation the number of unallocated blocks comprises:

incrementing a reserved block count in a second metadata container associated with the data set by the number of blocks needed, the reserved block count indicating how many unallocated blocks have been reserved for data sets managed by the storage server.

25. A storage server comprising:

a processor;

a network interface through which to communicate with a remote client;

a file system; and

a storage device storing code which, when executed by the processor, causes the storage server to execute a process that includes

receiving a signal corresponding to a request for a space reservation operation for a file in the file system;

computing a first number of blocks needed to be reserved to accommodate the file;

reserving for later allocation a fourth number of unallocated blocks in the file system such that the fourth number is calculated by subtracting from the first number of blocks a second number of blocks already allocated for the file and a third number of delayed allocated blocks for the file; and

performing a write operation to write data to the file by

determining whether a block reservation has been performed for the file,

in response to determining that a block reservation has been performed for the file, allocating one or more blocks for said data in the file system without determining whether enough blocks are available in the file system for completing the write operation; and

in response to determining that a block reservation has not been performed for the file, determining whether enough blocks are available in the file system for completing the write operation prior to allocating any blocks for said data in the file system;

wherein the file system employs a methodology in which data to be written are written to new blocks instead of being written to blocks previously allocated for said data.

26. A storage server as recited in claim 25, wherein the signal represents a zero length write request.

27. A storage server as recited in claim 25, wherein said computing the number of blocks needed to be reserved to accommodate the file comprises:

computing a first number of blocks representing a number of blocks needed to accommodate a size of the file;

computing a second number of blocks representing a number of blocks already allocated for the file;

computing a third number of blocks representing a number of delayed allocated blocks for the file; and

subtracting the second number of blocks and the third number of blocks from the first number of blocks to produce a fourth number of blocks representing the number of blocks needed to be reserved to accommodate the file.

28. A storage server as recited in claim 25, wherein said reserving for later allocation the number of unallocated blocks in the file system comprises:

setting a flag in a first metadata container associated with the file, that indicates blocks have been reserved for the file.

29. A storage server as recited in claim 28, wherein said process further comprises:

examining the flag during a subsequent write operation to determine whether blocks have been reserved for the file.

30. A storage server as recited in claim 28, wherein said reserving for later allocation the number of unallocated blocks in the file system comprises:

incrementing a reserved block count in a second metadata container associated with the file by the number of blocks needed, the reserved block count indicating how many unallocated blocks have been reserved for files in the file system.

31. A computerized method of managing a file, comprising:

receiving a write request for a file;

determining a desired number of blocks in which to store the file;

determining a number of previously reserved blocks by adding allocated and nonallocated blocks previously associated with the file;

determining an additional number of blocks by subtracting the number of previously reserved blocks from the desired number of blocks in which to store the file;

reserving the additional number of blocks; and

writing the file after successfully reserving the additional number of blocks by

determining whether a space reservation has been performed for the data set, and

in response to determining that a space reservation has been performed for the data set, allocating one or more blocks for said data without determining whether enough blocks are available for completing the write operation;

in response to determining that a block reservation has not been performed for the file, determining whether enough blocks are available in the file system for completing the write operation prior to allocating any blocks for said data in the file system;

wherein the file system employs a methodology in which data to be written are written to new blocks instead of being written to blocks previously allocated for said data.

32. The method of claim 31, wherein the desired number of blocks is the minimum number of blocks required for storing the file.

33. The method of claim 31, wherein the file is cache storage.

34. The method of claim 31, wherein the reserving the additional number of blocks includes setting a flag in an inode for the file.