[Bug 250816] ZFS cannot import its own export on AWS EC2 12.1 & 12.2-RELEASE
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Fri Nov 6 17:47:19 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250816
--- Comment #16 from Gunther Schadow <raj at gusw.net> ---
Why whaddoyouknow, this way it works:
---------------------------------------------------------------------------------------------
root at geli:/home/schadow # zpool create testpool /home/schadow/zfstc/0
/home/schadow/zfstc/1
root at geli:/home/schadow # zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH
ALTROOT
testpool 160M 83.5K 160M - - 1% 0% 1.00x ONLINE
-
root at geli:/home/schadow # zpool export testpool
root at geli:/home/schadow # zpool import -d zfstc
pool: testpool
id: 16913270329707857467
state: ONLINE
action: The pool can be imported using its name or numeric identifier.
config:
testpool ONLINE
/usr/home/schadow/zfstc/0 ONLINE
/usr/home/schadow/zfstc/1 ONLINE
root at geli:/home/schadow # zpool list
no pools available
root at geli:/home/schadow # zpool import -d zfstc testpool
root at geli:/home/schadow # zpool list
NAME SIZE ALLOC FREE CKPOINT EXPANDSZ FRAG CAP DEDUP HEALTH
ALTROOT
testpool 160M 120K 160M - - 3% 0% 1.00x ONLINE
-
-------------------------------------------------------------------------------------------
So, while this works as a workaround, I still think it is a bug. There is too
much reliance on these file names and paths and whether or not its a symlink,
etc, that should just not matter. And there is also that asymmetry, that I have
to specify full paths for create, but for import only a directory.
It is also a bug because it used to work and then suddenly it stopped working
(for no real benefit AFAICS)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list