Error 176/Zerofill/move table/Transaction

Using Aria, you can/should be able to easily copy tables between servers.
If the table has the option "TRANSACTION=1" set, this might fail with some strange error.

After copy, the table is zerofilled, and needs upgrade with repair table.
The result is an error 176 which is caused by the option "TRANSACTION=1"

I understand, it might really be the case a transaction has started, but even though I think this error should be recoverable. At least it should be documented, this option can cause a copy/backup not to be readable.

My backup was simple:
mariadb -e "FLUSH LOCAL TABLES WITH READ LOCK;"; cp tblX* /tmp/ -f; mariadb -e "UNLOCK TABLES;"
tmp is tmpfs (memory), I know there is a chance some transaction is started in between lock and copy. Still with transaction=0, the file is readable (recoverable) any time. With it set, the table can't even be read on another host.