| 1 |
On Tuesday, 14 January 2020 11:07:34 GMT n952162 wrote: |
| 2 |
> On 2020-01-14 11:10, Peter Humphrey wrote: |
| 3 |
--->8 |
| 4 |
> >> This is a fresh install from a minimal cd image. I'm starting out with |
| 5 |
> >> mkfs. I've tried that 3 times, twice using a stage 3 from 2020/01/08 |
| 6 |
> >> and once using a stage 3 from 2020/01/12. |
| 7 |
> > |
| 8 |
> > Er...you aren't running out of disk space, are you (either physical space |
| 9 |
> > or inodes)? Don't forget /tmp and /var/tmp. And what result did 'emerge |
| 10 |
> > --sync' return? Specifically, did you see a 'Sync completed' message? |
| 11 |
> > Have you watched /usr/bin/top status lines while syncing? |
| 12 |
> > |
| 13 |
> > And have you actually tried emerge-webrsync? |
| 14 |
> |
| 15 |
> 'emerge --sync' gave me status 1 and before that, the error about the |
| 16 |
> manifest: |
| 17 |
|
| 18 |
I didn't see a manifest error before; perhaps I overlooked it. |
| 19 |
|
| 20 |
> Number of files: 158,236 (reg: 131,524, dir: 26,712) |
| 21 |
> Number of created files: 158,235 (reg: 131,524, dir: 26,711) |
| 22 |
> Number of deleted files: 0 |
| 23 |
> Number of regular files transferred: 131,524 |
| 24 |
> Total file size: 208.96M bytes |
| 25 |
> Total transferred file size: 208.96M bytes |
| 26 |
> Literal data: 208.96M bytes |
| 27 |
> Matched data: 0 bytes |
| 28 |
> File list size: 3.90M |
| 29 |
> File list generation time: 0.001 seconds |
| 30 |
> File list transfer time: 0.000 seconds |
| 31 |
> Total bytes sent: 2.71M |
| 32 |
> Total bytes received: 218.79M |
| 33 |
> |
| 34 |
> sent 2.71M bytes received 218.79M bytes 56.02K bytes/sec |
| 35 |
|
| 36 |
HOW long?! 56KB/s shows something going badly wrong. |
| 37 |
|
| 38 |
> total size is 208.96M speedup is 0.94 |
| 39 |
|
| 40 |
I've never seen a speedup less than 1 before. |
| 41 |
|
| 42 |
> * Manifest timestamp: 2020-01-12 18:38:55 UTC |
| 43 |
> * Valid OpenPGP signature found: |
| 44 |
> * - primary key: DCD05B71EAB94199527F44ACDB6B8C1F96D8BF6D |
| 45 |
> * - subkey: E1D6ABB63BFCFB4BA02FDF1CEC590EEAC9189250 |
| 46 |
> * - timestamp: 2020-01-12 18:38:55 UTC |
| 47 |
> * Verifying /var/db/repos/gentoo/.tmp-unverified-download-quarantine |
| 48 |
> ...!!! Manifest v> |
| 49 |
> Manifest mismatch for media-plugins/Manifest.gz |
| 50 |
> __size__: expected: 48363, have: 48349 |
| 51 |
|
| 52 |
That would indeed leave the tree safely in quarantine. |
| 53 |
|
| 54 |
> Inodes? That's an interesting thought. Not sure how I'd check that ... |
| 55 |
> I'll redirect the output into a file next time. |
| 56 |
> |
| 57 |
> What would I look for in the top(1) status lines (the lines at the top |
| 58 |
> before the process table?)? |
| 59 |
|
| 60 |
I'd want to see how much memory and swap were consumed and available; the |
| 61 |
processor load may offer you a clue too. |
| 62 |
|
| 63 |
> With emerge-webrsync do you mean webrsync or is there some additional |
| 64 |
> facility? |
| 65 |
|
| 66 |
According to the Wiki* the first thing you do after chrooting into the new |
| 67 |
system is to issue the command 'emerge-webrsync'. I suggest you try it. |
| 68 |
|
| 69 |
|
| 70 |
* https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Base#Installing_an_ebuild_repository_snapshot_from_the_web |
| 71 |
|
| 72 |
-- |
| 73 |
Regards, |
| 74 |
Peter. |
Archives