Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Handle the empty file inode on macOS and FAT32 #1200

Merged
merged 1 commit into from
Jul 8, 2019
Merged

Handle the empty file inode on macOS and FAT32 #1200

merged 1 commit into from
Jul 8, 2019

Commits on Jul 8, 2019

  1. Handle the empty file inode on macOS and FAT32 

    On macOS and FAT32 partitions, we will sometimes get this inode value
for more than one file. It means the file is empty.  When this happens,
the hash table of file shares becomes corrupt, since more then one file
has the same inode. Instead, let's assume it is always fine to share
empty files. (Unity case 950616).
    @joshpeterson
    joshpeterson authored and Josh Peterson committed Jul 8, 2019
    Configuration menu
    Copy the full SHA
    5174f7e View commit details
    Browse the repository at this point in the history