diff options
| author |  memeplex <memeplex@web> | 2017-04-21 19:28:48 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-04-21 19:28:48 +0000 |
| commit | 04679ebab93344881155644e80e74a95bb7308e9 (patch) | |
| tree | fe79a138ca0baf81fbbbf4b7159e1409384a0772 | |
| parent | d43e83f31173ee0117fff6f497c8ac4c8da73d31 (diff) | |
| -rw-r--r-- | doc/forum/Lots_of_4k_symlinks.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/forum/Lots_of_4k_symlinks.mdwn b/doc/forum/Lots_of_4k_symlinks.mdwn index c9113d919..7f90f874d 100644 --- a/doc/forum/Lots_of_4k_symlinks.mdwn +++ b/doc/forum/Lots_of_4k_symlinks.mdwn @@ -1,6 +1,6 @@ Hi, -this is a minor issue and probably there is no better solution, but nevertheless I would like to point out it and maybe discuss a little about the issue. +this is a minor issue and probably there is no better solution, but nevertheless I would like to point it out and maybe discuss a little about the issue. Given that the symlinks generated by annex are pretty large in size (they point to a file named by a large hash number), ext4 is using an entire block (4K) of storage instead of [embedding the symlink into the inode][inode] itself. For the "archivist use case" of annex, this might lead to tens or hundreds of MBs of disk occupied by symlinks which actually don't add up to more than a few MBs. |