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

Boar should not be affected by FAT32 limits #29

Open
GoogleCodeExporter opened this issue Jun 15, 2015 · 0 comments
Open

Boar should not be affected by FAT32 limits #29

GoogleCodeExporter opened this issue Jun 15, 2015 · 0 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Create a repository on a FAT32 drive
2. Import a directory with a file with size > 4GB

What is the expected output? What do you see instead?

There is an error message. The operation should complete normally.

Due to how boar store files internally, file size limits imposed by the file 
system also affects boar. FAT32 is unfortunately still quite common as the 
default file system on portable media such as USB memory sticks and external 
HDDs. Boar should split large files so that a repository can always be stored 
on FAT32. FAT32 max file counts and filename limits are not expected to cause 
any problems.

There are possibly other file systems that should be supported by boar, but 
this issue covers only FAT32.

Original issue reported on code.google.com by ekb...@gmail.com on 15 Aug 2011 at 2:03

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

No branches or pull requests

1 participant