MAPPING LONG NAMES IN A FILESYSTEM

• US 20130290383A1
• Filed: 04/30/2012
• Published: 10/31/2013
• Est. Priority Date: 04/30/2012
• Status: Abandoned Application

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Nitin, Jain, Tucek, Joseph A., Anderson, Eric A
• Application Number:
  US13/460,167
• Publication Number:
  US 20130290383A1
• Time in Patent Office: Days
• US Class Current: 707/822
• CPC Class Codes: G06F 16/137 Hash-based content-based indexing of textual data G06F16/31

Abstract

Mapping long names in a filesystem is disclosed. An example method includes hashing a long file name, and storing a file with the hashed file name. Another example method includes splitting a long file name into at least two parts, and encoding the at least two parts of the long file name as directory structures in the filesystem.

Claims

1. A method of mapping long names in a filesystem, comprising:

hashing a long file name; and

storing file content with the hashed file name.

2. The method of claim 1, further comprising splitting the long file name into at least two parts using hash chaining.

3. The method of claim 2, further comprising replacing ‘

/’

with bytes not yet used in a legitimate filename.

4. The method of claim 3, wherein the ‘

/’

bytes are replaced with 0xff or 0xfe in binary format.

5. The method of claim 2, further comprising storing the file content in a first file and creating empty files for remaining file names.

6. The method of claim 2, further comprising storing the file content in a first file and remaining file names having first two bytes as ‘

dot and hexadecimal 0xff or 0xfe’

so that the remaining file names are hidden and not mistaken as user-created files.

7. The method of claim 2, further comprising storing a full filename in fake files.

8. The method of claim 2, further comprising using symbolic links to chain remaining file names together.

9. The method of claim 1, further comprising after hashing the long file name, creating a first file to store file content and a second file to store the long file name.

10. A method of mapping long names in a filesystem, comprising:

splitting a long file name into at least two parts; and

encoding the at least two parts of the long file name as directory structures in the filesystem.

11. The method of claim 10, wherein all but one of the at least two parts of the long file name has a length equal to a maximum allowed number of bytes minus one.

12. The method of claim 11, wherein a last one of the at least two parts of the long file name is less than or equal to the maximum allowed number of bytes minus one.

13. The method of claim 11, further comprising using a non-UTF-8 character to distinguish between a normal file name and the long file name.

14. The method of claim 11, wherein encoding comprises creating subdirectories for each of the at least two parts of the long file name.

15. The method of claim 14, further comprising storing file content under an innermost subdirectory.

16. The method of claim 10, further comprising encoding the long file name with a special character set before splitting the long file name.

17. The method of claim 16, wherein the special character set excludes ‘

/’

.

18. The method of claim 16, wherein characters are selected from the special character set in ASCII-betical order.

19. The method of claim 16, wherein a directory at every second level mitigates imposition of a maximum number of directories by the filesystem.

20. The method of claim 16, further comprising creating a directory after every two characters and appending the directory with a character not used in the encoding.