Log Spam: "there is a possible fork, and your client is not the majority...." #3305
Description
System information
Geth version: geth 1.5.19
OS & Version: Windows/Linux/OSX
Commit hash : (if develop)
Expected behaviour
start a node from genesis and it should sync smoothly without log spam in log file
Actual behaviour
The node can sync from genesis, but there is the log span: "there is a possible fork, and your client is not the majority...."
- For reproduce case 1(with init genesis):
# geth_v1.5.19 init --datadir=test genesis.json
INFO [08-22|14:03:56.790] Maximum peer count ETH=50 total=50
INFO [08-22|14:03:56.838] Sanitizing Go's GC trigger percent=100
INFO [08-22|14:03:56.839] Disabled shared storage pool cache
INFO [08-22|14:03:56.839] Set global gas cap cap=50,000,000
INFO [08-22|14:03:56.839] Initializing the KZG library backend=gokzg
INFO [08-22|14:03:56.849] Defaulting to pebble as the backing database
INFO [08-22|14:03:56.849] Allocated cache and file handles database=/root/rsync/test/geth/chaindata cache=16.00MiB handles=16 "memory table"=1.33MiB
INFO [08-22|14:03:56.853] Opened ancient database database=/root/rsync/test/geth/chaindata/ancient/chain readonly=false tail=0 frozen=0
INFO [08-22|14:03:56.853] State scheme set to default scheme=path
INFO [08-22|14:03:56.853] New journal reader for journal kv
INFO [08-22|14:03:56.853] New journal reader for journal kv
WARN [08-22|14:03:56.853] Failed to load disk journal with node buffer, discard it err="journal not found"
INFO [08-22|14:03:56.853] New async node buffer limit=64.00MiB layers=0
INFO [08-22|14:03:56.855] Opened ancient database database=/root/rsync/test/geth/chaindata/ancient/state readonly=false tail=0 frozen=0
INFO [08-22|14:03:56.855] Initialized path database cache=16.00MiB buffer=64.00MiB history=360,000
INFO [08-22|14:03:56.855] Writing custom genesis block
INFO [08-22|14:03:56.861] genesis block hash hash=0d2184..d57b5b
INFO [08-22|14:03:56.861] Successfully wrote genesis state database=chaindata hash=0x0d21840abff46b96c84b2ac9e10e4f5cdaeb5693cb665db62a2f3b02d2d57b5b`
# geth --config ~/config.toml --datadir=test --tries-verify-mode=none
...
WARN [08-22|13:57:09.421] there is a possible fork, and your client is not the majority. Please check... nextForkHash=fc3ca6b7
WARN [08-22|13:57:09.424] there is a possible fork, and your client is not the majority. Please check... nextForkHash=fc3ca6b7
WARN [08-22|13:57:09.426] there is a possible fork, and your client is not the majority. Please check... nextForkHash=fc3ca6b7
```
#### Steps to reproduce the behaviour
it can be reproduced in two scenarios:
- case 1(with init genesis):
```
geth_v1.5.19 init --datadir=test genesis.json
geth --config ~/config.toml --datadir=test --tries-verify-mode=none
```
- case 2(without init genesis):
```
geth --config ~/config.toml --datadir=test --tries-verify-mode=none
// wait until the node started to sync, then restart it, it will be reproduced
```
#### Backtrace
NA