The 3S! Safe Smoothie Solution

Community
, , , ,
22

IPossibly your nodes were full?

I grabbed the latest last night and it looked good - did 3GB in afew mins so I gave it 80Gb to chew on and went to bed.
Power went out overnight - I think the tumble dryer tripped the RCD which took out all downstairs sockets - so I dont know how far we got but nodes are ~40Gb larger than when I kicked off.

I’ll run it again and see if I see a similar problem.

2 Likes
23

Just built the latest and it stored 4.3Gb in 7m46.946s over 20 nodes.
Now attempting to store 166Gb to see where it craps out - which it will cos I only have a 120Gb SSD that ~/.safe/node is mounted on.

Meanwhile I will try to create a top level name, create a wallet and store that wallet URL at safe://wallet.top-level-name - and if that works, stick it in a script so I can easily send from the genesis DBC to 1000 human readable wallet addresses.

3 Likes
24

I wanna note that I am on windows, so maybe it is a windows regression in 0.70/0.75? Will test again with latest release and give results!

going strong now with the same safe and node release so I guess I might have initated baby-fleming without cleaning the previous one and it made it fail!

1 Like
25

ok I got a fail in windows, so I guess windows release is bugged:

 ~/.safe/cli/safe files put . > output.txt
Error:
   0: ClientError: Did not receive sufficient ACK messages from Elders to be sure this cmd (MsgId(afde..820a)) passed, expected: 7, received 0.
   1: Did not receive sufficient ACK messages from Elders to be sure this cmd (MsgId(afde..820a)) passed, expected: 7, received 0.

Location:
   sn_cli\src\subcommands\files.rs:213

it failed at sum size of 18GB in the baby-fleming-nodes folder size

also a note, when it fails it doesnt output the safe xorurls of the files it managed to upload! maybe when there is an error it should return the successful uploads info (xor url) like when it finishes without error

1 Like