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.

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

could not git extract on a vfat filesystem #1

Closed
teuben opened this issue Nov 16, 2020 · 7 comments
Closed

could not git extract on a vfat filesystem #1

teuben opened this issue Nov 16, 2020 · 7 comments

Comments

@teuben
Copy link

teuben commented Nov 16, 2020

I accidentally cloned this on a vfat filesystem. I would grab all the data, but then failed to restore the files. git then claims the command
git restore --source=HEAD :/
would fix it, but not until I had copied it to a proper unix (ext4 in my case) filesystem.

Not a major issue, unless you want to support this on legacy systems.

@teuben
Copy link
Author

teuben commented Nov 16, 2020

a casual inspection of the names didn't make it obvious to me why it failed on VFAT.

@amanchokshi
Copy link
Owner

I've never heard of the vfat filesystem. What operating system are you on? Do you think it's just the file names that may be messing things up? Most of the data is saved as binary txt files with a couple of plain text files.

@teuben
Copy link
Author

teuben commented Nov 17, 2020

vfat is sometimes seen on USB or external HDD's when you buy them. Comes out of the windows world. Also NTFS now. It's "portable" between Mac, Linux and Windows. But they have restrictions, e.g. no case sensitive files, there is some limitations e.g. you probably can't have a directory called /C: i would think. So something in your filenames is not 100% portable if you ever thought of using is more portable.

@teuben
Copy link
Author

teuben commented Nov 17, 2020

Just realized what the vfat problem was: filenames on vfat cannot contain a :
So, something like 2019-10-10-10:30.json would cause an error.

@amanchokshi
Copy link
Owner

Shucks! I'll keep that in mind for the future and make sure that we have more compatible file naming when similar experiments are run again.

Do you think I should put a note on the examples directory that there can be problems on a vfat filesystem? What operating system are you on?

@teuben
Copy link
Author

teuben commented Nov 17, 2020

I'm on linux, but since I ran out of space, I went to an empty looking partition on an externally mounted HDD, which I had forgotten kept in vfat since it's useful to copy files to "alien" computers sometimes. So, overall I don't think this is a problem. If I remember, i should check if on an ntfs you can have filenames with a : in them. If you ever suspect you may want to support windows, this would become an issue. mac should have no issue, but I've not tried that.

@amanchokshi
Copy link
Owner

Good to know. I'll add a comment to the top of the documentation to let users know that this is an possible issue on windows or the vfat system.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants