Was looking through some mostly 5TB HDDs for a folder with vintage.ponychan.net warc. Probably not in: z2 (Power_On_Hours=4863), z4 (dead), z6 (Power_On_Hours=2505), z7, z8, [ntfs] (Power_On_Hours=22656). So it might be in: z0, z1, z3, z5.

 >>/9204/
> dedicated computer
Offline for now: uptime at end was 9-00:25:54. "bash: fork: Cannot allocate memory" defeats the point of semi-remote usage of a computer when I gotta physically walk over to it to restart/fix it ("sudo reboot now" didn't work):
> $ ssh computer@10.0.[...]
> [kinda screwed with stuff for a while]
> $ free
> -bash: fork: Cannot allocate memory
> $ [almost any command]
> -bash: fork: Cannot allocate memory
> $ :(){ :|:& };: # fork bomb
> -bash: fork: Cannot allocate memory
> $ [...]
> -bash: xmalloc: .././bashhist.c:782: cannot allocate 1056 bytes (1458176 bytes allocated)
> Connection to 10.0.[...] closed.
> $ ssh computer@10.0.[...]
> kex_exchange_identification: read: Connection reset by peer
> Connection reset by 10.0.[...] port 22
> $ # https://askubuntu.com/questions/845233/running-any-command-returns-cannot-allocate-memory-on-ubuntu-server
Image from "/z2/data/205c227/y.smutty.horse/y.smutty.horse/mgrifgljegn.png" (https://y.smutty.horse/ = now gone as "DNS address could not be found")