question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Reported MFS size can be bigger than the size of repo

See original GitHub issue

cc https://github.com/ipfs-shipyard/ipfs-webui/issues/1042, https://github.com/ipfs-shipyard/ipfs-webui/issues/629

MFS can store files in “lazy” fashion, which means root is added to MFS, but children are fetched lazily, on first use.

Example

English wikipedia mirror is ~650 GB. Lazy pointer to it can be added to MFS instantly via:

$ ipfs files cp /ipfs/QmXoypizjW3WknFiJnKLwHCnL72vedxjQkDDP1mXWo6uco /en.wikipedia-on-ipfs.org

Problem

This feature of MFS creates a problem in WebUI, it looks like “Files” take more space than “entire repo”:

Screenshot_2019-10-11  cohosting full - Files - IPFS

This will become a problem when we start taking advantage of this lazy mode in website cohosting (discussed in https://github.com/ipfs-shipyard/cohosting/issues/6)

Solution?

We need to change the labels, make them more informative. Below is a quick mock that illustrates what additional information needs to be conveyed. The problem is that it does not look good, and we need to clean this up somehow.

Screenshot_2019-10-11  cohosting full - Files - IPFS(1)

Thoughts?

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:2
  • Comments:8 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
hsn10commented, Mar 31, 2021

I dont think this is a bug. It maybe confusing and need some UI adjust but behavior is correct.

1reaction
lidelcommented, Oct 14, 2019

Yup, dropping all is better 👍 I also would go with C, just for clarity’s sake: B introduces problem of having 2019-10-15--01-20-40 and 2019-10-15--01-20-59 pretty close to each other.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Reduce repository size - GitLab Docs
Git repositories become larger over time. When large files are added to a Git repository: Fetching the repository becomes slower because everyone must ......
Read more >
Git repo size on filesystem is way larger than its clone
The repo.git/objects folder is 3.8GB large on the server's filesystem (it the same same as reported in GitLab's UI).
Read more >
About large files on GitHub
GitHub limits the size of files you can track in regular Git repositories. ... a file to a repository via a browser, the...
Read more >
Git limits - Azure Repos - Microsoft Learn
We recommend keeping your repository below 10GB for optimal operation. If your repository exceeds this size consider using Git-LFS, Scalar, or ...
Read more >
New size limits for Git repositories and files as of Sept 2020
If you are regularly pushing files of 100MB or more · Git LFS lets you easily push files larger than 100MB to your...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found