[microcolonel]

I don't see it as such a big problem. Most filesystem images aren't intended to be ported directly between machines in general. As long as they have a tool to read the filesystem on a different configuration, a filesystem with this restriction could still be very useful for generic bulk storage on a single node.

[zackelan]

CPUs with hyperthreading typically allow you to disable it in the BIOS. If you're running a new, beta-ish CPU microarchitecture (such as Ryzen/Threadripper) you might wish to disable HT as part of troubleshooting a CPU freeze/hang.

Changing a single CPU-related flag in the BIOS should under no circumstances render a filesystem unmountable.

[biokoda]

Changing the number of cores given to a VM is not so uncommon.

[pantalaimon]

What if you upgrade the machine with a new CPU that has more cores?

[drewm1980]

A comment from one of the devs says there should be no impact as long as the number of CPU's stays below the number of locks the filesystem was created with, which will be very high by default. If it goes above, there is a possibility of more lock contention but it will still work.

[pixl97]

Disable some cores in the bios.

[loeg]

That sort of defeats the point of an upgrade.

[pixl97]

So going from 2GHz to 3, or getting 50÷ IPC from an updated chip isn't worth it?

[dredmorbius]

Archive and restore or transfer to new media.

[JoshTriplett]

Agreed. They might fix it at some point, but if there's a performance advantage to making the filesystem non-portable between machines with different numbers of CPUs, many people might happily take that performance advantage, at the cost of having to do file-level backups/transfers rather than image-level.

[pkx166j]

> Most filesystem images aren't intended to be ported directly between machines in general.

Wouldn't a Server hardware cluster potentially prove problematic?

[wfunction]

> Most filesystem images aren't intended to be ported directly between machines in general

You don't have external hard drives or flash drives...?

[justincormack]

This file system only works on nvdimms, which are typically in RAM sockets. It won't work on normal block devices.

[wfunction]

Er, the comment was, "Most filesystem images aren't intended to be ported directly between machines in general."

The entire complaint itself is the fact that this file system isn't able to do what people expect from most file system images (read: pretty much every one, except this one). Citing the fact that this particular one fails that pattern isn't a justification, it's circular logic.