Hi @smu44, it is great to have you at my side! Turns out I am being a bit slow to adjust. I was convinced my problem was all to do with my faulty local_manifest …
I really don’t understand your problems with Docker, never seen such behavior in my test VM … What is weird is that you can’t kill the container(s) !
That was all bad analysis. It was over-tired rambling as I tried to make sense of my notes taken over 48 hours. At that time I assumed that runaway downloads started with my known error, why could I not kill the error and get behind it and start again?, I was asking myself!
I was expressing that I could not end one little error from the recent past. I was laying blame on Docker always “restarting where it left off with my error, attributing local_manifest”.
In light of you receiving an enormous download, I see that you are correct and better analysis is required!
I misrepresented this too. Seeing that overlay2 probably has a backup function, I guess I had the sense that this was holding my error, contributing to my woes. This was just part of the same bad analysis!
Just to be clear on this point, the overlay2 size (on rootfs) does seem to be stable, what I describe as runaway downloads only occurs in my e-partition.
One thing to cross check with you - the repo command.
Immediately before I ran into problems I followed this (seen in the output from my standard build command):
A new version of repo (2.15) is available.
You should upgrade soon:
cp /srv/src/Q/.repo/repo/repo /usr/local/bin/repo
I simply did exactly that, no reported error.
So now I am investigating that step, I see repo was present but not installed:
:~$ which repo
:~$ repo -v
error: repo is not installed. Use "repo init" to install it here.
:/usr/local/bin$ sudo repo init
Downloading Repo source from https://gerrit.googlesource.com/git-repo
remote: Counting objects: 1, done
remote: Finding sources: 100% (38/38)
remote: Total 38 (delta 15), reused 38 (delta 15)
Unpacking objects: 100% (38/38), done.
repo: Updating release signing keys to keyset ver 2.3
fatal: manifest url is required.
:/usr/local/bin$ repo --version
repo version v2.16.3
(Tue, 20 Jul 2021 23:26:01 +0000)
repo launcher version 2.15
(currently at 2.16.3)
repo User-Agent git-repo/2.16.3 (Linux) git/2.20.1 Python/3.7.3
git User-Agent git/2.20.1 (Linux) git-repo/2.16.3
Python 3.7.3 (default, Jan 22 2021, 20:04:44)
OS Linux 4.19.0-16-amd64 (#1 SMP Debian 4.19.181-1 (2021-03-19))
CPU x86_64 (unknown)
Bug reports: https://bugs.chromium.org/p/gerrit/issues/entry?template=Repo+tool+issue
As the change in repo was the last odd thing to occur, it would be interesting to know if you got this repo command message and what action you took?
Regarding my new build, I enjoy a download rate of 3G per hour, so my current download of 207G has taken approx 3 days, downloading, but still no build started. Report to follow.