# Hashstore Migration Guide

**URL:** <https://forum.storj.io/t/hashstore-migration-guide/30658>\
**Category:** getting started\
**Tags:** hashstore\
**Created:** [September 1, 2025, 11:10am UTC](https://forum.storj.io/t/hashstore-migration-guide/30658 "2025-09-01T11:10:57Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![dancekid](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/dancekid/32/7825_2.png) [@dancekid](https://forum.storj.io/u/dancekid)\
**Post date:** [September 1, 2025, 11:10am UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/1 "2025-09-01T11:10:57Z")

</div>

Hello Community,

I see many Infos how to migrate to Hashstore.

Is there one Document available with all Options, Settings and stuff ?

When to restart the node ? Explanation of Environment Variables ?

I try to collect and update this Thread:

# What is the current status of automatic migration?

> [@Hashstore Migration Guide](https://forum.storj.io/t/hashstore-migration-guide/30658/280):
>
> It’s not entirely public, how far along in the hash store conversion we are. If you’ve not done anything yourself, there have been three stages: Testing: Where a handful of nodes were selected, and wrote new pieces to hash store Passive Migration: (We’re here now) New pieces are written to hash store, read pieces are converted to hash store. Pieces at rest stays in old piece store Active Migration: (Will come after a bit more testing): All remaining pieces are converted to hashstore. When I …

# How do I check if my node is using hash storage?

> [@Hashstore Migration Guide](https://forum.storj.io/t/hashstore-migration-guide/30658/279):
>
> yes, i think today all people has this directory, do you perform full migrate? if you migrate actively aal satellites, then blobs directory should be 0 size or near this, then migration is over.

> [@Hashstore Migration Guide](https://forum.storj.io/t/hashstore-migration-guide/30658/281):
>
> You can compare the prometheus metrics used\_space and hashstore{field=LenLogs}.

# For Migration (passive / active) Files need to be modified in your Storage Location:

- `/<storagelocation>/storage/hashstore/meta`

Also note the permissions of the **`.migrate** and **.migrate\_chore** files may be very restrictive. You might have to modify permissions on the files to allow writing, or make modifications as the specific owner.  
For the docker version - **you must stop and remove the container before making changes to these files** , only stopping the container is not enough, because the docker’s overlay filesystem could revert your changes when you start the stopped container back.

# **Enable passive migration. (requires version v1.119)**

### Info:

- **WriteToNew** will send all incoming uploads to the hashstore

- **TTLToNew** will send only uploads with a TTL to the hashstore

- **ReadNewFirst** will check any new download request first in hashstore then piecestore. Use true if you start using hashstore.

- **PassiveMigrate** will migrate any piece that gets hit by a download request

todo:

1. Stop and remove the container (or stop the storagenode service)
2. `cd /<your node location>/storage/hashstore/meta`
3. use 1 to 4 strings below (one for each satellite)

```auto
echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6.migrate
echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S.migrate
echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs.migrate
echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE.migrate

```

1. Run the container back (or start the storagenode service)

# **Enable active migration (requires version v1.120)**

### Info:

- Will take multipe days with high CPU time.

- You can enable it for all satellites at the same time.

- The migration will run through them one by one.

- single migration per satellite between node upgrades possible ? powerfull cpu ?

todo:

1. Stop and remove the container (or stop the storagenode service)
2. `cd /<storagelocation>/storage/hashstore/meta`
3. use 1 to 4 strings below (one for each satellite)

```auto
echo -n true > 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6.migrate_chore
echo -n true > 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S.migrate_chore
echo -n true > 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs.migrate_chore
echo -n true > 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE.migrate_chore

```

1. Run the container back (or start the storagenode service)

# CONFIG-Options in Environment Variables:

(note these will be changing to docker command line options in a future release after 135.5)

```auto
  - STORJ_HASHSTORE_COMPACTION_PROBABILITY_POWER=2 (default)

  - STORJ_HASHSTORE_COMPACTION_REWRITE_MULTIPLE=10 (default)

  - STORJ_HASHSTORE_MEMTABLE_MAX_SIZE=128MiB (default ????) 

  - STORJ_HASHSTORE_TABLE_DEFAULT_KIND=hashtbl (default)

  - STORJ_HASHSTORE_MEMTBL_MMAP=false (default)

```

# CONFIG-Options in Docker:

```auto
--hashstore.table-path (if you have SSD, use that one, but monitor degradation)

--hashstore.table-default-kind (if you have at least TB * 1.3 = GB memory)

--hashstore.hashtbl.mmap (if you know what is mmap, but don’t have enough memory, neither SSD, but still interested to check if it’s faster for hashtbl)

--hashstore.compaction.rewrite-multiple (if you have enough space, one compaction could rewrite more logs. You need * free space in addition to the used space)

--hashstore.compaction.alive-fraction: if you are fine with heavier IO / in exchange of less stored garbage (I use 0.65 on some nodes)

```

### Compaction

Compaction is the process of removing dead bytes from the log files. It runs once per day for each DB.

Most of the time you don’t need to touch the configuration of the compaction.

But if you are really interested about tuning it manually, the most important configurations are:

```auto
--hashstore.compaction.alive-fraction float
--hashstore.compaction.probability-power float
--hashstore.compaction.rewrite-multiple float

```

And they are expoained here:

[![](https://img.youtube.com/vi/87zG_pzuxNE/maxresdefault.jpg "Tuning Hashstore configuration parameters for Storj Storagenodes") ](https://www.youtube.com/watch?v=87zG_pzuxNE)

### hashtbl vs memtbl

- **Info: need atleast TB \* 1.3 = GB memory**

- `--hashstore.table-default-kind memtbl`

### use SSD

- create dir on ssd: mkdir //table

- `--hashstore.table-path`

# How to check Logfiles

> [@\[Tech Preview\] Hashstore backend for storage nodes](https://forum.storj.io/t/tech-preview-hashstore-backend-for-storage-nodes/28724/188):
>
> In logs, info level, with some custom filtering. Search my post in “log custom level” thread. The startup piece scan gives you the no. of pieces on each sat and the migration chore gives you a log entry after each 10.000 pieces processed. I can’t post the specific entries right now, but they are obvious.

```auto
docker logs storagenode 2>&1 | grep "piecemigrate:chore"

```

# How to check a progress

## How to check a progress with `strace`

```auto
sudo strace -p your_storagenode_pid -f -e trace=file -tt 2>&1 | grep blob

```

To get your storagenode pid, run

```auto
sudo docker top storagenode

```

Find the one that has the storagenode run on it.

## How to check a progress with `fatrace`

```auto
cd /path/to/storj/node-data
fatrace -ct

```

# Migration finished ? Cleanup your blobs

- delete files inside //storage/blobs/

### bash

to find all non-zero files which could remain:

```auto
find /mnt/storagenode/blobs -type f -size +0

```

to remove all under `/mnt/storagenode/blobs`:

```auto
rm -rf /mnt/storagenode/blobs/*

```

### zsh

to check:

```auto
ls -l /mnt/storagenode/blobs/**/*(.L1)

```

or

```auto
stat -f '%z %N' /mnt/storagenode/blobs/**/*(.L1)

```

to remove:

```auto
rm -rf /mnt/storagenode/blobs/*

```

### PowerShell

to check

```auto
Get-ChildItem -Path "X:\storagenode\storage\blobs" -Recurse -Directory | Where-Object { (Get-ChildItem -LiteralPath $_.FullName).Count -eq 0 } | Remove-Item -WhatIf

```

to remove only empty

```auto
Get-ChildItem -Path "X:\storagenode\storage\blobs" -Recurse -Directory | Where-Object { (Get-ChildItem -LiteralPath $_.FullName).Count -eq 0 } | Remove-Item

```

# Errorhandling

- Dashboard shows incorrect used space
  - → stop node, delete `storage/used_space_per_prefix.db`, restart node

# Example Docker-String

coming soon

# Example Windows-String

coming soon

Greetings Michael

---

<div class="post-metadata">

**Author:** ![EasyRhino](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/easyrhino/32/1133_2.png) [@EasyRhino](https://forum.storj.io/u/EasyRhino)\
**Post date:** [September 1, 2025, 4:57pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/2 "2025-09-01T16:57:51Z")

</div>

the formatting with the “headers” got kind rough there.

---

<div class="post-metadata">

**Author:** ![EasyRhino](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/easyrhino/32/1133_2.png) [@EasyRhino](https://forum.storj.io/u/EasyRhino)\
**Post date:** [September 1, 2025, 5:22pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/3 "2025-09-01T17:22:46Z")

</div>

the first bit with the passive migrate echo lines is messed up formatting in two ways.

1. the outer encapsulator is a single quote ’ and needs to be a double quote (edit: no wait, the outer single quote is good, it just can’t be slantey)

2. inside the echo line, the double quotes are “windows style” slantey quotes and not unix style straight double quotes so I get an error like this:

> storj14003 | 2025-09-01T17:10:29Z WARN failed to unmarshal migration state {“Process”: “storagenode”, “error”: “invalid character ‘â’ looking for beginning of object key string”, “satellite”: “1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE”}

at the end of the day each .migrate file should look something like this:

```auto
{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}

```

---

<div class="post-metadata">

**Author:** ![dancekid](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/dancekid/32/7825_2.png) [@dancekid](https://forum.storj.io/u/dancekid)\
**Post date:** [September 1, 2025, 6:32pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/4 "2025-09-01T18:32:57Z")

</div>

how to post those links without line break ?

something like an additional (longer) field ?

Michael

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [September 1, 2025, 7:07pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/5 "2025-09-01T19:07:53Z")

</div>

Great initiative 😎

Perhaps you should add info about where to place the files ? (/storage/hashstore/meta)

Also things to consider adding:

- how to check logs for progress
- how to delete obsolete folders in /storage/blobs//\* after migration
- how to solve the double-usage data-usage with `used_space_per_prefix.db`
- explain what memtbl settings does and how especially that it is not a requirement (it will use a few gigs og ram on larger nodes)

---

<div class="post-metadata">

**Author:** ![EasyRhino](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/easyrhino/32/1133_2.png) [@EasyRhino](https://forum.storj.io/u/EasyRhino)\
**Post date:** [September 1, 2025, 10:00pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/6 "2025-09-01T22:00:25Z")

</div>

> [@dancekid](#):
>
> how to post those links without line break ?
> 
> Michael

you can use the “preformatted text” quote option.

Important prerequisite before setting these lines.

need to move to your storage folder that has the hashstore meta. on my system it is: /storagedrive/storage/hashstore/meta

And the permissions are really restrictive on the meta files. in my case the owner was “root” so I had to be logged in as root to issue the echo commands.

here is what my echo lines looked like that worked:

```auto

echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6.migrate
echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S.migrate
echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs.migrate
echo '{"PassiveMigrate":true,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}' > 1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE.migrate

```

---

<div class="post-metadata">

**Author:** ![Alexey](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/alexey/32/41_2.png) [@Alexey](https://forum.storj.io/u/Alexey)\
**Post date:** [September 2, 2025, 4:19am UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/7 "2025-09-02T04:19:52Z")

</div>

I converted the first post to the wiki, now you can edit it and make it a fulfil documentation.

---

<div class="post-metadata">

**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\
**Post date:** [September 2, 2025, 11:29am UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/9 "2025-09-02T11:29:00Z")

</div>

> [@dancekid](#):
>
> ```auto
> - STORJ_HASHSTORE_COMPACTION_PROBABILITY_POWER=2
> - STORJ_HASHSTORE_COMPACTION_REWRITE_MULTIPLE=10
> - STORJ_HASHSTORE_MEMTABLE_MAX_SIZE=128MiB
> - STORJ_HASHSTORE_SYNC_LIFO=true
> - STORJ_HASHSTORE_STORE_FLUSH_SEMAPHORE=1
> - STORJ_HASHSTORE_TABLE_DEFAULT_KIND=memtbl
> - STORJ_HASHSTORE_MEMTBL_MMAP=true
> - STORJ_HASHSTORE_MEMTBL_MLOCK=true
> 
> ```

There are way too many values here. I believe most of the time, it’s better to keep the defaults. Unless you really understand all of these settings, and you need them to fine-tune SN for your hardware.

It would be better to show the documentation of these, and explain when they are useful, instead of recommending as default options.

The `STORJ_HASHSTORE_TABLE_DEFAULT_KIND=memtbl` is probably the difference (still it should be used with enough memory). Same for MMAP. And AFAIK MLOCK is true by default.

---

<div class="post-metadata">

**Author:** ![Vadim](https://storj.bcdn.literatehosting.com/letter_avatar/vadim/32/6_449c533f586939b6e5f246632a46421f.png) [@Vadim](https://forum.storj.io/u/Vadim)\
**Post date:** [September 2, 2025, 12:43pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/10 "2025-09-02T12:43:12Z")

</div>

Is it possible to know what row do what? and requirements to use it.

---

<div class="post-metadata">

**Author:** ![Balage76](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/balage76/32/1129_2.png) [@Balage76](https://forum.storj.io/u/Balage76)\
**Post date:** [September 2, 2025, 3:41pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/11 "2025-09-02T15:41:51Z")

</div>

Could you please summarize what lines/parameters should be entered in the config file for the different options if I use Windows?

---

<div class="post-metadata">

**Author:** ![elek](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/elek/32/9189_2.png) [@elek](https://forum.storj.io/u/elek)\
**Post date:** [September 2, 2025, 3:50pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/12 "2025-09-02T15:50:16Z")

</div>

From the next release, it will be possible to change them also by configuration settings or command line flag.

Therefore the help can be printed out:

 ![image](https://storj-s3.bcdn.literatehosting.net/original/3X/9/8/98036fd6afa9ac68dfdb567990280604760cf5a0.png)

There is no requirement to use these, our goal is to make the defaults smart enough to work well for everybody. IMHO there shouldn’t be any requirement to learn internals, just to be a successful SNO.

Still we can write a Tuning Guide, but it’s a bigger effort.

My generic recommendation: set flags only if you understand the consequences 😃

If you really like knobs, and you MUST adjust them, I would start with these:

- `--hashstore.table-path` (if you have SSD, use that one, but monitor degradation)
- `--hashstore.table-default-kind` (if you have at least TB \* 1.3 = GB memory)
- `--hashstore.hashtbl.mmap` (if you know what is mmap, but don’t have enough memory, neither SSD, but still interested to check if it’s faster for hashtbl)
- `--hashstore.compaction.rewrite-multiple` (if you have enough space, one compaction could rewrite more logs. You need \* free space in addition to the used space)
- `--hashstore.compaction.alive-fraction`: if you are fine with heavier IO / in exchange of less stored garbage (I use 0.65 on some nodes)

---

<div class="post-metadata">

**Author:** ![EasyRhino](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/easyrhino/32/1133_2.png) [@EasyRhino](https://forum.storj.io/u/EasyRhino)\
**Post date:** [September 2, 2025, 5:23pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/13 "2025-09-02T17:23:48Z")

</div>

Since it’s a wiki I updated the first post just to show the default values.

It will be nice when it’s regular command line options

---

<div class="post-metadata">

**Author:** ![zeeshanabid](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/zeeshanabid/32/69_2.png) [@zeeshanabid](https://forum.storj.io/u/zeeshanabid)\
**Post date:** [September 3, 2025, 7:19pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/14 "2025-09-03T19:19:44Z")

</div>

Do we have to migrate to hashstore? Is it mandatory? I read somewhere it will be default in coming versions and all nodes will be automatically migrated. Was it true? Should I wait for that if it will be automatically be migrated or do I need to take other actions?

---

<div class="post-metadata">

**Author:** ![EasyRhino](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/easyrhino/32/1133_2.png) [@EasyRhino](https://forum.storj.io/u/EasyRhino)\
**Post date:** [September 3, 2025, 9:54pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/15 "2025-09-03T21:54:39Z")

</div>

It will be mandatory, automatic, and gradual.

> [@Hashstore rollout commencing!](https://forum.storj.io/t/hashstore-rollout-commencing/30589/178):
>
> I want to test restoration/recovery of the hashtbl. What’s the difference between this tool and the write-hashtbl command in the main Storj repo? I am also assuming to restore we’d just drop hashtbl into the meta folder? I noticed sometimes the hashtbl filename will also have a long number attached to it, for example hashtbl-0000000000000003. Edit: I used both tools (with --kind=0 for the first) and they result in different sizes. First was 130M and the other 33M.

I’ve been working testing it gradually (my tiniest node) on it because most of my storage uses NFS mounted storage (which storj doesn’t support) and it breaks on the new hashstore unless I make adjustments.

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [September 4, 2025, 8:13pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/16 "2025-09-04T20:13:05Z")

</div>

I have put true into migrate\_chore, I see disk activity, I see size of the hashstore folder grow, however in the node log I don’t see new uploads going to hashstore, they continue to be logged by piecestore.

What am I missing?

---

<div class="post-metadata">

**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\
**Post date:** [September 4, 2025, 8:58pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/17 "2025-09-04T20:58:45Z")

</div>

The display is in piecestore. That is what I also wondered about, why it is not displayed as hashstore. But when you check the blobs folder it is empty, so everything works as hashstore apart from the display in the logs yet.

Just check when the old blobs are completed into hashlogs, then everything works as hashstore.

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [September 4, 2025, 9:57pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/18 "2025-09-04T21:57:09Z")

</div>

> [@arrogantrabbit](#):
>
> they continue to be logged by piecestore.
> 
> What am I missing?

Probably nothing, logging function does not display hashstore but piecestore regardless of the used storage backend.

However, in order for new pieces to go into hashstore, you also need these files:

```auto
storage/hashstore/meta/121RTSDpyNZVcEU84Ticf2L1ntiuUimbWgfATz21tuvgk3vzoA6.migrate
storage/hashstore/meta/12EayRS2V1kEsWESU9QMRseFhdxYxKicsiFmxrsLZHeLUtdps3S.migrate
storage/hashstore/meta/12L9ZFwhzVpuEKMUNUqkaTLGzwY9G24tbiigLiXpmZWKwmcNDDs.migrate
storage/hashstore/meta/1wFTAgs9DP5RSnCqKV1eLf6N9wtk4EAtmN5DpSxcs8EjT69tGE.migrate

```

to contain this:

`{"PassiveMigrate":false,"WriteToNew":true,"ReadNewFirst":true,"TTLToNew":true}`

.. but I’m assuming you already did this?

I was wondering the same thing initially when I migrated my nodes, but found piece of mind when using `fatrace -ct` in the SN path and saw the live traffic go to hashstore. I’m sure there is an equivalent in FreeBSD to double check.

---

<div class="post-metadata">

**Author:** ![Walter1](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/walter1/32/7825_2.png) [@Walter1](https://forum.storj.io/u/Walter1)\
**Post date:** [September 4, 2025, 10:05pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/19 "2025-09-04T22:05:59Z")

</div>

What does false, true, true, true do? Was the recommendation not to set all to true?

---

<div class="post-metadata">

**Author:** ![mike](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/mike/32/1127_2.png) [@mike](https://forum.storj.io/u/mike)\
**Post date:** [September 4, 2025, 10:14pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/20 "2025-09-04T22:14:41Z")

</div>

> [@Walter1](#):
>
> What does false, true, true, true do? Was the recommendation not to set all to true?

PassiveMigrate moves a piece from piecestore to hashstore if it is served by a client request. It’s a little redundant if you are doing active migration, but probably wouldn’t hurt 🙂

---

<div class="post-metadata">

**Author:** ![arrogantrabbit](https://storj.bcdn.literatehosting.com/user_avatar/forum.storj.io/arrogantrabbit/32/11200_2.png) [@arrogantrabbit](https://forum.storj.io/u/arrogantrabbit)\
**Post date:** [September 4, 2025, 10:35pm UTC](https://forum.storj.io/t/hashstore-migration-guide/30658/21 "2025-09-04T22:35:15Z")

</div>

> [@mike](#):
>
> .. but I’m assuming you already did this?

No, I haven’t. Should I have? I got an impression that those files (mostly based on their names) control migration: active vs passive. And since I’m doing active migration, passive configuration should be irrelevant.

> [@mike](#):
>
> live traffic go to hashstore

I’ll wait for it to finish, and then check where do actual writes go. Thanks!

[Next page](https://forum.storj.io/t/hashstore-migration-guide/30658.md?page=2)
