Multiple "storage attachments" can be initialized. How to specify which one is currently used?

[ChaiWenyu1983]

lotus-miner storage attach --init --store ~/storage/disk1
lotus-miner storage attach --init --store ~/storage/disk2
.................................
Multiple "storage attachments" can be initialized. How to specify which one is currently used?

[LexLuthr]

Use the "--weight" option.
How are these storages prioritized for usage?

• By space used and weight. Storage is picked by multiplying % available space by the weight - so a 90% full disk with weight 10 is as likely to be picked as 0% full disk with weight 1 (10% * 10 vs 100% * 1)

[ChaiWenyu1983]

A little bit clear, that is, you can not care about the storage location, but only the total remaining space，The system will automatically allocate and use all available space?

[ChaiWenyu1983]

Supplement: assuming the same priority, there is no weight setting.

[LexLuthr]

$ lotus-miner storage attach --help
NAME:
   lotus-miner storage attach - attach local storage path

USAGE:
   lotus-miner storage attach [command options] [arguments...]

DESCRIPTION:
   Storage can be attached to the miner using this command. The storage volume
   list is stored local to the miner in $LOTUS_MINER_PATH/storage.json. We do not
   recommend manually modifying this value without further understanding of the
   storage system.
   
   Each storage volume contains a configuration file which describes the
   capabilities of the volume. When the '--init' flag is provided, this file will
   be created using the additional flags.
   
   Weight
   A high weight value means data will be more likely to be stored in this path
   
   Seal
   Data for the sealing process will be stored here
   
   Store
   Finalized sectors that will be moved here for long term storage and be proven
   over time

OPTIONS:
   --init               initialize the path first (default: false)
   --weight value       (for init) path weight (default: 10). --------------------> Needs to be used while attaching storage.
   --seal               (for init) use path for sealing (default: false)
   --store              (for init) use path for long-term storage (default: false)
   --max-storage value  (for init) limit storage space for sectors (expensive for very large paths!)
   --groups value       path group names
   --allow-to value     path groups allowed to pull data from this path (allow all if not specified)
   --help, -h           show help (default: false)

If you want to adjust weight then it can be done in sectorstorage.json residing within the storage path. It will require a restart to take effect.

{
  "ID": "9ed75093-f5ac-4629-bff5-676ddc4b383f",
  "Weight": 10,
  "CanSeal": false,
  "CanStore": true,
  "MaxStorage": 0,
  "Groups": null,
  "AllowTo": null
}

Ideally, yes, you don't need to care about storage location. As long as there is enough space, lotus-miner will take care of placing the sector correctly. Please let me know if there is any confusion.