File system having transaction record coalescing
First Claim
1. An electronic data system comprising:
- a flash memory having a stored data;
a file system code executable to organize and maintain the stored data in one or more files and one or more directories;
a transaction file maintained by the file system code in the flash memory, the transaction file comprising a plurality of transaction records stored on the flash memory, where the plurality of transaction records correspond to a plurality of transactions that have been, or are to be executed, on the one or more files and/or the one or more directories, where each transaction record of the plurality of transaction records comprises a header section and a data section, where each header section identifies a file of the one or more files and/or a directory of the one or more directories associated with each data section; and
where the file system code coalesces the plurality of transaction records stored on the flash memory by;
scanning each header section of each transaction record of the plurality of transaction records to identify a first subset of the plurality of transaction records directed to a same file, a second subset of the plurality of transaction records directed to a same logical portion of a file, and/or a third subset of the plurality of transaction records directed to a same directory, andcombining the first subset of the plurality of transaction records identified during the scanning as directed to the same file into one or more first coalesced transaction records and releasing one or more transaction records of the first subset of the plurality of transaction records identified as directed to the same file as a free memory to thereby reduce an amount of memory used by the transaction file,combining the second subset of the plurality of transaction records identified during the scanning as directed to the same logical portion of the file into one or more second coalesced transaction records and releasing one or more transaction records of the second subset of the plurality of transaction records identified as directed to the same logical portion of the file as the free memory to thereby reduce the amount of memory used by the transaction file, and/orcombining the third subset of the plurality of transaction records identified during the scanning as directed to the same directory into one or more third coalesced transaction records and releasing one or more transaction records of the third subset of the plurality of transaction records identified as directed to the same directory as the free memory to thereby reduce the amount of memory used by the transaction file;
and where each header section of each transaction record of the plurality of transaction records further comprises a first field used to determine the starting address at which the data section is to be written into the identified file of the one or more files and/or the identified directory of the one or more directories, and a second field used to determine an amount of the identified file of the one or more files and/or the identified directory of the one or more directories that is to be overwritten.
13 Assignments
0 Petitions
Accused Products
Abstract
An electronic data system comprises memory storage having stored data, file system software, and a transaction file. The transaction file is maintained by the file system software, and includes a plurality of transaction records corresponding to transactions that have been or are to be executed on one or more files and/or the or more directories of the file system. The file system software operates to organize and maintain the stored data in the files and directories and also to coalesce multiple transaction records meeting one or more criteria into fewer coalesced transaction records. The physical memory space required by the transaction file is reduced by the transaction record coalescing. The coalesced transaction records may be constructed so that they represent a logical result of applying each transaction record of a transaction record set in chronological order. Once the coalesced transaction records have been committed in the file system, the physical memory used by the original transaction records in the set may be reclaimed for further use (e.g., to store further transaction records) or may be otherwise removed from further use (e.g., when the physical memory is located in a block of memory in a flash-like memory device that has reached its maximum number of write and/or erase cycles).
133 Citations
16 Claims
-
1. An electronic data system comprising:
-
a flash memory having a stored data; a file system code executable to organize and maintain the stored data in one or more files and one or more directories; a transaction file maintained by the file system code in the flash memory, the transaction file comprising a plurality of transaction records stored on the flash memory, where the plurality of transaction records correspond to a plurality of transactions that have been, or are to be executed, on the one or more files and/or the one or more directories, where each transaction record of the plurality of transaction records comprises a header section and a data section, where each header section identifies a file of the one or more files and/or a directory of the one or more directories associated with each data section; and where the file system code coalesces the plurality of transaction records stored on the flash memory by; scanning each header section of each transaction record of the plurality of transaction records to identify a first subset of the plurality of transaction records directed to a same file, a second subset of the plurality of transaction records directed to a same logical portion of a file, and/or a third subset of the plurality of transaction records directed to a same directory, and combining the first subset of the plurality of transaction records identified during the scanning as directed to the same file into one or more first coalesced transaction records and releasing one or more transaction records of the first subset of the plurality of transaction records identified as directed to the same file as a free memory to thereby reduce an amount of memory used by the transaction file, combining the second subset of the plurality of transaction records identified during the scanning as directed to the same logical portion of the file into one or more second coalesced transaction records and releasing one or more transaction records of the second subset of the plurality of transaction records identified as directed to the same logical portion of the file as the free memory to thereby reduce the amount of memory used by the transaction file, and/or combining the third subset of the plurality of transaction records identified during the scanning as directed to the same directory into one or more third coalesced transaction records and releasing one or more transaction records of the third subset of the plurality of transaction records identified as directed to the same directory as the free memory to thereby reduce the amount of memory used by the transaction file; and where each header section of each transaction record of the plurality of transaction records further comprises a first field used to determine the starting address at which the data section is to be written into the identified file of the one or more files and/or the identified directory of the one or more directories, and a second field used to determine an amount of the identified file of the one or more files and/or the identified directory of the one or more directories that is to be overwritten. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9)
-
-
10. A computer readable storage medium having a plurality of computer- executable instructions for performing a method comprising:
-
organizing and maintaining a plurality of files and a plurality of directories stored on a flash memory device; maintaining, on the flash memory device, a transaction file comprising a plurality of transaction records where each transaction record comprises a header section and a data section, where each header section identifies a file of the plurality of files and/or a directory of the plurality of directories associated with each data section; coalescing the plurality of transaction records stored on the flash memory device by; scanning each header section of each transaction record of the plurality of transaction records to identify a first subset of the plurality of transaction records directed to a same file, a second subset of the plurality of transaction records directed to a same logical portion of a file, and/or a third subset of the plurality of transaction records directed to a same directory, combining the first subset of the plurality of transaction records identified during the scanning as directed to the same file into one or more first coalesced transaction records and releasing one or more transaction records of the first subset of the plurality of transaction records identified as directed to the same file to thereby reduce an amount of memory used by the transaction file, combining the second subset of the plurality of transaction records identified during the scanning as directed to the same logical portion of the file into one or more second coalesced transaction records and releasing one or more transaction records of the second subset of the plurality of transaction records identified as directed to the same logical portion of the file to thereby reduce the amount of memory used by the transaction file, and/or combining the third subset of the plurality of transaction records identified during the scanning as directed to the same directory into one or more third coalesced transaction records and releasing one or more transaction records of the third subset of the plurality of transaction records identified as directed to the same directory to thereby reduce the amount of memory used by the transaction file; and where each header section of each transaction record of the plurality of transaction records further comprises a first field used to determine the starting address at which the data section is to be written into the identified file of the one or more files and/or the identified directory of the one or more directories, and a second field used to determine an amount of the identified file of the one or more files and/or the identified directory of the one or more directories that is to be overwritten. - View Dependent Claims (11, 12, 13, 14, 15, 16)
-
Specification