• 2 Posts
  • 20 Comments
Joined 6 months ago
cake
Cake day: March 4th, 2025

help-circle






  • It’s fine to do it that way.

    Make sure your pool is healthy, then replace one drive, add the new one to the pool and start resilvering. If something breaks in the resilvering process, you still have the one you took out with all the data.

    If you want to be extra sure, copy the whole pool’s content to the fourth drive so even if both old drives fail (unlikely, but as you mentioned, same production line etc, and resilvering is a very read intensive process) you have your data.














  • Yes it is, and as the other comment mentioned, using subdomains works perfectly fine.

    Theoretically, a migration can work, but it’s just not implemented. I think there’s keys for each account on your instance and they would be other keys on your new software but remote instances would not accept those new keys so you would need to migrate your old keys and there’s no feature to do that.

    E.g. you can switch from mastodon to a fork and keep your database and I’ve heard PieFed is working on a migration feature from Lemmy.