Efficient journaling and recovery mechanism for embedded flash file systems

• US 20080077590A1
• Filed: 09/22/2006
• Published: 03/27/2008
• Est. Priority Date: 09/22/2006
• Status: Abandoned Application

• Current Assignee: Honeywell International Inc.
• Original Assignee: Honeywell International Inc.
• Inventors: Pandit, Anil Kumar
• Application Number:
  US11/525,637
• Publication Number:
  US 20080077590A1
• Time in Patent Office: Days
• US Class Current: 707/8
• CPC Class Codes: G06F 11/1435 using file system or storage system metadata
• CPC Class Codes: G06F 11/1441 Resetting or repowering
• CPC Class Codes: G06F 16/1774 Locking methods, e.g. locking methods for file systems allowing shared and concurrent access to files
• CPC Class Codes: G06F 16/1847 specifically adapted to static storage, e.g. adapted to flash memory or SSD

Abstract

Implicit journaling of a file operation relating to a file stored in a flash memory is performed by locking a semaphore corresponding to the file on which a file operation is to be performed, by initializing journaling of the file operation using the file map, by performing the file operation on the file, by completing journaling of the file operation using a file map corresponding to the file, and unlocking the semaphore. Additionally or alternatively, a file system is placed in a stable state following an interruption occurring during a file operation by scanning File Maps corresponding to the files, determining whether a file operation is incomplete based on validity flags contained in the file maps, and performing remediation so as to eliminate the incomplete file operation.

Claims

1. A method of journaling a file operation relating to a file stored in a flash memory, the flash memory containing a file map containing at least one entry about the file, the method comprising:

locking a semaphore corresponding to the file on which a file operation is to be performed;

initializing journaling of the file operation using the file map;

performing the file operation on the file;

completing journaling of the file operation using the file map; and

, unlocking the semaphore.

2. The method of claim 1 wherein the performing of the file operation comprises performing a write transaction in append, wherein the initializing of the journaling of the file operation using the file map comprises setting a validity flag of the file map to an initial erased state, and wherein the completing of the journaling of the file operation using the file map comprises changing the validity flag to a valid state following writing of the file.

3. The method of claim 1 wherein the performing of the file operation comprises performing a write transaction in an overwrite mode, wherein the initializing of the journaling of the file operation using the file map comprises setting a first validity flag for a new data block to a default erased state, and wherein the completing of the journaling of the file operation using the file map comprises:

setting the first validity flag to a valid state following writing of file data to the new data block; and

,

setting a second validity flag for an old data block containing data to be overwritten to a dirty state following writing of the file data to the new data block.

4. The method of claim 1 wherein the performing of the file operation comprises performing a file creation, wherein the initializing of the journaling of the file operation using the file map comprises setting a validity flag of a file map block to an erased state, and wherein the completing of the journaling of the file operation using the file map comprises:

changing the validity flags to a valid state following writing of information into an Inode block; and

,

updating an extended filemap entry to point to a filemap block allocated for the file creation.

5. The method of claim 1 wherein the performing of the file operation comprises performing a file deletion, wherein the initializing of the journaling of the file operation using the file map comprises setting a validity flag in a file map corresponding to the file, and wherein the completing of the journaling of the file operation using the file map comprises changing the validity flag from the deleted state to a dirty state following deletion of the file and upon recovering of all the blocks used by the file.

6. The method of claim 1 wherein the performing of the file operation comprises performing a file rename, wherein the initializing of the journaling of the file operation using the file map comprises setting a first validity flag of a file map corresponding to a new meta-data block allocated for a new name of the file to an erased state, x and wherein the completing of the journaling of the file operation using the file map comprises:

setting a second validity flag of a file map corresponding to an old meta-data block containing an old name for the file to a dirty state; and

,

changing the first validity flag to a valid state following writing of inode information with the updated name in a newly allocated inode block.

7. The method of claim 1 wherein the performing of the file operation comprises performing a reclamation, wherein the initializing of the journaling of the file operation using the file map comprises setting a validity flag of the file map corresponding to a new block to which valid data from a reclaimed block is to be relocated to an initial erased state, wherein the performing the file operation on the file comprises relocating the valid data to the new block, wherein the completing of the journaling of the file operation using the file map comprises changing the validity flag to a valid state following relocating of the valid data, and wherein the method further comprises:

relocating at least one file data block;

relocating at least one inode block; and

,

relocating at least one fmap block.

8. The method of claim 1 wherein the performing of the file operation comprises performing a write transaction in append, and wherein the journaling of the file operation using the file map comprises:

locking a semaphore corresponding to a file partition containing the file to be appended;

allocating a new data block for the write in append operation;

setting the new block as used;

setting a validity flag of the file map corresponding to the new block to an erased state;

writing file data to the new block;

changing the validity flag to a valid state; and

,

unlocking the semaphore.

9. The method of claim 1 wherein the performing of the file operation comprises performing a write transaction in an overwrite mode, and wherein the journaling of the file operation using the file map comprises:

locking a semaphore corresponding to a file partition containing the file that is to be overwritten;

overwriting the file data blocks with the updated data; and

,

unlocking the semaphore.

10. The method of claim 1 wherein the performing of the file operation comprises performing a file creation, and wherein the journaling of the file operation using the file map comprises:

locking a semaphore corresponding to a partition containing the file to be created;

allocating a first free data block for an inode and a second free data block for a file map block for the file to be created;

setting the first and second free data blocks as used;

adding entries for a new file to a parent file map;

setting a validity flag in the parent file map to a default erased state;

erasing the second free data block used for storing the fmap entries of the file;

writing inode information into the first free data block;

setting validity flags in the first and second free data blocks to a valid state;

allocating an incore inode for the new file being created;

setting the validity flag in the parent file map to the valid state; and

,

unlocking the file/semaphore.

11. The method of claim 1 wherein the performing of the file operation comprises performing a file deletion, and wherein the journaling of the file operation using the file map comprises:

locking a semaphore corresponding to a partition containing the file to be deleted;

setting a validity flag in a file map of an incore inode corresponding to the file to be deleted to a deleted state;

setting a validity flag in a parent file map corresponding to the file to be deleted to the deleted state;

traversing the file and setting all valid file data blocks, all valid file map blocks, and the inode block to a dirty state;

setting the validity flag in the parent file map to the dirty state;

freeing up the incore inode; and

,

unlocking the semaphore.

12. The method of claim 1 wherein the performing of the file operation comprises performing a file rename, and wherein the journaling of the file operation using the file map comprises:

locking a semaphore corresponding to a partition containing the file to be renamed;

allocating a new block to an inode corresponding to the file;

adding a new entry in the parent'"'"'s file map for the new name;

setting a validity flag in the new entry to an erased state;

updating inode information in the new block;

setting the validity flag in the new entry to a valid state;

setting a validity flag in an entry for the old inode in the parent'"'"'s file map to a dirty entry;

updating an incore inode with a new hash for the renamed file; and

,

unlocking the semaphore.

13. The method of claim 1 wherein the performing of the file operation comprises performing a file creation, and wherein the locking of a semaphore, initializing of journaling, performing of the file operation, completing the journaling, and unlocking the semaphore comprises:

locking a semaphore corresponding to a partition containing the file to be created;

allocating a first free data block for an inode and a second free data block for a file map block for the file to be created;

adding entries for a new file to a parent file map;

setting a validity flag in the parent file map to a default erased state;

writing inode information into the first free block with an extended fmap entry in the inode block pointing to the second free block;

setting validity flags in the first and second free data blocks to a valid state;

setting the second free data block as used;

setting the first free data block as used;

setting the validity flag in the parent file map to the valid state; and

,

unlocking the file/semaphore.

14. The method of claim 1 wherein the performing of the file operation comprises performing a file deletion, and wherein the locking of a semaphore, initializing of journaling, performing of the file operation, completing the journaling, and unlocking the semaphore comprises:

locking a semaphore corresponding to a partition containing the file to be deleted;

setting a validity flag in a parent file map corresponding to the file to be deleted to the deleted state;

setting all valid file data blocks, all valid file map blocks, and the inode block to a free state;

setting the validity flag in the parent file map to the dirty state;

freeing up an incore inode corresponding to the deleted file; and

, unlocking the semaphore.

15. A method performed at a file system startup with respect to files stored on a flash memory, the method comprising:

scanning file maps corresponding to the files/directories;

determining whether a file operation is incomplete based on validity flags contained in the file maps; and

,

performing remediation so as to eliminate the incomplete file operation.

16. The method of claim 15 wherein the performing of remediation so as to eliminate the incomplete file operation comprises completing the file operation.

17. The method of claim 15 wherein the performing of remediation so as to eliminate the incomplete file operation comprises:

undoing the incomplete operation; and

,

recovering any blocks that might lead to storage block leaks.

18. The method of claim 15 further comprising:

validating links; and

,

marking as dirty any meta-data blocks that have not been completely written.

19. The method of claim 15 further comprising invalidating older duplicate file map entries in the event that there are duplicate file map entries.

20. The method of claim 15 further comprising:

detecting an erase operation interruption based on all blocks in an erase unit being marked with a dirty state; and

,

completing the erase operation for the erase unit.

21. The method of claim 15 further comprising:

detecting an incomplete reclamation of an erase unit based on a valid state of at least one block in the erase unit; and

,

completing the reclamation for the erase unit.

22. The method of claim 15 further comprising:

detecting an incomplete file deletion if a validity flag corresponding the file being deleted is in a delete state;

completing the file deletion.

23. The method of claim 22 wherein the completing of the file deletion comprises:

marking any meta-data blocks, data blocks, and inode blocks corresponding to the file being deleted as free; and

,

setting a validity flag of a file map corresponding the file being deleted to a dirty state.

24. The method of claim 15 further comprising:

detecting an incomplete file creation if a validity flag corresponding to the file being created is in a default erased state; and

,

undoing the file creation by marking any blocks set aside for the file being created as dirty and by setting a validity flag in a file map corresponding to the file being created to a dirty state.

25. A method of journaling a file operation relating to a file stored in a flash memory, the flash memory containing a file map containing at least one entry about the file, the method comprising:

locking a semaphore corresponding to the file on which a file operation is to be performed;

performing the file operation on the file;

journaling the file operation using the file map; and

,

unlocking the semaphore.