Mefs provides users with an encrypted file system LFS, which supports bucket and object operations
After confirming that mefs-user daemon is running, and the running role is user, run mefs-user lfs start;
When the return value is returned, there will be information about the success or failure of the startup. The initial startup process includes the entire network query and contract signing, so the startup time is relatively long.
When the user starts lfs, he can choose to use the default parameters; if you lower the price parameter, you may not find enough providers;
If you increase the ks parameter, you may not find enough keepers; if you increase the ps parameter, you may not find enough providers.
ps parameter setting should be greater than 1, other parameters should be greater than 0; rdo is true/false.
The greater the storage duration and the storage size, the greater the amount required to sign the contract.
Restart LFS, set new parameters, and set rdo to true.
This means that the bucket has been created with this name, and now the bucket is deleted, only marking records, not real deletion. Therefore, even if the bucket is deleted, creating it with this name again will still show that the bucket already exists.
This is because the file already exists in the current directory, you can download it from another directory, or rename the file in the current directory.
This means that there is already a file with this name in the currently uploaded bucket. Now that the file is deleted, it is only marked for recording, not a real deletion. So even if the file is deleted, creating it with this name again will still show that the file already exists. You can modify the upload path, for example, mefs-user lfs put_object objectName bucketName/, upload to the directory of < new dir name > corresponding to bucketName.