pink posts?
>>/10098/
> Though y'all still have over 200 posts before you get to the absolute reply limit.
I didn't know about that, so it's 1000 as the limit (like textboards).
>>/10084/
> I have a total of about 212,693 + 212693 inodes ...
More like a total of 212,693 inodes only because parts of / symlink to /tmp (/ and /tmp = two different devices/FSs). Each symlink takes up one inode, same with each file.
> https://askubuntu.com/questions/919748/
says:
> Use this command to get an ordered list of the subdirectories with the most inodes used:
> $ sudo find . -xdev -type f | cut -d "/" -f 2 | sort | uniq -c | sort -n
> Run this in your root folder, then drill down until you find your culprit.
df -i says:
> Filesystem Inodes IUsed IFree IUse% Mounted on
> /cow 212693 212693 0 100% /
but that ...uniq -c... says that not that many inodes are used:
> 2 root \ 8 boot \ 156 sbin
> 167 bin \ 1216 etc \ 5644 lib
> 6140 var \ 60321 home \ 79788 usr
> $ # 153,442 = 60321 + 79788 + 6140 + 5644 + 1216 + 167 + 156 + 8 + 2
> $ # /tmp has 67,594 free inodes
because I only checked file-type and not link-type:
> $ sudo find . -xdev -type l | cut -d "/" -f 2 | sort | uniq -c | sort -n
> 1 initrd.img \ 1 media \ 1 vmlinuz
> 20 bin \ 89 sbin \ 126 lib
> 228 var \ 811 etc \ 21056 usr
> 145066 home
> $ # 167,399 = 145066 + 21056 + 811 + 228 + 126 + 89 + 20 + 3
> $ # 320,841 = 153442 + 167399, so "over the total by 108,148"?
Files+links in home in / = 205,387 (60,321 + 145,066). Can't symlink a folder, only files. Conclusion: this system has a total of like 212,693 inodes. It would need to only use up 12,693 on initialization to have 200,000 free which is about the number of free inodes that I need. However, 1216 etc + 5644 lib + 6140 var use 13,000; + 79788 usr = 92,788. But, running "find $HOME | wc -l" says 206,460. Deleting all of the .data files in $HOME = 6364 used and 206329 free inodes. If each Ponibooru webpage is <256K, then that's 200,000 files. However, the JS thing to get the live image links is like 40 MB, so that's 156 blocks doesn't matter.
Doesn't show the right number of ChildBlocks (because that would take too long I guess):
> $ ipfs ls QmbYszVbDz9TNvFGmvvTVVyL3M2vmiMDHj8NwyL3h8iusu
> QmeqMsP2Gsro13LWjrfXNNkv95usEqsGprwk11tAZJb7w2 - ponibooru_restored_version_2024.02.28.07.29.03.Z/
> $ ipfs files stat /ipfs/QmeqMsP2Gsro13LWjrfXNNkv95usEqsGprwk11tAZJb7w2
> QmeqMsP2Gsro13LWjrfXNNkv95usEqsGprwk11tAZJb7w2
> Size: 0
> CumulativeSize: 2543210216
> ChildBlocks: 256
> Type: directory
"ipfs dag import --stats QmbYszVbDz9TNvFGmvvTVVyL3M2vmiMDHj8NwyL3h8iusu.car" says... whatever it says, that may not correspond to the total count of DATA files that it uses up.