rt/snapraid
1
0
Fork 0
mirror of https://github.com/amadvance/snapraid.git synced 2026-10-26 10:51:54 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Adds a comment about not using inode order by default.

Browse source
This commit is contained in:
Andrea Mazzoleni 2014-04-03 22:52:53 +02:00
parent 641b818432
commit dde48ca299
1 changed files with 9 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

11
cmdline/unix.c
View file

@ -180,7 +180,7 @@ int filephy(const char* path, struct stat* st, uint64_t* physical)
return 0;
}
/* otherwise don't use anything, and keep the existing order */
/* otherwise don't use anything, and keep the directory traversal order */
/* at now this should happen only for vfat */
/* and it's surely better than using fake inodes */
*physical = FILEPHY_UNREPORTED_OFFSET;
@ -188,7 +188,14 @@ int filephy(const char* path, struct stat* st, uint64_t* physical)
return -1;
#else
/* In a generic Unix use a dummy value for all the files */
/* We don't want to risk to use the inode without knowing if it really improves performance */
/* We don't want to risk to use the inode without knowing */
/* if it really improves performance. */
/* In this way we keep them in the directory traversal order */
/* that at least keeps files in the same directory together. */
/* Note also that in newer filesystem with snapshot, like ZFS, */
/* the inode doesn't represent even less the disk position, becasue files */
/* are not overwritten in place, but rewritten in another location */
/* of the disk. */
*physical = FILEPHY_UNREPORTED_OFFSET;
(void)path; /* not used here */