US20130080485A1 - Quick filename lookup using name hash - Google Patents
Quick filename lookup using name hash Download PDFInfo
- Publication number
- US20130080485A1 US20130080485A1 US13/685,018 US201213685018A US2013080485A1 US 20130080485 A1 US20130080485 A1 US 20130080485A1 US 201213685018 A US201213685018 A US 201213685018A US 2013080485 A1 US2013080485 A1 US 2013080485A1
- Authority
- US
- United States
- Prior art keywords
- field
- directoryentry
- value
- file
- length
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G06F17/30312—
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1417—Boot up procedures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/164—File meta data generation
- G06F16/166—File name conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/13—File access structures, e.g. distributed indices
- G06F16/137—Hash-based
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
- G06F16/152—File search processing using file content signatures, e.g. hash values
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
- G06F9/4403—Processor initialisation
Definitions
- portable computing devices such as digital still cameras, digital video cameras, media players, mobile phones, mobile computing devices, personal digital assistants, and the like that maintain data on a storage media, such as a portable storage media.
- a storage media such as a portable storage media.
- the continued development of more complex portable computing devices and larger storage capacity portable storage media places a greater demand for flexibility on the file system format used on the storage media.
- Current file system format approaches can become deficient in that they may provide inadequate flexibility for increasing storage size capacities and/or storage media applications.
- the extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined.
- the primary and secondary directory entry types can be further classified as critical and benign directory entries.
- a computer-readable medium having computer-executable components for storing data is provided.
- the computer-readable components can include specific structures for improving the efficiency of determining if a target file name exists.
- determining if the target file name exists includes (1) determining a file name hash, (2) finding a directory entry set containing the same hash and a potentially matching filename, thus either reducing the set of possible directory entries or more quickly removing a directory entry from consideration, and (3) determining the target file name exists by matching its file name against the potentially matching filename.
- target file name may be converted to an uppercase version of the filename, e.g. for operating systems which perform case-insensitive operations on files.
- conversion to uppercase may be based on an Up-Case Table stored on the media.
- the directory entry can be read from one or more computer readable storage media, and the file name hash is compared to the directory entry set name hash value.
- determining the file name hash can include using a set of pre-calculated hash values for at least a portion of the target file name. For example, if the device only creates 1000 file names, it can lookup the corresponding file name hash from a pre-computed corresponding set of values instead of performing the calculation.
- a portion of the file names commonly created by the device are the same (e.g., all files start with “IMG” followed by a four digit number)
- a portion of the hash can be precomputed (e.g., “IMG0”, “IMG1”, “IMG2”, “IMG”, etc.) to further reduce computation of the hash value.
- the above processes can enable determination if a file name exists by allowing a comparison of fixed-length file hashes prior to comparisons of variable-length strings.
- a directory entry set on one or more computer-readable storage media is updated to contain information corresponding to a file.
- the directory entry set can be comprised of at least three contiguous DirectoryEntry data structures, the first of which can be a File DirectoryEntry data structure, the second can be a Stream Extension DirectoryEntry data structure, and the third can be a first File Name Extension DirectoryEntry data structure of a one or more contiguous File Name Extension DirectoryEntry data structures, the Stream Extension DirectoryEntry data structure can include a name hash field and a name length field, and the name length field can indicate the number of characters in the file name stored in the one or more contiguous File Name Extension DirectoryEntry data structures.
- the DirectoryEntry data structures are all of the same fixed length, to further improve computational efficiencies.
- FIGS. 1A-1C are block diagrams illustrative of an illustrative environment including a portable computing device and a storage device implementing the extensible file system format in accordance with embodiments of the invention.
- FIG. 2 is a block diagram illustrative of various volume layout components corresponding to an extensible file system format in accordance with an embodiment of the invention.
- FIG. 3 is a block diagram illustrative of an extensible file system directory structures including primary and secondary directory entry structures in accordance with an embodiment of the invention.
- FIG. 4 is a block diagram illustrative of data components for implementing a boot process block in an extensible file system format in accordance with an embodiment of the invention.
- FIG. 5 is a block diagram illustrative of data components for implementing directory entries in an extensible file system format in accordance with an embodiment of the invention.
- FIG. 6 is a block diagram illustrative of data components for implementing a file name and extensions in an extensible file system format in accordance with an embodiment of the invention.
- FIG. 7 is a block diagram illustrative of data components for implementing a volume identifier in an extensible file system format in accordance with an embodiment of the invention.
- FIG. 8 is a block diagram illustrative of data components for implementing an extensible directory entry in an extensible file system format in accordance with an embodiment of the invention.
- FIG. 9 is a block diagram illustrative of data components for implementing an extensible directory entry in an extensible file system format in accordance with an embodiment of the invention.
- FIG. 10 is a block diagram illustrative of data components for implementing an access control list in an extensible file system format in accordance with an embodiment of the invention.
- FIG. 11 is a flow diagram illustrative of a file name creation routine for an extensible file system format in accordance with an embodiment of the invention.
- FIG. 12 is an example of a suitable computing system environment for an extensible file system format.
- the application relates to an extensible file system format and various processes associated with the extensible file system format.
- the extensible file system format corresponds to an extensible file system format for portable storage media and various processes associated with the extensible file system format on the portable storage media.
- Extensible File Allocation Table is one illustrative embodiment of the disclosed file system.
- the exFAT embodiment retains both the simplicity and ease of implementation of other FAT-based file systems.
- the file directory structure has been kept unsorted and “flat”.
- the exFAT embodiment also enables many files (e.g. up to 2,796,202) in a single directory.
- a comparison of the target file name can be done against each file record (e.g. DirectoryEntry set).
- a string comparison can be more processor, power, and energy intensive than an integer comparison.
- file records e.g. DirectoryEntry sets
- the speed and efficiency of the operation to find the matching target file name is improved.
- the speed and efficiency of later operations to find this file by name can be improved.
- the hash function can be based on a partly case-insensitive manner.
- the file system can embed the lower-case to upper-case translation table on the media.
- Embedding the lower-case to upper-case translation table can provide support for unicode character mappings which may spring into existence or change in the future, without affecting the resulting hash on existing media. Additional details of an exFAT embodiment can be found more fully described in Appendix A, which begins at page 34.
- FIGS. 1A-1C are block diagrams illustrative of various operating environments 100 for the extensible file system format.
- the extensible file system format is utilized to store data from a computing device, such as a mobile computing device 102 , and a storage media, such as a portable storage media 104 .
- the mobile computing device 102 can correspond to any one of a variety of computing devices, including but not limited to, portable computing devices, mobile telephones, personal digital assistants, music players, media players.
- the portable storage media can also include, but is not limited to, hard drives, flash media, micro-drives and other storage media.
- the extensible file system on the portable storage media 104 does not have to include any type of executable or readable software components, such as an operating environment, utilized by the mobile computing device 102 .
- the extensible file system on the portable storage media 104 may include executable or readable software components used by the mobile device 102 .
- the mobile computing device 102 may be in communication with other computing devices for collecting/exchanging data to be stored on the portable storage media 104 .
- the mobile computing device 102 may be in direct communication with another computing device 106 and storage media 108 .
- the direct communication can correspond to various wired and wireless communication methods.
- the other storage media 108 is not required to be formatted in accordance with the extensible file system format.
- the mobile computing device 102 may also be in communication with another computing device 110 and storage media 112 , via a network connection.
- the network connection can correspond to local area network (LAN) and wide are network (WAN) connections.
- the volume layout 200 includes a boot parameters component 202 that include various information related to a description of the file system parameters of the partition.
- the boot parameters component 202 can include code for bootstrapping from a defined partition, fundamental file system parameters for the defined partition, and various error checking information.
- a data structure for defining at least a portion of the boot parameters will be described below with regard to FIG. 4 .
- the volume layout 200 also includes an extensible parameters component, designated as OEM parameters 204 , that define various additional data structures used in conjunction with the file system.
- OEM parameters 204 an original equipment manufacture (OEM) may specify various extensible data structures, such as performance parameters for a storage medium, that can be defined at time of manufacture.
- the volume layout 200 can further include a file allocation table component 206 that defines file and directory allocations.
- each entry in the file allocation table component 206 corresponds to a 32-bit entry that represents an allocated cluster, an unallocated cluster or an unusable cluster.
- the volume layout 200 can still further include series of file data components 208 A- 208 X that correspond to the data stored according to the file system format.
- Various data structures for defining a portion of the file data components 208 A- 208 X will be defined with regard to FIGS. 3-10 .
- the file data components 208 may include one or more directory entries according to a directory structure 300 .
- directory structure 300 is organized into primary directory entries 302 and secondary directory entries 304 .
- Each directory entry in the primary and secondary entries is typed.
- type values for the primary and secondary directory entries can correspond to a range of 1-255.
- Primary directory entries 302 correspond to the entries in the root directory of the file system.
- Secondary directory entries 304 follow a primary directory entry and are associated with the primary directory entry. Secondary directory entries extend the metadata associated with the correlated primary directory entry.
- the primary directory entries 302 can be further classified as critical primary directory entries 306 and benign primary directory entries 308 .
- Critical primary directory entries 306 define potentially different formats for each directory entry.
- an operating environment will not mount a volume corresponding to the extensible file system format with an unknown critical primary directory entry, as will be described below.
- Examples of known primary directory entries 306 can include allocation bitmaps, up-case tables, volume labels, encryption keys, and normal directory entries.
- Benign primary directory entries 308 also define potential different formats for each directory entry, but can be ignored by the file system if a particular benign primary directory entry is not understood. Benign primary directory entries 308 can be associated with another cluster chain the volume. Additionally, benign primary directory entries 308 can also be associated a number of secondary directory entries 304 .
- secondary directory entries 304 may also be further classified as critical secondary directory entries 310 and benign secondary directory entries 312 .
- the critical secondary directory entries 310 and benign secondary directory entries 312 are associated with a benign primary directory entry and extend the metadata associated with the primary directory entry. Both the critical secondary directory entries 310 and the benign secondary directory entries 312 can be associated with another cluster chain the volume.
- the file system implements a mount volume procedure.
- the mount volume procedure attempts to a look at a version number for the volume. If the version number is not understood (e.g., the version number is higher), the volume will not be mounted. During a normal directory enumeration, any critical primary directory entries not known by the file system will prevent the volume from being mounted. Thereafter, various user-initiated processes, such as a file open, will cause the file system to enumerate the secondary directory entries. If the critical secondary directory entries 310 are not known by a file system, the entire directory entry will be skipped. Additionally, if benign secondary directory entries 312 are not known by the file system, the particular unknown benign secondary directory entry will be ignored.
- the data components 400 include an OEM name component 402 for specifying a name for the file system format of the storage media.
- the data components 400 also include a data size descriptor component 404 for specifying various characteristics of the data stored in the file system.
- the data size descriptor component 404 can specify a count of bytes per sector, a number of sectors per allocation unit, a FAT table offset, and a count of sectors for all data structures.
- the data components include an active FAT flags component 406 for specifying a number of active FATs on the file system.
- a file system may support multiple FATs for utilization with some operating system environments.
- the data components 400 can further include a volume identification component 408 for identifying a volume serial number and/or version number. Still further, the data components 400 can include a file system type for specifying the file system format for the file system.
- the data components 400 can include a number of additional/alternative rows for implementing the above-identified components 402 - 410 and additional components.
- the data components 500 include an in use component 502 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use.
- the data components 500 further include a type designation component 504 for specifying that the directory entry is associated with a normal directory entry.
- the data components 500 further include a secondary directory entries component 504 for specifying a number of secondary entries associated with the normal directory entry.
- the data components 500 also include a file attributes component 508 for specifying various file system attributes for the directory entry.
- the data components 500 include a time component 510 for specifying various time information such as a creation timestamp, modification time stamp and other time information. Additionally, the data components 500 further include a time zone component 512 for specifying a time zone for the last created time stamp.
- a time component 510 for specifying various time information such as a creation timestamp, modification time stamp and other time information.
- the data components 500 further include a time zone component 512 for specifying a time zone for the last created time stamp.
- the data components 500 can include a number of additional/alternative rows for implementing the above-identified components 502 - 512 and additional components.
- the data components 600 include an in use component 602 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use.
- the data components 600 further include a type designation component 604 for specifying that the directory entry is associated with a file system name.
- the data components further include a file name length component 606 and a file name has component 608 . The utilization of the file name hash component 608 will be described below.
- the data components 600 also include a file name component 610 for specifying the file name.
- the data components 600 can include a number of additional/alternative rows for implementing the above-identified components 602 - 610 and additional components. Additionally, file name directory entries may be extended by secondary directory entries.
- the data components 700 include an in use component 702 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use.
- the data components 700 further include a type designation component 704 for specifying that the directory entry is associated with a volume identifier.
- the data components 700 further include a secondary directory entries component 706 for specifying a number of secondary entries associated with the volume identifier.
- the data components 700 also include a volume identifier 708 , such as a global unique identifier.
- the data components 700 can include a number of additional/alternative rows for implementing the above-identified components 702 - 708 and additional components. Additionally, in an illustrative embodiment, the data components 700 correspond to a benign directory entry that can be ignored by a file system that does not support volume identifiers.
- parties such as an OEM, may be able to define specific benign primary directory entry types 308 and benign secondary directory entry types 312 .
- parties such as an OEM, may be able to define specific benign primary directory entry types 308 and benign secondary directory entry types 312 .
- the file system could ignore the defined directory entry types.
- the data components 800 include an in use component 802 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use.
- the data components 800 further include a type designation component 804 for specifying that the directory entry is a benign primary directory entry.
- the data components 800 further include a secondary directory entries component 806 for specifying a number of secondary entries associated with the volume identifier.
- the data components 800 also include a volume identifier 808 , such as a global unique identifier.
- the data components 800 can further include additional information 810 , such as verification information and a starting cluster.
- additional information 810 such as verification information and a starting cluster.
- the data components 800 can include a number of additional/alternative rows for implementing the above-identified components 802 - 810 and additional components.
- the data components 900 include an in use component 902 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use.
- the data components 900 further include a type designation component 904 for specifying that the directory entry is a benign primary directory entry.
- the data components 900 further include a secondary directory entries component 906 for specifying a number of secondary entries associated with the volume identifier.
- the data components 900 also include a volume identifier 908 , such as a global unique identifier.
- the data components 900 can further include additional information 910 , such as verification information and a starting cluster.
- additional information 910 such as verification information and a starting cluster.
- the data components 900 can include a number of additional/alternative rows for implementing the above-identified components 902 - 906 and additional components.
- FIG. 10 is a block diagram illustrative of data components 1000 for implementing an access control list in an extensible file system format.
- the data components 1000 include an in use component 1002 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use.
- the data components 1000 further include a type designation component 1004 for specifying that the directory entry is an ACL directory entry.
- the data components 1000 further include a number of ACL fields 1006 , such as ACL flags, pointers to ACL databases, and the like.
- ACL access control list
- a file system obtains a request to create a directory entry with a specific file name.
- the specific file name can correspond to a naming convention, such as a digital camera picture naming convention.
- the file system generates a target name hash.
- the specific file name is converted via a conversion table (e.g. an UpCase Table) into a second string prior to generating the target name hash.
- a conversion table e.g. an UpCase Table
- an iterative loop is begun by examining the next directory entry hash value.
- An illustrative directory entry type for storing directory entry hash values is described above with regard to data components 600 ( FIG. 6 ).
- a test is conducted to determine whether the target hash value matches the current directory entry hash value. This enables implementations to perform a quick comparison when searching for a file by name. Importantly, the NameHash provides a sure verification of a mismatch. However, the NameHash does not provide a sure verification of a match. If they do not match, the routine 1100 returns to block 1106 (until all the directory entries have been examined. If the hash values match at decision block 1108 , at block 1110 , the file system obtains the full file name for the potentially matching directory entry. In some embodiments, this comparison is done by comparing the converted versions of the two file names.
- an embodiment may compare an Up-Cased version of the specific file name against an Up-Cased version of the full file name for the potentially matching directory entry.
- An illustrative directory entry type for storing directory entry full file names is described above with regard to data components 600 ( FIG. 6 ).
- a test is conducted to determine whether the target file name matches the full file name of the potentially matching directory entry. If so, the routine 1100 terminates by reporting a conflict and the file system will be required to select a new file name. If the full file does not match, the routine 1100 will return to block 1106 to continue checking hash values for the remaining directory entries.
- the target file name is first converted into a second string via a conversion table.
- the second string can be an up-cased version of the target file name
- the conversion table can be an Up-Case table.
- the conversion table is stored on the same one or more pieces of media that contain the directory entries.
- the calculation of the name hash can initialize a temporary value to a predetermined start value (e.g. zero). For each character of the second string, the temporary value can be rotated right by one bit, and then have the current character of the second string added to the temporary value.
- (Temp>>1); Temp + (UInt16)Buffer[Index]; ⁇ return Hash; ⁇
- the generating the name hash either the target file name or the second string may be determined to correspond to a naming convention, such as a digital camera picture naming convention, which uses the same prefix (e.g. “IMG”) for many file names.
- a naming convention such as a digital camera picture naming convention, which uses the same prefix (e.g. “IMG”) for many file names.
- the calculation of a hash value for a common prefix will always yield the same temporary value (i.e. partial hash) after the hash function includes the common prefix and before it includes the variable portion of the file name.
- a common prefix e.g. “IMG”, “IMG00”, “IMG01”, and the like
- the temporary value may instead be initialized to the pre-computed partial hash value corresponding to the common prefix.
- the remaining hash generating steps e.g. rotation and addition steps
- UInt16 NameHash (WCHAR * VariableString, UCHAR NumChar, UInt16 PrecomputedHash) ⁇
- UCHAR * Buffer (UCHAR *)VariableString;
- (Temp>>1); Temp + (UInt16)Buffer[Index]; ⁇ return Hash; ⁇
- the PrecomputedHash for a name where a portion of the file name does not have a common prefix the partial hash value may be a predetermined value (e.g. zero), thus allowing the same function to generate the hash for all file names. It will be appreciated that the same operations can be applied to directory entry names. As can be further appreciated, the conversion of the file name to the second string may occur as an integral part of the name hash generation, as opposed to occurring prior to the generation of the hash. For example, in psuedo-code based on the “C” language, the same result occurs with:
- a device only creates files with a limited set of file names (i.e. 10,000 files with names “DSCN0000.JPG”, “DSCN0001.JPG”, . . . “DSCN9999JPG”)
- some or all of these file names may have their hash fully precomputed and stored in a device's memory. Then, when determining if a file exists or creating a new file record, the corresponding precomputed final hash may be simply read from the device's memory.
- FIG. 12 illustrates an example of a suitable computing system environment 9900 on which embodiments of the invention may be implemented.
- the computing system environment 9900 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention. Neither should the computing environment 9900 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the example operating environment 9900 .
- Embodiments of the invention are operational with numerous other general purpose or special purpose computing system environments or configurations.
- Examples of well known computing systems, environments, and/or configurations that may be suitable for use with embodiments of the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices (such as mobile phones, media players, etc.), multiprocessor systems, microprocessor-based systems, set top boxes, consumer electronics (such as televisions, optical disk players, digital picture frames, etc.), media kiosks, network PCs, minicomputers, mainframe computers, telephony systems, distributed computing environments that include any of the above systems or devices, and the like.
- Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer.
- program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
- at least a portion of processes described above may be implemented by computer-executable instructions executable by one or more computing systems.
- Embodiments of the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
- program modules may be located in both local and remote computer storage media including memory storage devices.
- an example system for implementing embodiments of the invention includes a general-purpose computing device in the form of a computer 9910 .
- Components of computer 9910 may include, but are not limited to, a processing unit 9920 , a system memory 9930 , and a system bus 9921 that couples various system components including the system memory to the processing unit 9920 .
- the system bus 9921 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures.
- such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.
- ISA Industry Standard Architecture
- MCA Micro Channel Architecture
- EISA Enhanced ISA
- VESA Video Electronics Standards Association
- PCI Peripheral Component Interconnect
- Computer 9910 typically includes a variety of computer readable media.
- Computer readable media can be any available media that can be accessed by computer 9910 and includes both volatile and nonvolatile media, removable and non-removable media.
- Computer readable media may comprise computer storage media and communication media.
- Computer readable storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 9910 .
- Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
- the system memory 9930 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 9931 and random access memory (RAM) 9932 .
- ROM read only memory
- RAM random access memory
- BIOS basic input/output system 9933
- RAM 9932 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 9920 .
- FIG. 12 illustrates operating system 9934 , application programs 9935 , other program modules 9936 , and program data 9937 .
- the computer 9910 may also include other removable/non-removable volatile/nonvolatile computer storage media.
- FIG. 12 illustrates a hard disk drive 9941 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 9951 that reads from or writes to a removable, nonvolatile magnetic disk 9952 , and an optical disk drive 9955 that reads from or writes to a removable, nonvolatile optical disk 9956 such as a CD ROM or other optical media.
- removable/non-removable, volatile/nonvolatile computer storage media that can be used in the example operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like.
- the hard disk drive 9941 is typically connected to the system bus 9921 through a non-removable memory interface such as interface 9940
- magnetic disk drive 9951 and optical disk drive 9955 are typically connected to the system bus 9921 by a removable memory interface, such as interface 9950 .
- the drives and their associated computer storage media discussed above and illustrated in FIG. 12 provide storage of computer readable instructions, data structures, program modules and other data for the computer 9910 .
- hard disk drive 9941 is illustrated as storing operating system 9944 , application programs 9945 , other program modules 9946 , and program data 9947 .
- operating system 9944 application programs 9945 , other program modules 9946 , and program data 9947 are given different numbers here to illustrate that, at a minimum, they are different copies.
- a user may enter commands and information into the computer 9910 through input devices such as a keyboard 9962 , a microphone 9963 , and a pointing device 9961 , such as a mouse, trackball or touch pad.
- Other input devices may include a joystick, game pad, satellite dish, scanner, or the like.
- a monitor 9991 or other type of display device is also connected to the system bus 9921 via an interface, such as a video interface 9990 .
- computers may also include other peripheral output devices such as speakers 9997 and printer 9996 , which may be connected through an output peripheral interface 9990 .
- the computer 9910 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 9980 .
- the remote computer 9980 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 9910 .
- the logical connections depicted in FIG. 12 include a local area network (LAN) 9971 and a wide area network (WAN) 9973 , but may also include other networks.
- LAN local area network
- WAN wide area network
- Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
- the computer 9910 When used in a LAN networking environment, the computer 9910 is connected to the LAN 9971 through a network interface or adapter 9970 .
- the computer 9910 When used in a WAN networking environment, the computer 9910 typically includes a modem 9972 or other means for establishing communications over the WAN 9973 , such as the Internet.
- the modem 9972 which may be internal or external, may be connected to the system bus 9921 via the user input interface 9960 , or other appropriate mechanism.
- program modules depicted relative to the computer 9910 may be stored in the remote memory storage device.
- FIG. 12 illustrates remote application programs 9985 as residing on remote computer 9980 .
- network connections shown are example and other means of establishing a communications link between the computers may be used.
- various additional functionality may be added through the specification of specific directory types.
- name streams may be supported by specifying a name stream directory entry.
- on-disk encryption may also be supported through the utilization of specific encryption algorithms and key exchanges.
- time zone conversions may be associated with directory entries to automatically convert a current time zone with a time zone with the directory entry was made.
- file structures used in the file system described herein can be those described more fully in Appendix A.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Software Systems (AREA)
- Human Computer Interaction (AREA)
- Library & Information Science (AREA)
- Computer Security & Cryptography (AREA)
- Quality & Reliability (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
A method of updating a file record on at least one of a first one or more computer readable storage media including writing at least three contiguous DirectoryEntry data structures corresponding to a directory entry set, the directory entry set corresponding to a file, the writing occurring to the at least one of a first one or more computer readable storage media.
Description
- This application is a divisional of U.S. application Ser. No. 12/389,396, entitled QUICK FILENAME LOOKUP USING NAME HASH, filed on Feb. 20, 2009, which claims the benefit of U.S. Provisional Application No. 61/030,043, entitled FILE ALLOCATION TABLE, filed on Feb. 20, 2008;
- U.S. application Ser. No. 12/389,396 is a continuation-in-part of U.S. Non-Provisional application Ser. No. 11/229,485, entitled EXTENSIBLE FILE SYSTEM, filed on Sep. 16, 2005, which claims the benefit of U.S. Provisional Application No. 60/637,407, entitled FILE SYSTEM FORMAT FOR PORTABLE MEDIA, and filed on Dec. 17, 2004;
- The contents of U.S. application Ser. No. 12/389,396, U.S. application Ser. No. 11/229,485, U.S. Provisional Application No. 60/637,407, and U.S. Provisional Application No. 61/030,043 are incorporated by reference herein in their entirety.
- Generally described, there are a number of portable computing devices, such as digital still cameras, digital video cameras, media players, mobile phones, mobile computing devices, personal digital assistants, and the like that maintain data on a storage media, such as a portable storage media. The continued development of more complex portable computing devices and larger storage capacity portable storage media places a greater demand for flexibility on the file system format used on the storage media. Current file system format approaches can become deficient in that they may provide inadequate flexibility for increasing storage size capacities and/or storage media applications.
- An extensible file system format for portable storage media is provided. The extensible file system format includes the specification of primary and secondary directory entry types that may be custom defined. The primary and secondary directory entry types can be further classified as critical and benign directory entries.
- In some embodiments, a computer-readable medium having computer-executable components for storing data is provided. The computer-readable components can include specific structures for improving the efficiency of determining if a target file name exists. In some embodiments, determining if the target file name exists includes (1) determining a file name hash, (2) finding a directory entry set containing the same hash and a potentially matching filename, thus either reducing the set of possible directory entries or more quickly removing a directory entry from consideration, and (3) determining the target file name exists by matching its file name against the potentially matching filename. In some embodiments, target file name may be converted to an uppercase version of the filename, e.g. for operating systems which perform case-insensitive operations on files. In some embodiments, conversion to uppercase may be based on an Up-Case Table stored on the media. In some embodiments, the directory entry can be read from one or more computer readable storage media, and the file name hash is compared to the directory entry set name hash value. In some embodiments, determining the file name hash can include using a set of pre-calculated hash values for at least a portion of the target file name. For example, if the device only creates 1000 file names, it can lookup the corresponding file name hash from a pre-computed corresponding set of values instead of performing the calculation. In some embodiments, if the a portion of the file names commonly created by the device are the same (e.g., all files start with “IMG” followed by a four digit number), a portion of the hash can be precomputed (e.g., “IMG0”, “IMG1”, “IMG2”, “IMG”, etc.) to further reduce computation of the hash value. As would be appreciated, the above processes can enable determination if a file name exists by allowing a comparison of fixed-length file hashes prior to comparisons of variable-length strings.
- In some embodiments, a directory entry set on one or more computer-readable storage media is updated to contain information corresponding to a file. The directory entry set can be comprised of at least three contiguous DirectoryEntry data structures, the first of which can be a File DirectoryEntry data structure, the second can be a Stream Extension DirectoryEntry data structure, and the third can be a first File Name Extension DirectoryEntry data structure of a one or more contiguous File Name Extension DirectoryEntry data structures, the Stream Extension DirectoryEntry data structure can include a name hash field and a name length field, and the name length field can indicate the number of characters in the file name stored in the one or more contiguous File Name Extension DirectoryEntry data structures. In some embodiments, the DirectoryEntry data structures are all of the same fixed length, to further improve computational efficiencies.
- This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
- The foregoing aspects and many of the attendant advantages embodied herein will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
-
FIGS. 1A-1C are block diagrams illustrative of an illustrative environment including a portable computing device and a storage device implementing the extensible file system format in accordance with embodiments of the invention. -
FIG. 2 is a block diagram illustrative of various volume layout components corresponding to an extensible file system format in accordance with an embodiment of the invention. -
FIG. 3 is a block diagram illustrative of an extensible file system directory structures including primary and secondary directory entry structures in accordance with an embodiment of the invention. -
FIG. 4 is a block diagram illustrative of data components for implementing a boot process block in an extensible file system format in accordance with an embodiment of the invention. -
FIG. 5 is a block diagram illustrative of data components for implementing directory entries in an extensible file system format in accordance with an embodiment of the invention. -
FIG. 6 is a block diagram illustrative of data components for implementing a file name and extensions in an extensible file system format in accordance with an embodiment of the invention. -
FIG. 7 is a block diagram illustrative of data components for implementing a volume identifier in an extensible file system format in accordance with an embodiment of the invention. -
FIG. 8 is a block diagram illustrative of data components for implementing an extensible directory entry in an extensible file system format in accordance with an embodiment of the invention. -
FIG. 9 is a block diagram illustrative of data components for implementing an extensible directory entry in an extensible file system format in accordance with an embodiment of the invention. -
FIG. 10 is a block diagram illustrative of data components for implementing an access control list in an extensible file system format in accordance with an embodiment of the invention. -
FIG. 11 is a flow diagram illustrative of a file name creation routine for an extensible file system format in accordance with an embodiment of the invention. -
FIG. 12 is an example of a suitable computing system environment for an extensible file system format. - Generally described, the application relates to an extensible file system format and various processes associated with the extensible file system format. In an illustrative embodiment, the extensible file system format corresponds to an extensible file system format for portable storage media and various processes associated with the extensible file system format on the portable storage media. Although one aspect will be described with regard to a portable storage media file system format, one skilled in the relevant art will appreciate that the disclosed embodiments are illustrative in nature and should not be construed as limiting. Additionally, one skilled in the relevant art will appreciate that the data structures and data layouts used in the illustrative examples may require additional information related to performance, security, and the like.
- Extensible File Allocation Table (exFAT) is one illustrative embodiment of the disclosed file system. The exFAT embodiment retains both the simplicity and ease of implementation of other FAT-based file systems. In order to keep the simplicity of implementation, and in order to enable implementations on devices with limited memory and processor capacity, the file directory structure has been kept unsorted and “flat”. The exFAT embodiment also enables many files (e.g. up to 2,796,202) in a single directory. In order to find if a target file name exists in a “flat” unsorted directory structure (for example, to create, open, update, or delete a file with that name), a comparison of the target file name can be done against each file record (e.g. DirectoryEntry set). A string comparison can be more processor, power, and energy intensive than an integer comparison. Thus, by first creating a Name Hash based on the target file name, and then only performing a string comparison on file records (e.g. DirectoryEntry sets) which have a matching Name Hash, the speed and efficiency of the operation to find the matching target file name is improved. Similarly, by creating a Name Hash when creating or updating a directory entry for a file, the speed and efficiency of later operations to find this file by name can be improved. In addition, because some computing device systems perform case-insensitive file operations, in some embodiments the hash function can be based on a partly case-insensitive manner. In some embodiments, the file system can embed the lower-case to upper-case translation table on the media. Embedding the lower-case to upper-case translation table can provide support for unicode character mappings which may spring into existence or change in the future, without affecting the resulting hash on existing media. Additional details of an exFAT embodiment can be found more fully described in Appendix A, which begins at page 34.
-
FIGS. 1A-1C are block diagrams illustrative of various operating environments 100 for the extensible file system format. With reference toFIG. 1A , in an illustrative embodiment, the extensible file system format is utilized to store data from a computing device, such as amobile computing device 102, and a storage media, such as aportable storage media 104. In an illustrative embodiment, themobile computing device 102 can correspond to any one of a variety of computing devices, including but not limited to, portable computing devices, mobile telephones, personal digital assistants, music players, media players. The portable storage media can also include, but is not limited to, hard drives, flash media, micro-drives and other storage media. In an illustrative embodiment, the extensible file system on theportable storage media 104 does not have to include any type of executable or readable software components, such as an operating environment, utilized by themobile computing device 102. Alternatively, the extensible file system on theportable storage media 104 may include executable or readable software components used by themobile device 102. - In an illustrative embodiment, the
mobile computing device 102 may be in communication with other computing devices for collecting/exchanging data to be stored on theportable storage media 104. With reference toFIG. 1B , themobile computing device 102 may be in direct communication with anothercomputing device 106 andstorage media 108. In an illustrative embodiment, the direct communication can correspond to various wired and wireless communication methods. In an illustrative embodiment, theother storage media 108 is not required to be formatted in accordance with the extensible file system format. With reference toFIG. 1C , in a similar manner, themobile computing device 102 may also be in communication with anothercomputing device 110 andstorage media 112, via a network connection. In an illustrative embodiment, the network connection can correspond to local area network (LAN) and wide are network (WAN) connections. - With reference now to
FIG. 2 , an illustrative embodiment volume layout 200 for an extensible file system format will be described. The volume layout 200 includes a boot parameters component 202 that include various information related to a description of the file system parameters of the partition. In an illustrative embodiment, the boot parameters component 202 can include code for bootstrapping from a defined partition, fundamental file system parameters for the defined partition, and various error checking information. A data structure for defining at least a portion of the boot parameters will be described below with regard toFIG. 4 . - The volume layout 200 also includes an extensible parameters component, designated as OEM parameters 204, that define various additional data structures used in conjunction with the file system. In an illustrative embodiment, an original equipment manufacture (OEM) may specify various extensible data structures, such as performance parameters for a storage medium, that can be defined at time of manufacture. The volume layout 200 can further include a file
allocation table component 206 that defines file and directory allocations. In an illustrative embodiment, each entry in the fileallocation table component 206 corresponds to a 32-bit entry that represents an allocated cluster, an unallocated cluster or an unusable cluster. The volume layout 200 can still further include series of file data components 208A-208X that correspond to the data stored according to the file system format. Various data structures for defining a portion of the file data components 208A-208X will be defined with regard toFIGS. 3-10 . - Turning now to
FIG. 3 , in one aspect, thefile data components 208 may include one or more directory entries according to adirectory structure 300. In an illustrative embodiment,directory structure 300 is organized intoprimary directory entries 302 and secondary directory entries 304. Each directory entry in the primary and secondary entries is typed. For example, in an illustrative embodiment, type values for the primary and secondary directory entries can correspond to a range of 1-255.Primary directory entries 302 correspond to the entries in the root directory of the file system. Secondary directory entries 304 follow a primary directory entry and are associated with the primary directory entry. Secondary directory entries extend the metadata associated with the correlated primary directory entry. - With continued reference to
FIG. 3 , in an illustrative embodiment, theprimary directory entries 302 can be further classified as criticalprimary directory entries 306 and benignprimary directory entries 308. Criticalprimary directory entries 306 define potentially different formats for each directory entry. In an illustrative embodiment, an operating environment will not mount a volume corresponding to the extensible file system format with an unknown critical primary directory entry, as will be described below. Examples of knownprimary directory entries 306 can include allocation bitmaps, up-case tables, volume labels, encryption keys, and normal directory entries. Benignprimary directory entries 308 also define potential different formats for each directory entry, but can be ignored by the file system if a particular benign primary directory entry is not understood. Benignprimary directory entries 308 can be associated with another cluster chain the volume. Additionally, benignprimary directory entries 308 can also be associated a number of secondary directory entries 304. - In a manner similar to
primary directory entries 302, secondary directory entries 304 may also be further classified as criticalsecondary directory entries 310 and benignsecondary directory entries 312. As described above, the criticalsecondary directory entries 310 and benignsecondary directory entries 312 are associated with a benign primary directory entry and extend the metadata associated with the primary directory entry. Both the criticalsecondary directory entries 310 and the benignsecondary directory entries 312 can be associated with another cluster chain the volume. - To mount a corresponding to the extensible file system format, the file system implements a mount volume procedure. In an illustrative embodiment, the mount volume procedure attempts to a look at a version number for the volume. If the version number is not understood (e.g., the version number is higher), the volume will not be mounted. During a normal directory enumeration, any critical primary directory entries not known by the file system will prevent the volume from being mounted. Thereafter, various user-initiated processes, such as a file open, will cause the file system to enumerate the secondary directory entries. If the critical
secondary directory entries 310 are not known by a file system, the entire directory entry will be skipped. Additionally, if benignsecondary directory entries 312 are not known by the file system, the particular unknown benign secondary directory entry will be ignored. - With reference now to
FIG. 4 , a block diagram illustrative of data components 400 for implementing a boot process block in the boot parameters component 202 (FIG. 2 ) will be described. The data components 400 include anOEM name component 402 for specifying a name for the file system format of the storage media. The data components 400 also include a datasize descriptor component 404 for specifying various characteristics of the data stored in the file system. For example, the datasize descriptor component 404 can specify a count of bytes per sector, a number of sectors per allocation unit, a FAT table offset, and a count of sectors for all data structures. The data components include an activeFAT flags component 406 for specifying a number of active FATs on the file system. In an illustrative embodiment, a file system may support multiple FATs for utilization with some operating system environments. The data components 400 can further include avolume identification component 408 for identifying a volume serial number and/or version number. Still further, the data components 400 can include a file system type for specifying the file system format for the file system. One skilled in the relevant art will appreciate that the data components 400 can include a number of additional/alternative rows for implementing the above-identified components 402-410 and additional components. - Turning now to
FIG. 5 , a block diagram illustrative of data components 500 for implementing directory entries in an extensible file system format will be described. The data components 500 include an inuse component 502 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use. The data components 500 further include a type designation component 504 for specifying that the directory entry is associated with a normal directory entry. The data components 500 further include a secondary directory entries component 504 for specifying a number of secondary entries associated with the normal directory entry. The data components 500 also include a file attributescomponent 508 for specifying various file system attributes for the directory entry. Still further, the data components 500 include atime component 510 for specifying various time information such as a creation timestamp, modification time stamp and other time information. Additionally, the data components 500 further include atime zone component 512 for specifying a time zone for the last created time stamp. One skilled in the relevant art will appreciate that the data components 500 can include a number of additional/alternative rows for implementing the above-identified components 502-512 and additional components. - Turning now to
FIG. 6 , a blockdiagram data components 600 for implementing a file name and extensions will be described. Thedata components 600 include an inuse component 602 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use. Thedata components 600 further include atype designation component 604 for specifying that the directory entry is associated with a file system name. The data components further include a filename length component 606 and a file name hascomponent 608. The utilization of the filename hash component 608 will be described below. Thedata components 600 also include afile name component 610 for specifying the file name. One skilled in the relevant art will appreciate that thedata components 600 can include a number of additional/alternative rows for implementing the above-identified components 602-610 and additional components. Additionally, file name directory entries may be extended by secondary directory entries. - Turning now to
FIG. 7 , a block diagram illustrative ofdata components 700 for implementing a volume identifier in an extensible file system format is provided. Thedata components 700 include an inuse component 702 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use. Thedata components 700 further include atype designation component 704 for specifying that the directory entry is associated with a volume identifier. Thedata components 700 further include a secondarydirectory entries component 706 for specifying a number of secondary entries associated with the volume identifier. Thedata components 700 also include avolume identifier 708, such as a global unique identifier. One skilled in the relevant art will appreciate that thedata components 700 can include a number of additional/alternative rows for implementing the above-identified components 702-708 and additional components. Additionally, in an illustrative embodiment, thedata components 700 correspond to a benign directory entry that can be ignored by a file system that does not support volume identifiers. - With reference now to
FIGS. 8 and 9 , in an illustrative embodiment, parties, such as an OEM, may be able to define specific benign primarydirectory entry types 308 and benign secondary directory entry types 312. As discussed above, in the event the file system would not recognize or understand either the specific benign primarydirectory entry types 308 or benign secondary directory entry types 312, the file system could ignore the defined directory entry types. - With reference to
FIG. 8 , a block diagram illustrative ofdata components 800 for implementing an extensible benignprimary directory entry 308 in an extensible file system format will be described. Thedata components 800 include an inuse component 802 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use. Thedata components 800 further include atype designation component 804 for specifying that the directory entry is a benign primary directory entry. Thedata components 800 further include a secondarydirectory entries component 806 for specifying a number of secondary entries associated with the volume identifier. Thedata components 800 also include avolume identifier 808, such as a global unique identifier. Thedata components 800 can further includeadditional information 810, such as verification information and a starting cluster. One skilled in the relevant art will appreciate that thedata components 800 can include a number of additional/alternative rows for implementing the above-identified components 802-810 and additional components. - With reference to
FIG. 9 , a block diagram illustrative ofdata components 900 for implementing a benign secondary directory entry in an extensible file system format will be described. Thedata components 900 include an inuse component 902 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use. Thedata components 900 further include atype designation component 904 for specifying that the directory entry is a benign primary directory entry. Thedata components 900 further include a secondary directory entries component 906 for specifying a number of secondary entries associated with the volume identifier. Thedata components 900 also include avolume identifier 908, such as a global unique identifier. Thedata components 900 can further includeadditional information 910, such as verification information and a starting cluster. One skilled in the relevant art will appreciate that thedata components 900 can include a number of additional/alternative rows for implementing the above-identified components 902-906 and additional components. - In an illustrative embodiment, a benign primary directory entry and/or secondary directory entries may be associated with access control list (ACL) information.
FIG. 10 is a block diagram illustrative ofdata components 1000 for implementing an access control list in an extensible file system format. Thedata components 1000 include an inuse component 1002 for specifying whether the particular directory entry is in use. In an illustrative embodiment, the high bit of the data components will be set to “1” if the directory entry is in use. Thedata components 1000 further include atype designation component 1004 for specifying that the directory entry is an ACL directory entry. Thedata components 1000 further include a number ofACL fields 1006, such as ACL flags, pointers to ACL databases, and the like. One skilled in the relevant art will appreciate that thedata components 1000 can include a number of additional/alternative rows for implementing the above-identified components 1002-1006 and additional components. - With reference now to
FIG. 11 , a filename creation routine 1100 for an extensible file system format will be described. Atblock 1102, a file system obtains a request to create a directory entry with a specific file name. In an illustrative embodiment, the specific file name can correspond to a naming convention, such as a digital camera picture naming convention. Atblock 1104, the file system generates a target name hash. In some embodiments, the specific file name is converted via a conversion table (e.g. an UpCase Table) into a second string prior to generating the target name hash. Atblock 1106, an iterative loop is begun by examining the next directory entry hash value. An illustrative directory entry type for storing directory entry hash values is described above with regard to data components 600 (FIG. 6 ). - At
decision block 1108, a test is conducted to determine whether the target hash value matches the current directory entry hash value. This enables implementations to perform a quick comparison when searching for a file by name. Importantly, the NameHash provides a sure verification of a mismatch. However, the NameHash does not provide a sure verification of a match. If they do not match, the routine 1100 returns to block 1106 (until all the directory entries have been examined. If the hash values match atdecision block 1108, atblock 1110, the file system obtains the full file name for the potentially matching directory entry. In some embodiments, this comparison is done by comparing the converted versions of the two file names. For example, an embodiment may compare an Up-Cased version of the specific file name against an Up-Cased version of the full file name for the potentially matching directory entry. An illustrative directory entry type for storing directory entry full file names is described above with regard to data components 600 (FIG. 6 ). Atdecision block 1112, a test is conducted to determine whether the target file name matches the full file name of the potentially matching directory entry. If so, the routine 1100 terminates by reporting a conflict and the file system will be required to select a new file name. If the full file does not match, the routine 1100 will return to block 1106 to continue checking hash values for the remaining directory entries. - In some embodiments at
block 1104, when generating the name hash, the target file name is first converted into a second string via a conversion table. For example, the second string can be an up-cased version of the target file name, and the conversion table can be an Up-Case table. In some embodiments, the conversion table is stored on the same one or more pieces of media that contain the directory entries. The calculation of the name hash can initialize a temporary value to a predetermined start value (e.g. zero). For each character of the second string, the temporary value can be rotated right by one bit, and then have the current character of the second string added to the temporary value. - An example of code implementing one embodiment of the name hash generation written in psuedo-code based on the “C” language:
-
UInt16 NameHash(WCHAR * SecondString, UCHAR NumChar) { UCHAR * Buffer = (UCHAR *)FileName; UInt16 Temp =0; for (UInt16 Index = 0; Index < NumChar * 2; Index++) { Temp = ((Temp&1) ? 0x8000 : 0) | (Temp>>1); Temp += (UInt16)Buffer[Index]; } return Hash; } - In some embodiments at
block 1104, the generating the name hash, either the target file name or the second string may be determined to correspond to a naming convention, such as a digital camera picture naming convention, which uses the same prefix (e.g. “IMG”) for many file names. In some embodiments, the calculation of a hash value for a common prefix will always yield the same temporary value (i.e. partial hash) after the hash function includes the common prefix and before it includes the variable portion of the file name. In these embodiments, a common prefix (e.g. “IMG”, “IMG00”, “IMG01”, and the like) can have its corresponding partial hash value pre-computed. Thus, when computing the hash value for a second string with a common prefix, the temporary value may instead be initialized to the pre-computed partial hash value corresponding to the common prefix. The remaining hash generating steps (e.g. rotation and addition steps) would then be applied only to the variable portion of the file name, thus saving a few instruction cycles in the computation of the name hash of the target file name, while resulting in the same name hash. - An example of code implementing one embodiment of the name hash generation for a common prefix, written in psuedo-code based on the “C” language, is as follows:
-
UInt16 NameHash(WCHAR * VariableString, UCHAR NumChar, UInt16 PrecomputedHash) { UCHAR * Buffer = (UCHAR *)VariableString; UInt16 Temp = PrecomputedHash; for (UInt16 Index = 0; Index < NumChar * 2; Index++) { Temp = ((Temp&1) ? 0x8000 : 0) | (Temp>>1); Temp += (UInt16)Buffer[Index]; } return Hash; } - As can be appreciated, in the above example pseudo-code, the PrecomputedHash for a name where a portion of the file name does not have a common prefix, the partial hash value may be a predetermined value (e.g. zero), thus allowing the same function to generate the hash for all file names. It will be appreciated that the same operations can be applied to directory entry names. As can be further appreciated, the conversion of the file name to the second string may occur as an integral part of the name hash generation, as opposed to occurring prior to the generation of the hash. For example, in psuedo-code based on the “C” language, the same result occurs with:
-
UInt16 NameHash(WCHAR * TargetFileName, UCHAR NumChar) { UInt16 Temp =0; for (UInt16 Index = 0; Index < NumChar; Index++) { // convert the characters one at a time WCHAR x = UpCase(*TargetFileName); TargetFileName++; // apply both bytes to the hash BYTE *z = (BYTE*)&x; Temp = ((Temp&1) ? 0x8000 : 0) | (Temp>>1); Temp += (UInt16)(*z); z++; Temp = ((Temp&1) ? 0x8000 : 0) | (Temp>>1); Temp += (UInt16)(*z); } return Hash; } - Similarly, in some embodiments, if a device only creates files with a limited set of file names (i.e. 10,000 files with names “DSCN0000.JPG”, “DSCN0001.JPG”, . . . “DSCN9999JPG”), some or all of these file names may have their hash fully precomputed and stored in a device's memory. Then, when determining if a file exists or creating a new file record, the corresponding precomputed final hash may be simply read from the device's memory.
-
FIG. 12 illustrates an example of a suitablecomputing system environment 9900 on which embodiments of the invention may be implemented. Thecomputing system environment 9900 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of embodiments of the invention. Neither should thecomputing environment 9900 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in theexample operating environment 9900. - Embodiments of the invention are operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with embodiments of the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices (such as mobile phones, media players, etc.), multiprocessor systems, microprocessor-based systems, set top boxes, consumer electronics (such as televisions, optical disk players, digital picture frames, etc.), media kiosks, network PCs, minicomputers, mainframe computers, telephony systems, distributed computing environments that include any of the above systems or devices, and the like.
- Embodiments of the invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. In some embodiments of the invention, at least a portion of processes described above may be implemented by computer-executable instructions executable by one or more computing systems. Embodiments of the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
- With reference to
FIG. 12 , an example system for implementing embodiments of the invention includes a general-purpose computing device in the form of a computer 9910. Components of computer 9910 may include, but are not limited to, aprocessing unit 9920, a system memory 9930, and a system bus 9921 that couples various system components including the system memory to theprocessing unit 9920. The system bus 9921 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus. - Computer 9910 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 9910 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer readable storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 9910. Communication media typically embodies computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
- The system memory 9930 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 9931 and random access memory (RAM) 9932. A basic input/output system 9933 (BIOS), containing the basic routines that help to transfer information between elements within computer 9910, such as during start-up, is typically stored in ROM 9931.
RAM 9932 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on byprocessing unit 9920. By way of example, and not limitation,FIG. 12 illustratesoperating system 9934, application programs 9935, other program modules 9936, and program data 9937. - The computer 9910 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
FIG. 12 illustrates a hard disk drive 9941 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 9951 that reads from or writes to a removable, nonvolatile magnetic disk 9952, and an optical disk drive 9955 that reads from or writes to a removable, nonvolatileoptical disk 9956 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the example operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 9941 is typically connected to the system bus 9921 through a non-removable memory interface such as interface 9940, and magnetic disk drive 9951 and optical disk drive 9955 are typically connected to the system bus 9921 by a removable memory interface, such as interface 9950. - The drives and their associated computer storage media discussed above and illustrated in
FIG. 12 , provide storage of computer readable instructions, data structures, program modules and other data for the computer 9910. InFIG. 12 , for example, hard disk drive 9941 is illustrated as storing operating system 9944, application programs 9945, other program modules 9946, and program data 9947. Note that these components can either be the same as or different fromoperating system 9934, application programs 9935, other program modules 9936, and program data 9937. Operating system 9944, application programs 9945, other program modules 9946, and program data 9947 are given different numbers here to illustrate that, at a minimum, they are different copies. - A user may enter commands and information into the computer 9910 through input devices such as a keyboard 9962, a
microphone 9963, and a pointing device 9961, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to theprocessing unit 9920 through a user input interface 9960 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 9991 or other type of display device is also connected to the system bus 9921 via an interface, such as a video interface 9990. In addition to the monitor, computers may also include other peripheral output devices such as speakers 9997 and printer 9996, which may be connected through an output peripheral interface 9990. - The computer 9910 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 9980. The remote computer 9980 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 9910. The logical connections depicted in
FIG. 12 include a local area network (LAN) 9971 and a wide area network (WAN) 9973, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet. - When used in a LAN networking environment, the computer 9910 is connected to the LAN 9971 through a network interface or adapter 9970. When used in a WAN networking environment, the computer 9910 typically includes a modem 9972 or other means for establishing communications over the WAN 9973, such as the Internet. The modem 9972, which may be internal or external, may be connected to the system bus 9921 via the user input interface 9960, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 9910, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
FIG. 12 illustrates remote application programs 9985 as residing on remote computer 9980. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers may be used. In an example embodiment, various additional functionality may be added through the specification of specific directory types. For example, name streams may be supported by specifying a name stream directory entry. Additionally, on-disk encryption may also be supported through the utilization of specific encryption algorithms and key exchanges. Still further, time zone conversions may be associated with directory entries to automatically convert a current time zone with a time zone with the directory entry was made. - In an example embodiment, the file structures used in the file system described herein can be those described more fully in Appendix A.
- While illustrative embodiments have been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of that which is disclosed herein.
Claims (12)
1. One or more computer readable storage media having computer executable instructions that, when executed on at least one processor, configure the at least one processor to perform a method of updating a file record on at least one of a first one or more computer readable storage media, the method comprising:
writing at least three contiguous DirectoryEntry data structures corresponding to a directory entry set, the directory entry set corresponding to a file, the writing occurring to the at least one of a first one or more computer readable storage media,
a first of the at least three DirectoryEntry data structures is a File DirectoryEntry data structure;
a second of the at least three DirectoryEntry data structures is a Stream Extension DirectoryEntry data structure, the Stream Extension DirectoryEntry data structure contiguous to and immediately following the File DirectoryEntry data structure; and
the third of the at least three DirectoryEntry data structures is a first File Name Extension DirectoryEntry data structure, the File Name Extension DirectoryEntry data structure contiguous to and immediately following the Stream Extension DirectoryEntry data structure.
2. The one or more computer readable storage media of claim 1 , further comprising:
an EntryType field, the EntryType comprising:
an InUse field at bit offset seven and one bit in length;
a TypeCategory field at bit offset six and one bit in length;
a TypeImportance field at bit offset five and one bit in length; and
a TypeCode field at bit offset zero and one bit in length;
the File DirectoryEnty data structure comprising:
a first EntryType field at byte offset zero, one byte in length, set to the value 85h, indicating the TypeCode field is set to the value five, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value zero, and the InUse field is set to the value one;
a SecondaryCount field at byte offset one, one byte in length, having a value in the range one to 255 inclusive, the value corresponding to the number of the at least three DirectoryEntry data structures minus one; and
a SetChecksum field at byte offset two, two bytes in length, and corresponding to a checksum of the at least three DirectoryEntry data structures excluding the SetChecksum field;
the Stream Extension DirectoryEntry data structure comprising:
a second EntryType field at byte offset zero, one byte in length, and set to the value COh, indicating the TypeCode field is set to the value zero, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value one, and the InUse field is set to the value one;
a NameLength field at byte offset three and one byte in length; and
a NameHash field at byte offset four and two bytes in length;
the first File Name Extension DirectoryEntry data structure comprising:
a third EntryType field at byte offset zero, one byte in length, and set to the value Cl h, indicating the TypeCode field is set to the value one, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value one, and the InUse field is set to the value one; and
a FileName field at byte offset two and 30 bytes in length;
the NameLength field in the Stream Extension DirectoryEntry indicating the number of characters of a Unicode string in the FileName fields of a one or more contiguous File Name Extension DirectoryEntry data structures, not including any trailing NULL, the first of the one or more contiguous File Name Extension DirectoryEntry data structures being the first NameExtension DirectoryEntry; and
the value in the NameHash field corresponding to a hash calculated based on the Unicode string in the NameLength field.
3. The one or more computer readable storage media of claim 1 , the File DirectoryEntry data structure further comprising:
a SetChecksum field at byte offset two, two bytes in length, and corresponding to a checksum of the at least three DirectoryEntry data structures excluding the SetChecksum field.
4. The one or more computer readable storage media of claim 1 , further comprising:
reading the at least three contiguous DirectoryEntry data structures, the File DirectoryEntry data structure further comprising a SetChecksum field, the SetChecksum field at byte offset two and two bytes in length within the File DirectoryEntry data structure;
calculating a checksum corresponding to all bytes of the at least three contiguous DirectoryEntry data structures, except for the two bytes of the SetChecksum field;
updating the SetChecksum field in the File DirectoryEntry data structure after writing at least the File DirectoryEntry data structure.
5. In a computing device, a method
of updating a file record on at least one of a first one or more computer readable storage media, the method comprising:
writing at least three contiguous DirectoryEntry data structures corresponding to a directory entry set, the directory entry set corresponding to a file, the writing occurring to the at least one of a first one or more computer readable storage media,
a first of the at least three DirectoryEntry data structures is a File DirectoryEntry data structure;
a second of the at least three DirectoryEntry data structures is a Stream Extension DirectoryEntry data structure, the Stream Extension DirectoryEntry data structure contiguous to and immediately following the File DirectoryEntry data structure; and
the third of the at least three DirectoryEntry data structures is a first File Name Extension DirectoryEntry data structure, the File Name Extension DirectoryEntry data structure contiguous to and immediately following the Stream Extension DirectoryEntry data structure.
6. The method of claim 5 , further comprising:
an EntryType field, the EntryType field comprising:
an InUse field at bit offset seven and one bit in length;
a TypeCategory field at bit offset six and one bit in length;
a TypeImportance field at bit offset five and one bit in length; and
a TypeCode field at bit offset zero and one bit in length;
the File DirectoryEnty data structure comprising:
a first EntryType field at byte offset zero, one byte in length, set to the value 85h, indicating the TypeCode field is set to the value five, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value zero, and the InUse field is set to the value one;
a SecondaryCount field at byte offset one, one byte in length, having a value in the range one to 255 inclusive, the value corresponding to the number of the at least three DirectoryEntry data structures minus one; and
a SetChecksum field at byte offset two, two bytes in length, and corresponding to a checksum of the at least three DirectoryEntry data structures excluding the SetChecksum field;
the Stream Extension DirectoryEntry data structure comprising:
a second EntryType field at byte offset zero, one byte in length, and set to the value COh, indicating the TypeCode field is set to the value zero, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value one, and the InUse field is set to the value one;
a NameLength field at byte offset three and one byte in length; and
a NameHash field at byte offset four and two bytes in length;
the first File Name Extension DirectoryEntry data structure comprising:
a third EntryType field at byte offset zero, one byte in length, and set to the value Cl h, indicating the TypeCode field is set to the value one, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value one, and the InUse field is set to the value one; and
a FileName field at byte offset two and 30 bytes in length;
the NameLength field in the Stream Extension DirectoryEntry indicating the number of characters of a Unicode string in the FileName fields of a one or more contiguous File Name Extension DirectoryEntry data structures, not including any trailing NULL, the first of the one or more contiguous File Name Extension DirectoryEntry data structures being the first NameExtension DirectoryEntry; and
the value in the NameHash field corresponding to a hash calculated based on the Unicode string in the NameLength field.
7. The method of claim 5 , the File DirectoryEntry data structure further comprising:
a SetChecksum field at byte offset two, two bytes in length, and corresponding to a checksum of the at least three DirectoryEntry data structures excluding the SetChecksum field.
8. The method of claim 5 , further comprising:
reading the at least three contiguous DirectoryEntry data structures, the File DirectoryEntry data structure further comprising a SetChecksum field, the SetChecksum field at byte offset two and two bytes in length within the File DirectoryEntry data structure;
calculating a checksum corresponding to all bytes of the at least three contiguous DirectoryEntry data structures, except for the two bytes of the SetChecksum field;
updating the SetChecksum field in the File DirectoryEntry data structure after writing at least the File DirectoryEntry data structure.
9. A computing device having a memory that stores computer executable instructions and a processor for executing the instructions, the instructions, when executed by the processor, causing the device to perform operations for updating a file record on at least one of a first one or more computer readable storage media, the operations comprising:
writing at least three contiguous DirectoryEntry data structures corresponding to a directory entry set, the directory entry set corresponding to a file, the writing occurring to the at least one of a first one or more computer readable storage media,
a first of the at least three DirectoryEntry data structures is a File DirectoryEntry data structure;
a second of the at least three DirectoryEntry data structures is a Stream Extension DirectoryEntry data structure, the Stream Extension DirectoryEntry data structure contiguous to and immediately following the File DirectoryEntry data structure; and
the third of the at least three DirectoryEntry data structures is a first File Name Extension DirectoryEntry data structure, the File Name Extension DirectoryEntry data structure contiguous to and immediately following the Stream Extension DirectoryEntry data structure.
10. The device of claim 9 , further comprising:
an EntryType field, the EntryType field comprising:
an InUse field at bit offset seven and one bit in length;
a TypeCategory field at bit offset six and one bit in length;
a TypeImportance field at bit offset five and one bit in length; and
a TypeCode field at bit offset zero and one bit in length;
the File DirectoryEnty data structure comprising:
a first EntryType field at byte offset zero, one byte in length, set to the value 85h, indicating the TypeCode field is set to the value five, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value zero, and the InUse field is set to the value one;
a SecondaryCount field at byte offset one, one byte in length, having a value in the range one to 255 inclusive, the value corresponding to the number of the at least three DirectoryEntry data structures minus one; and
a SetChecksum field at byte offset two, two bytes in length, and corresponding to a checksum of the at least three DirectoryEntry data structures excluding the SetChecksum field;
the Stream Extension DirectoryEntry data structure comprising:
a second EntryType field at byte offset zero, one byte in length, and set to the value COh, indicating the TypeCode field is set to the value zero, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value one, and the InUse field is set to the value one;
a NameLength field at byte offset three and one byte in length; and
a NameHash field at byte offset four and two bytes in length;
the first File Name Extension DirectoryEntry data structure comprising:
a third EntryType field at byte offset zero, one byte in length, and set to the value Cl h, indicating the TypeCode field is set to the value one, the TypeImportance field is set to the value zero, the TypeCategory field is set to the value one, and the InUse field is set to the value one; and
a FileName field at byte offset two and 30 bytes in length;
the NameLength field in the Stream Extension DirectoryEntry indicating the number of characters of a Unicode string in the FileName fields of a one or more contiguous File Name Extension DirectoryEntry data structures, not including any trailing NULL, the first of the one or more contiguous File Name Extension DirectoryEntry data structures being the first NameExtension DirectoryEntry; and
the value in the NameHash field corresponding to a hash calculated based on the Unicode string in the NameLength field.
11. The device of claim 9 , the File DirectoryEntry data structure further comprising:
a SetChecksum field at byte offset two, two bytes in length, and corresponding to a checksum of the at least three DirectoryEntry data structures excluding the SetChecksum field.
12. The device of claim 9 , further comprising:
reading the at least three contiguous DirectoryEntry data structures, the File DirectoryEntry data structure further comprising a SetChecksum field, the SetChecksum field at byte offset two and two bytes in length within the File DirectoryEntry data structure;
calculating a checksum corresponding to all bytes of the at least three contiguous DirectoryEntry data structures, except for the two bytes of the SetChecksum field;
updating the SetChecksum field in the File DirectoryEntry data structure after writing at least the File DirectoryEntry data structure.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/685,018 US20130080485A1 (en) | 2004-12-17 | 2012-11-26 | Quick filename lookup using name hash |
US14/842,963 US10614032B2 (en) | 2004-12-17 | 2015-09-02 | Quick filename lookup using name hash |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US63740704P | 2004-12-17 | 2004-12-17 | |
US11/229,485 US9639554B2 (en) | 2004-12-17 | 2005-09-16 | Extensible file system |
US3004308P | 2008-02-20 | 2008-02-20 | |
US12/389,396 US8321439B2 (en) | 2004-12-17 | 2009-02-20 | Quick filename lookup using name hash |
US13/685,018 US20130080485A1 (en) | 2004-12-17 | 2012-11-26 | Quick filename lookup using name hash |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/389,396 Division US8321439B2 (en) | 2004-12-17 | 2009-02-20 | Quick filename lookup using name hash |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/842,963 Division US10614032B2 (en) | 2004-12-17 | 2015-09-02 | Quick filename lookup using name hash |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130080485A1 true US20130080485A1 (en) | 2013-03-28 |
Family
ID=40789823
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/389,396 Active 2027-03-09 US8321439B2 (en) | 2004-12-17 | 2009-02-20 | Quick filename lookup using name hash |
US13/685,018 Abandoned US20130080485A1 (en) | 2004-12-17 | 2012-11-26 | Quick filename lookup using name hash |
US14/842,963 Active 2028-01-27 US10614032B2 (en) | 2004-12-17 | 2015-09-02 | Quick filename lookup using name hash |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/389,396 Active 2027-03-09 US8321439B2 (en) | 2004-12-17 | 2009-02-20 | Quick filename lookup using name hash |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/842,963 Active 2028-01-27 US10614032B2 (en) | 2004-12-17 | 2015-09-02 | Quick filename lookup using name hash |
Country Status (1)
Country | Link |
---|---|
US (3) | US8321439B2 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140149344A1 (en) * | 2004-12-17 | 2014-05-29 | Microsoft Corporation | Contiguous File Allocation In An Extensible File System |
US9547657B2 (en) | 2014-02-18 | 2017-01-17 | Black Duck Software, Inc. | Methods and systems for efficient comparison of file sets |
US9558223B2 (en) | 2006-05-23 | 2017-01-31 | Microsoft Technology Licensing, Llc | Extending cluster allocations in an extensible file system |
US9575988B2 (en) | 2004-12-17 | 2017-02-21 | Microsoft Technology Licensing, Llc | Extensible file system |
US10256977B2 (en) | 2014-02-18 | 2019-04-09 | Synopsys, Inc. | Methods and systems for efficient representation of file sets |
US10614032B2 (en) | 2004-12-17 | 2020-04-07 | Microsoft Technology Licensing, Llc | Quick filename lookup using name hash |
Families Citing this family (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP5593254B2 (en) * | 2010-05-12 | 2014-09-17 | パナソニック株式会社 | Semiconductor memory device and semiconductor memory system |
DE102010033673A1 (en) * | 2010-08-06 | 2012-02-09 | Daimler Ag | A method of operating a media player and media player |
KR20140145879A (en) | 2013-06-14 | 2014-12-24 | 삼성전자주식회사 | Apparatas and method for mounting a file system of virtual block device in an electronic device |
US10417196B2 (en) | 2014-01-06 | 2019-09-17 | Tuxera Inc. | Systems and methods for fail-safe operations of storage devices |
WO2015102670A1 (en) | 2014-01-06 | 2015-07-09 | Tuxera Inc. | Systems and methods for fail-safe operations of storage devices |
US10089318B2 (en) * | 2014-12-30 | 2018-10-02 | Excalibur Ip, Llc | Contracting and/or de-contracting stored parameters |
US10430182B2 (en) | 2015-01-12 | 2019-10-01 | Microsoft Technology Licensing, Llc | Enhanced compression, encoding, and naming for resource strings |
US9886442B2 (en) | 2015-01-12 | 2018-02-06 | Microsoft Technology Licensing, Llc | Enhanced compression, encoding, and naming for resource strings |
US9467166B2 (en) | 2015-01-12 | 2016-10-11 | Microsoft Technology Licensing, Llc | Enhanced compression, encoding, and naming for resource strings |
US10467001B2 (en) | 2015-01-12 | 2019-11-05 | Microsoft Technology Licensing, Llc | Enhanced compression, encoding, and naming for resource strings |
CN106294193B (en) * | 2015-06-03 | 2019-10-15 | 杭州海康威视系统技术有限公司 | Store equipment and the piecemeal storage method based on the storage equipment |
US10372674B2 (en) * | 2015-10-16 | 2019-08-06 | International Business Machines Corporation | File management in a storage system |
CN106708724B (en) * | 2015-11-16 | 2019-06-14 | 致伸科技股份有限公司 | Test macro |
US10496607B2 (en) | 2016-04-01 | 2019-12-03 | Tuxera Inc. | Systems and methods for enabling modifications of multiple data objects within a file system volume |
US10614044B2 (en) * | 2016-07-07 | 2020-04-07 | Tuxera, Inc. | Systems and methods for performing data object renaming operations |
US20180032540A1 (en) * | 2016-07-28 | 2018-02-01 | Dell Products L.P. | Method and system for implementing reverse directory lookup using hashed file metadata |
US10776342B2 (en) * | 2016-11-18 | 2020-09-15 | Tuxena, Inc. | Systems and methods for recovering lost clusters from a mounted volume |
CN106599084A (en) * | 2016-11-21 | 2017-04-26 | 上海斐讯数据通信技术有限公司 | Database data synchronous input device and method |
CN107423291B (en) * | 2017-05-05 | 2020-12-29 | 腾讯科技(深圳)有限公司 | Data translation method and client device |
US11537561B2 (en) * | 2017-12-15 | 2022-12-27 | Microsoft Technology Licensing, Llc | Techniques for handling letter case in file systems |
CN108021717B (en) * | 2017-12-29 | 2020-12-01 | 成都三零嘉微电子有限公司 | Method for implementing lightweight embedded file system |
US11507533B2 (en) * | 2018-02-05 | 2022-11-22 | Huawei Technologies Co., Ltd. | Data query method and apparatus |
CN109062935A (en) * | 2018-06-14 | 2018-12-21 | 新华三技术有限公司 | A kind of method and apparatus of file operation |
US11423069B2 (en) * | 2018-09-19 | 2022-08-23 | Servicenow, Inc. | Data structures for efficient storage and updating of paragraph vectors |
CN114328375A (en) * | 2020-09-29 | 2022-04-12 | 伊姆西Ip控股有限责任公司 | Method, apparatus and computer program product for storage management |
CN112416879B (en) * | 2020-12-09 | 2023-08-04 | 成都傲梅科技有限公司 | NTFS file system-based block-level data deduplication method |
CN113377711B (en) * | 2021-06-29 | 2024-04-30 | 云洗电子商务有限公司 | Data processing method, device, equipment and computer readable storage medium |
WO2023113251A1 (en) * | 2021-12-16 | 2023-06-22 | 삼성전자주식회사 | Operation method of electronic device for file search, and electronic device thereof |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6286013B1 (en) * | 1993-04-01 | 2001-09-04 | Microsoft Corporation | Method and system for providing a common name space for long and short file names in an operating system |
Family Cites Families (162)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPS6019763A (en) | 1983-07-13 | 1985-01-31 | Sankyo Co Ltd | Production of azetidinone thioester compound |
US4780821A (en) | 1986-07-29 | 1988-10-25 | International Business Machines Corp. | Method for multiple programs management within a network having a server computer and a plurality of remote computers |
JPS63286941A (en) | 1987-05-20 | 1988-11-24 | Hitachi Ltd | File system managing system |
US5307494A (en) | 1987-08-05 | 1994-04-26 | Fuji Xerox Co., Ltd. | File name length augmentation method |
JP2606222B2 (en) | 1987-08-06 | 1997-04-30 | 富士ゼロックス株式会社 | File name length extension method |
JPH01315843A (en) | 1988-06-15 | 1989-12-20 | Matsushita Electric Ind Co Ltd | File name managing method |
JP2629034B2 (en) | 1988-11-30 | 1997-07-09 | 富士通株式会社 | File management method for data with identifiers of unlimited length |
CA1323448C (en) | 1989-02-24 | 1993-10-19 | Terrence C. Miller | Method and apparatus for translucent file system |
EP0618535B1 (en) | 1989-04-13 | 1999-08-25 | SanDisk Corporation | EEPROM card with defective cell substitution and cache memory |
US5083264A (en) | 1989-04-24 | 1992-01-21 | Xerox Corporation | Process and apparatus for saving and restoring critical files on the disk memory of an electrostatographic reproduction machine |
JPH0317753A (en) | 1989-06-14 | 1991-01-25 | Fuji Xerox Co Ltd | File access system |
GB8915875D0 (en) | 1989-07-11 | 1989-08-31 | Intelligence Quotient United K | A method of operating a data processing system |
US5363487A (en) | 1989-08-29 | 1994-11-08 | Microsoft Corporation | Method and system for dynamic volume tracking in an installable file system |
US5371885A (en) | 1989-08-29 | 1994-12-06 | Microsoft Corporation | High performance file system |
US5247658A (en) | 1989-10-31 | 1993-09-21 | Microsoft Corporation | Method and system for traversing linked list record based upon write-once predetermined bit value of secondary pointers |
US5202982A (en) | 1990-03-27 | 1993-04-13 | Sun Microsystems, Inc. | Method and apparatus for the naming of database component files to avoid duplication of files |
US5313446A (en) * | 1990-03-30 | 1994-05-17 | Canon Kabushiki Kaisha | Disc drive device having a head carriage |
US5201044A (en) | 1990-04-16 | 1993-04-06 | International Business Machines Corporation | Data processing method for file status recovery includes providing a log file of atomic transactions that may span both volatile and non volatile memory |
JPH0454541A (en) | 1990-06-21 | 1992-02-21 | Fujitsu Ltd | Processing system for generation of file name |
US5367671A (en) | 1990-09-25 | 1994-11-22 | International Business Machines Corp. | System for accessing extended object attribute (EA) data through file name or EA handle linkages in path tables |
JP2888958B2 (en) | 1990-10-20 | 1999-05-10 | 富士通株式会社 | File management method for partially rewritable storage media |
JPH04188239A (en) | 1990-11-22 | 1992-07-06 | Nec Software Ltd | File control system |
CA2067633C (en) | 1991-07-24 | 1996-10-01 | Eric Jonathan Bauer | Method and apparatus for accessing a computer-based file system |
CA2067650C (en) | 1991-07-24 | 1996-10-22 | Eric Jonathan Bauer | Method and apparatus for operating a computer-based file system |
US5359725A (en) | 1991-10-15 | 1994-10-25 | Time Warner Interactive Group, Inc. | Method of creating CD-ROM image of files of different format with proper directories to be read by respective operating systems |
US6256642B1 (en) | 1992-01-29 | 2001-07-03 | Microsoft Corporation | Method and system for file system management using a flash-erasable, programmable, read-only memory |
US5434974A (en) | 1992-03-30 | 1995-07-18 | International Business Machines Corporation | Name resolution for a multisystem network |
JPH0619771A (en) | 1992-04-20 | 1994-01-28 | Internatl Business Mach Corp <Ibm> | File management system of shared file by different kinds of clients |
US5421001A (en) | 1992-05-01 | 1995-05-30 | Wang Laboratories, Inc. | Computer method and apparatus for a table driven file interface |
US5469562A (en) | 1992-06-26 | 1995-11-21 | Digital Equipment Corporation | Durable atomic storage update manager |
JPH0619763A (en) | 1992-07-02 | 1994-01-28 | Nec Corp | File name/directory name extension system |
US5745902A (en) | 1992-07-06 | 1998-04-28 | Microsoft Corporation | Method and system for accessing a file using file names having different file name formats |
US5627996A (en) | 1992-08-19 | 1997-05-06 | At&T | Method and apparatus for accessing the same computer file using different file name formats |
JPH06103140A (en) | 1992-09-18 | 1994-04-15 | Pfu Ltd | File directory retrieval system |
US5596755A (en) | 1992-11-03 | 1997-01-21 | Microsoft Corporation | Mechanism for using common code to handle hardware interrupts in multiple processor modes |
JPH06290096A (en) | 1993-03-31 | 1994-10-18 | Matsushita Electric Ind Co Ltd | Pass name solving device |
EP0618540B1 (en) | 1993-04-01 | 2001-12-12 | Microsoft Corporation | Common name space for long and short filenames |
FR2705803B1 (en) | 1993-05-26 | 1995-07-07 | Gemplus Card Int | Method for writing information in a non-volatile memory. |
US5399725A (en) * | 1993-05-27 | 1995-03-21 | Bristol-Myers Squibb Co. | 7-oxabicycloheptane carboxylic acid prostaglandin analog intermediates useful in the preparation of anti-thrombotic and anti-vasospastic compounds and method for preparing same |
BR9405407A (en) | 1993-06-14 | 1999-09-08 | Sony Corp | Processes of administering a registration medium to perform the administration of the registration status of a digital data in relation to a registration medium, of establishing a registration area for the purpose of registering a digital data on a registration medium, and of registering a digital data record data on a recording medium, means for recording digital data on a recording medium, means for recording or reproducing a digital data, and a computer system for recording a digital data on a recording medium |
DE4323405A1 (en) | 1993-07-13 | 1995-01-19 | Sel Alcatel Ag | Access control method for a buffer memory and device for buffering data packets and switching center with such a device |
CA2126950A1 (en) | 1993-07-30 | 1995-01-31 | Bryan M. Willman | Booting a computer system using a last known good set of configuration data |
US5483652A (en) | 1994-01-24 | 1996-01-09 | Digital Equipment Corporation | Mechanism for locating without search discrete application resources known by common name only in a distributed network computing environment |
JPH07234879A (en) | 1994-02-24 | 1995-09-05 | Toshiba Corp | Information processor and data base retrieving method |
US6119151A (en) | 1994-03-07 | 2000-09-12 | International Business Machines Corp. | System and method for efficient cache management in a distributed file system |
US6081804A (en) * | 1994-03-09 | 2000-06-27 | Novell, Inc. | Method and apparatus for performing rapid and multi-dimensional word searches |
US5915129A (en) | 1994-06-27 | 1999-06-22 | Microsoft Corporation | Method and system for storing uncompressed data in a memory cache that is destined for a compressed file system |
US5574907A (en) | 1994-11-30 | 1996-11-12 | Microsoft Corporation | Two-pass defragmentation of compressed hard disk data with a single data rewrite |
US5745752A (en) | 1994-12-13 | 1998-04-28 | Microsoft Corporation | Dual namespace client having long and short filenames |
US6108759A (en) | 1995-02-23 | 2000-08-22 | Powerquest Corporation | Manipulation of partitions holding advanced file systems |
JP3509285B2 (en) | 1995-05-12 | 2004-03-22 | 富士通株式会社 | Compressed data management method |
US5699548A (en) | 1995-06-01 | 1997-12-16 | Intel Corporation | Method and apparatus for selecting a mode for updating external memory |
US5819275A (en) | 1995-06-07 | 1998-10-06 | Trusted Information Systems, Inc. | System and method for superimposing attributes on hierarchically organized file systems |
US5778168A (en) | 1995-09-11 | 1998-07-07 | Sun Microsystems, Inc. | Transaction device driver technique for a journaling file system to ensure atomicity of write operations to a computer mass storage device |
US5907672A (en) | 1995-10-04 | 1999-05-25 | Stac, Inc. | System for backing up computer disk volumes with error remapping of flawed memory addresses |
US5742818A (en) | 1995-12-15 | 1998-04-21 | Microsoft Corporation | Method and system of converting data from a source file system to a target file system |
US5761677A (en) | 1996-01-03 | 1998-06-02 | Sun Microsystems, Inc. | Computer system method and apparatus providing for various versions of a file without requiring data copy or log operations |
US6144969A (en) | 1996-02-09 | 2000-11-07 | Sony Corporation | File name conversion |
US5732268A (en) | 1996-02-26 | 1998-03-24 | Award Software International | Extended BIOS adapted to establish remote communication for diagnostics and repair |
US5761675A (en) | 1996-03-19 | 1998-06-02 | Symantec Corporation | Diagnosis and repair of defective long filenames |
JPH1055269A (en) * | 1996-08-08 | 1998-02-24 | Fuji Xerox Co Ltd | Information processor |
US5734340A (en) | 1996-08-27 | 1998-03-31 | Symantech Corporation | Method and apparatus for storing run-intensive information in compact form |
US5923884A (en) | 1996-08-30 | 1999-07-13 | Gemplus S.C.A. | System and method for loading applications onto a smart card |
US5754848A (en) | 1996-09-11 | 1998-05-19 | Hewlett-Packard Co. | Apparatus and method for disaster recovery of an operating system utilizing long file and directory names |
US5832515A (en) | 1996-09-12 | 1998-11-03 | Veritas Software | Log device layered transparently within a filesystem paradigm |
US5765169A (en) | 1996-09-30 | 1998-06-09 | International Business Machines Corporation | Method and apparatus for converting long file names to short file names |
US6035379A (en) | 1997-01-09 | 2000-03-07 | Microsoft Corporation | Transaction processing for user data employing both logging and shadow copying |
US6023744A (en) | 1997-03-07 | 2000-02-08 | Microsoft Corporation | Method and mechanism for freeing disk space in a file system |
JPH10326107A (en) | 1997-03-25 | 1998-12-08 | Mitsubishi Electric Corp | Method and system for servocontrol |
US5930828A (en) | 1997-03-26 | 1999-07-27 | Executive Software International | Real-time apparatus and method for minimizing disk fragmentation in a computer system |
US6253300B1 (en) | 1997-08-20 | 2001-06-26 | Powerquest Corporation | Computer partition manipulation during imaging |
US6049807A (en) | 1997-09-03 | 2000-04-11 | International Business Machines Corporation | Technique for maintaining object integrity during modification of a persistent store of objects |
US6032223A (en) | 1997-10-15 | 2000-02-29 | Dell Usa, L.P. | System and method for determining a RAM disk logical drive designation |
US6374268B1 (en) | 1998-04-14 | 2002-04-16 | Hewlett-Packard Company | Methods and systems for an incremental file system |
US6038636A (en) | 1998-04-27 | 2000-03-14 | Lexmark International, Inc. | Method and apparatus for reclaiming and defragmenting a flash memory device |
DE19826091A1 (en) | 1998-06-12 | 1999-12-16 | Alcatel Sa | Method for securely changing data stored in a database, database system and network element equipped with it |
JP2000020365A (en) | 1998-07-07 | 2000-01-21 | Matsushita Electric Ind Co Ltd | Data processor and file managing method therefor |
US6377958B1 (en) | 1998-07-15 | 2002-04-23 | Powerquest Corporation | File system conversion |
EP2200032A3 (en) | 1998-09-18 | 2010-09-22 | Kabushiki Kaisha Toshiba | Information recording method, information recording device, and information recording medium |
US6205558B1 (en) | 1998-10-07 | 2001-03-20 | Symantec Corporation | Recovery of file systems after modification failure |
TW463107B (en) | 1998-12-22 | 2001-11-11 | Ibm | Extended card file system |
US7380140B1 (en) | 1998-12-30 | 2008-05-27 | Spyrus, Inc. | Providing a protected volume on a data storage device |
US6510552B1 (en) | 1999-01-29 | 2003-01-21 | International Business Machines Corporation | Apparatus for keeping several versions of a file |
US6922708B1 (en) | 1999-02-18 | 2005-07-26 | Oracle International Corporation | File system that supports transactions |
US6427123B1 (en) | 1999-02-18 | 2002-07-30 | Oracle Corporation | Hierarchical indexing for accessing hierarchically organized information in a relational system |
US6754696B1 (en) | 1999-03-25 | 2004-06-22 | Micosoft Corporation | Extended file system |
US6374265B1 (en) | 1999-03-29 | 2002-04-16 | Inventec Corp. | Method for backup and recovery of the long filename in computer system |
US6654772B1 (en) | 1999-04-28 | 2003-11-25 | Emc Corporation | Multi-volume extent based file system |
IL129947A (en) | 1999-05-13 | 2003-06-24 | Tadiran Telecom Business Syste | Method and apparatus for downloading software into an embedded system |
FI991262A (en) * | 1999-06-02 | 2000-12-03 | Nokia Networks Oy | Memory based on digital tree structure |
JP5113967B2 (en) | 1999-08-05 | 2013-01-09 | オラクル・インターナショナル・コーポレイション | Internet file system |
US7620620B1 (en) | 1999-08-05 | 2009-11-17 | Oracle International Corporation | Basing directory contents on a query that is associated with a file identifier |
CN100442393C (en) | 1999-10-21 | 2008-12-10 | 松下电器产业株式会社 | A semiconductor memory card access apparatus, a computer-readable recording medium, an initialization method, and a semiconductor memory card |
JP2001117821A (en) | 1999-10-22 | 2001-04-27 | Sony Corp | Recording medium, editing device, and recording system |
ES2190928T3 (en) | 1999-11-12 | 2003-09-01 | Ricoh Kk | SYSTEM TO TREAT QUESTIONS STORED AS DOCUMENTS THAT CAN BE SEARCHED IN A DOCUMENT MANAGEMENT SYSTEM. |
US6567887B2 (en) | 2000-01-03 | 2003-05-20 | Texas Instruments Incorporated | Buffering of partition tables, file system directory structures and individual file cluster chains in a mass storage device |
US6470345B1 (en) | 2000-01-04 | 2002-10-22 | International Business Machines Corporation | Replacement of substrings in file/directory pathnames with numeric tokens |
US6615365B1 (en) | 2000-03-11 | 2003-09-02 | Powerquest Corporation | Storing a computer disk image within an imaged partition |
US7216251B2 (en) | 2000-02-19 | 2007-05-08 | Powerquest Corporation | Computer imaging recovery without a working partition or a secondary medium |
JP4452363B2 (en) | 2000-02-23 | 2010-04-21 | 富士通株式会社 | File system |
US6856993B1 (en) | 2000-03-30 | 2005-02-15 | Microsoft Corporation | Transactional file system |
CN100442247C (en) | 2000-05-04 | 2008-12-10 | Nxp股份有限公司 | Method, system and computer program for data management on storage medium |
JP2001325134A (en) | 2000-05-15 | 2001-11-22 | Sony Corp | Directory setting method and recorder |
US6681386B1 (en) | 2000-05-22 | 2004-01-20 | International Business Machines Corporation | Method, system, and program for parameter expansion, generation, and execution of scripts in a networked environment |
US7043472B2 (en) | 2000-06-05 | 2006-05-09 | International Business Machines Corporation | File system with access and retrieval of XML documents |
US6658437B1 (en) | 2000-06-05 | 2003-12-02 | International Business Machines Corporation | System and method for data space allocation using optimized bit representation |
US6675180B2 (en) | 2000-06-06 | 2004-01-06 | Matsushita Electric Industrial Co., Ltd. | Data updating apparatus that performs quick restoration processing |
US6789094B2 (en) | 2000-07-25 | 2004-09-07 | Sun Microsystems, Inc. | Method and apparatus for providing extended file attributes in an extended attribute namespace |
US7092870B1 (en) * | 2000-09-15 | 2006-08-15 | International Business Machines Corporation | System and method for managing a textual archive using semantic units |
JP3899795B2 (en) | 2000-09-21 | 2007-03-28 | 日本電気株式会社 | File management system and method |
US6571259B1 (en) | 2000-09-26 | 2003-05-27 | Emc Corporation | Preallocation of file system cache blocks in a data storage system |
JP2002132566A (en) | 2000-10-27 | 2002-05-10 | Ntt Me Corp | Data management system and method, and computer readable recording medium |
US7058667B2 (en) | 2000-12-27 | 2006-06-06 | Microsoft Corporation | Method and system for creating and maintaining version-specific properties in a file |
US7383288B2 (en) | 2001-01-11 | 2008-06-03 | Attune Systems, Inc. | Metadata based file switch and switched file system |
US7062602B1 (en) | 2001-04-09 | 2006-06-13 | Matrix Semiconductor, Inc. | Method for reading data in a write-once memory device using a write-many file system |
US6889233B2 (en) | 2001-06-18 | 2005-05-03 | Microsoft Corporation | Selective file purging for delete or rename |
US20030028765A1 (en) | 2001-07-31 | 2003-02-06 | Cromer Daryl Carvis | Protecting information on a computer readable medium |
US6973463B2 (en) | 2001-11-06 | 2005-12-06 | Sun Microsystems, Inc. | Replication architecture for a directory server |
US6883114B2 (en) | 2001-11-08 | 2005-04-19 | M-Systems Flash Disk Pioneers Ltd. | Block device driver enabling a ruggedized file system |
JP2003162709A (en) | 2001-11-27 | 2003-06-06 | Canon Inc | Image processor, image pickup unit, image processing system, image managing method, storage medium, and its program |
GB0129044D0 (en) | 2001-12-05 | 2002-01-23 | Koninkl Philips Electronics Nv | Data storage methods and apparatuses with basic and extended file system capacity |
JP4108973B2 (en) | 2001-12-26 | 2008-06-25 | 株式会社日立製作所 | Backup system |
US7274857B2 (en) | 2001-12-31 | 2007-09-25 | Scientific-Atlanta, Inc. | Trick modes for compressed video streams |
JP2003248582A (en) * | 2002-02-26 | 2003-09-05 | Fujitsu Ltd | Execution environment construction processing method and execution environment construction processing program |
US7890554B2 (en) | 2002-03-14 | 2011-02-15 | International Business Machines Corporation | Apparatus and method of exporting file systems without first mounting the file systems |
US7007046B2 (en) | 2002-03-19 | 2006-02-28 | Network Appliance, Inc. | Format for transmission file system information between a source and a destination |
JP3848209B2 (en) | 2002-05-23 | 2006-11-22 | 株式会社東芝 | Data transfer device, data transfer method and program |
US8447963B2 (en) | 2002-06-12 | 2013-05-21 | Bladelogic Inc. | Method and system for simplifying distributed server management |
US7519984B2 (en) | 2002-06-27 | 2009-04-14 | International Business Machines Corporation | Method and apparatus for handling files containing confidential or sensitive information |
US7444317B2 (en) | 2002-06-28 | 2008-10-28 | Microsoft Corporation | System and method for managing file names for file system filter drivers |
KR100484147B1 (en) | 2002-07-26 | 2005-04-18 | 삼성전자주식회사 | Flash memory management method |
US6775751B2 (en) | 2002-08-06 | 2004-08-10 | International Business Machines Corporation | System and method for using a compressed main memory based on degree of compressibility |
US6792518B2 (en) | 2002-08-06 | 2004-09-14 | Emc Corporation | Data storage system having mata bit maps for indicating whether data blocks are invalid in snapshot copies |
AU2003267284A1 (en) | 2002-09-18 | 2004-04-08 | Netezza Corporation | Disk mirror architecture for database appliance |
US7287046B2 (en) * | 2002-09-30 | 2007-10-23 | Emc Corporation | Method and system of compacting sparse directories in a file system |
US7174420B2 (en) | 2002-10-22 | 2007-02-06 | Microsoft Corporation | Transaction-safe FAT file system |
US7363540B2 (en) | 2002-10-22 | 2008-04-22 | Microsoft Corporation | Transaction-safe FAT file system improvements |
US7032107B2 (en) | 2002-10-30 | 2006-04-18 | Symantec Corporation | Virtual partition for recording and restoring computer data files |
US7051251B2 (en) | 2002-12-20 | 2006-05-23 | Matrix Semiconductor, Inc. | Method for storing data in a write-once memory array using a write-many file system |
JP4401666B2 (en) | 2003-03-24 | 2010-01-20 | 池上通信機株式会社 | Digital image recording apparatus and image viewer apparatus |
US7072917B2 (en) | 2003-04-24 | 2006-07-04 | Neopath Networks, Inc. | Extended storage capacity for a network file server |
US7877426B2 (en) | 2003-07-17 | 2011-01-25 | International Business Machines Corporation | Performance-enhancing system and method of accessing file system objects |
US20050172005A1 (en) | 2004-01-30 | 2005-08-04 | Goodwin Kevin M. | Forestalling use of duplicate volume identifiers |
US7523343B2 (en) * | 2004-04-30 | 2009-04-21 | Microsoft Corporation | Real-time file system repairs |
US8352697B2 (en) | 2004-05-17 | 2013-01-08 | Sandisk Il Ltd. | Method of managing files for optimal performance |
US7444359B2 (en) | 2004-06-17 | 2008-10-28 | International Business Machines Corporation | Method and system for checking availability of automounted file systems |
US8607016B2 (en) | 2004-07-21 | 2013-12-10 | Sandisk Technologies Inc. | FAT analysis for optimized sequential cluster management |
JP4113524B2 (en) | 2004-09-13 | 2008-07-09 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Cache memory system and control method thereof |
US7380157B2 (en) | 2004-10-27 | 2008-05-27 | Pillar Data Systems, Inc. | Staggered writing for data storage systems |
US7284085B2 (en) | 2004-11-01 | 2007-10-16 | Emulex Design & Manufacturing Corporation | Managing configuration data in a flash configuration space in flash memory within a host interface port |
US7873596B2 (en) | 2006-05-23 | 2011-01-18 | Microsoft Corporation | Extending cluster allocations in an extensible file system |
US9639554B2 (en) | 2004-12-17 | 2017-05-02 | Microsoft Technology Licensing, Llc | Extensible file system |
ZA200509273B (en) | 2004-12-17 | 2008-12-31 | Microsoft Corp | Extensible file system |
US8321439B2 (en) | 2004-12-17 | 2012-11-27 | Microsoft Corporation | Quick filename lookup using name hash |
US8606830B2 (en) | 2004-12-17 | 2013-12-10 | Microsoft Corporation | Contiguous file allocation in an extensible file system |
US7363298B2 (en) * | 2005-04-01 | 2008-04-22 | Microsoft Corporation | Optimized cache efficiency behavior |
EP1814046A3 (en) | 2006-01-25 | 2008-12-24 | Océ-Technologies B.V. | System and method providing a file list display function and a file name generation function |
US7478217B2 (en) | 2006-04-07 | 2009-01-13 | Mediatek Inc. | Method of storing both large and small files in a data storage device and data storage device thereof |
US7941435B2 (en) * | 2006-08-01 | 2011-05-10 | Cisco Technology, Inc. | Substring search algorithm optimized for hardware acceleration |
US7685171B1 (en) | 2006-09-22 | 2010-03-23 | Emc Corporation | Techniques for performing a restoration operation using device scanning |
US7613738B2 (en) | 2007-01-16 | 2009-11-03 | Microsoft Corporation | FAT directory structure for use in transaction safe file system |
US7747664B2 (en) | 2007-01-16 | 2010-06-29 | Microsoft Corporation | Storage system format for transaction safe file system |
-
2009
- 2009-02-20 US US12/389,396 patent/US8321439B2/en active Active
-
2012
- 2012-11-26 US US13/685,018 patent/US20130080485A1/en not_active Abandoned
-
2015
- 2015-09-02 US US14/842,963 patent/US10614032B2/en active Active
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6286013B1 (en) * | 1993-04-01 | 2001-09-04 | Microsoft Corporation | Method and system for providing a common name space for long and short file names in an operating system |
Non-Patent Citations (1)
Title |
---|
Sans Institute InfoSec Reading Room. "Reverse Engineering the Microsoft exFAT File System." 12/1/2009. https://www.sans.org/reading-room/whitepapers/forensics/reverse-engineering-microsoft-exfat-file-system-33274 * |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140149344A1 (en) * | 2004-12-17 | 2014-05-29 | Microsoft Corporation | Contiguous File Allocation In An Extensible File System |
US9575988B2 (en) | 2004-12-17 | 2017-02-21 | Microsoft Technology Licensing, Llc | Extensible file system |
US9575972B2 (en) * | 2004-12-17 | 2017-02-21 | Microsoft Technology Licensing, Llc | Contiguous file allocation in an extensible file system |
US9639554B2 (en) | 2004-12-17 | 2017-05-02 | Microsoft Technology Licensing, Llc | Extensible file system |
US10303650B2 (en) | 2004-12-17 | 2019-05-28 | Microsoft Technology Licensing, Llc | Contiguous file allocation in an extensible file system |
US10474641B2 (en) | 2004-12-17 | 2019-11-12 | Microsoft Technology Licensing, Llc | Extensible file system |
US10614032B2 (en) | 2004-12-17 | 2020-04-07 | Microsoft Technology Licensing, Llc | Quick filename lookup using name hash |
US9558223B2 (en) | 2006-05-23 | 2017-01-31 | Microsoft Technology Licensing, Llc | Extending cluster allocations in an extensible file system |
US10585868B2 (en) | 2006-05-23 | 2020-03-10 | Microsoft Technology Licensing, Llc | Extending cluster allocations in an extensible file system |
US9547657B2 (en) | 2014-02-18 | 2017-01-17 | Black Duck Software, Inc. | Methods and systems for efficient comparison of file sets |
US10256977B2 (en) | 2014-02-18 | 2019-04-09 | Synopsys, Inc. | Methods and systems for efficient representation of file sets |
Also Published As
Publication number | Publication date |
---|---|
US8321439B2 (en) | 2012-11-27 |
US20150370821A1 (en) | 2015-12-24 |
US10614032B2 (en) | 2020-04-07 |
US20090164440A1 (en) | 2009-06-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20130080485A1 (en) | Quick filename lookup using name hash | |
US10474641B2 (en) | Extensible file system | |
US10303650B2 (en) | Contiguous file allocation in an extensible file system | |
US8027961B2 (en) | System and method for composite record keys ordered in a flat key space for a distributed database | |
US8862555B1 (en) | Methods and apparatus for generating difference files | |
US20190179948A1 (en) | Storing unstructured data in a structured framework | |
EP1076301B1 (en) | Apparatus and method for loading objects from a primary memory hash index | |
US8498965B1 (en) | Methods and apparatus for generating difference files | |
WO2022148055A1 (en) | File retrieval method and computing device | |
US20070174238A1 (en) | Indexing and searching numeric ranges | |
WO2021174836A1 (en) | Differential package generation method and apparatus, computer device, and storage medium | |
JP2011215835A (en) | Storage device having full-text search function | |
CN116361287A (en) | Path analysis method, device and system | |
US20120259897A1 (en) | Determination of landmarks | |
JP2013030189A (en) | Storage device provided with full-text search function |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034544/0541 Effective date: 20141014 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |