> "Petter" == Petter Reinholdtsen writes:
Petter> So, should this problem be considered a documentation issue, a local
Petter> configuration error, a bug in the startup scripts or something else?
Petter> In other words, should it be kept over or closed as fixed?
Petter> It
So, should this problem be considered a documentation issue, a local
configuration error, a bug in the startup scripts or something else?
In other words, should it be kept over or closed as fixed?
It is the only open RC issue with zfs on linux.
--
Happy hacking
Petter Reinholdtsen
> "Antonio" == Antonio Russo writes:
>> The pool systematically fails to mount after the upgrade, at each boot,
>> even if I manually mounted it..
Antonio> The terminology with ZFS is a little different: pools are
"imported"
Antonio> and the datasets (that are filesystems
On 9/29/19 2:30 PM, Alberto Berti wrote:
> Hi Antonio,
>
> thanks for answering.
No problem! :-)
>
>> "Antonio" == Antonio Russo writes:
>
> Antonio> Could you please clarify: did you experience any data loss,
> Antonio> or were you simply unable to import your pool at one point?
Could you please clarify: did you experience any data loss, or were you simply
unable to import your pool at one point?
As a second note, you should have done something like
zpool import -d /dev/disks/by-id -a
so that your import is done by labels that are stable across boots (names like
5 matches
Mail list logo
