Not really sure what's going on here, but I figured it's weird enough behavior to report. I've been trying to rename my zpool for a couple days now. Whenever I tried to import the zpool after exporting it, It would "dissapear" from the list of importable pools.
```
root@lordran:/etc/systemd/system# zpool export graveyard-0
root@lordran:/etc/systemd/system# zpool import
pool: graveyard-0
id: 1478417917094675172
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
graveyard-0 ONLINE
mirror-0 ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615660R ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615654A ONLINE
root@lordran:/etc/systemd/system# zpool import
no pools available to import
```
Attached is an straced version of what happens when import is called.
Anyway, I noticed that the action said that it could be imported using its name or its identifier, so I tried the identifier...and *that* worked. At a complete loss for why, or who I should report it to. There are a fair number of people on these forums that have had issues with zfs renaming over the years, so I figured I'd start here. To be clear, the problem is *solved*-ish.
```
root@lordran:/etc/systemd/system# zpool export graveyard-0
root@lordran:/etc/systemd/system# zpool import
pool: graveyard-0
id: 1478417917094675172
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
graveyard-0 ONLINE
mirror-0 ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615660R ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615654A ONLINE
root@lordran:/etc/systemd/system# zpool import
pool: graveyard-0
id: 1478417917094675172
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
graveyard-0 ONLINE
mirror-0 ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615660R ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615654A ONLINE
root@lordran:/etc/systemd/system# zpool import 1478417917094675172
```
```
root@lordran:/etc/systemd/system# zpool export graveyard-0
root@lordran:/etc/systemd/system# zpool import
pool: graveyard-0
id: 1478417917094675172
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
graveyard-0 ONLINE
mirror-0 ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615660R ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615654A ONLINE
root@lordran:/etc/systemd/system# zpool import
no pools available to import
```
Attached is an straced version of what happens when import is called.
Anyway, I noticed that the action said that it could be imported using its name or its identifier, so I tried the identifier...and *that* worked. At a complete loss for why, or who I should report it to. There are a fair number of people on these forums that have had issues with zfs renaming over the years, so I figured I'd start here. To be clear, the problem is *solved*-ish.
```
root@lordran:/etc/systemd/system# zpool export graveyard-0
root@lordran:/etc/systemd/system# zpool import
pool: graveyard-0
id: 1478417917094675172
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
graveyard-0 ONLINE
mirror-0 ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615660R ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615654A ONLINE
root@lordran:/etc/systemd/system# zpool import
pool: graveyard-0
id: 1478417917094675172
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
graveyard-0 ONLINE
mirror-0 ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615660R ONLINE
ata-Samsung_SSD_870_EVO_1TB_S6PTNM0T615654A ONLINE
root@lordran:/etc/systemd/system# zpool import 1478417917094675172
```