zfs crypto discuss - Oct 2007 - alpha release and current zpools not working?

Hello,

I did a bfu install from the current alpha release on build 69.
After the reboot i had an error with not starting the HAL service, after some
searching i found that i was missing libexpat.so.1
I found this thread :
http://www.opensolaris.org/jive/thread.jspa?threadID=34225&tstart=45, and
installed libexpat from source.
After that HAL is running perfectly, but i am having another problem.
All my current pools are marked as ''faulted''

I can reboot back to my normal build 69, where i can import the pools without
problems.
Is the alpha release not working with zfs version 8? or do i have another
problem?
greets Leon

----------------------------
blog: http://logic855.no-ip.info/blog
msn: logic855 at hotmail.com
 
 
This message posted from opensolaris.org

Leon Versteeg wrote:
> Hello,
> 
> I did a bfu install from the current alpha release on build 69.
> After the reboot i had an error with not starting the HAL service, after
some searching i found that i was missing libexpat.so.1
> I found this thread :
http://www.opensolaris.org/jive/thread.jspa?threadID=34225&tstart=45, and
installed libexpat from source.
> After that HAL is running perfectly, but i am having another problem.
> All my current pools are marked as ''faulted''
> 
> I can reboot back to my normal build 69, where i can import the pools
without problems.
> Is the alpha release not working with zfs version 8? or do i have another
problem?
> greets Leon
> 
I''m observing similar behavior.  When I create a pool from a 
non-zfscrypto BE (Boot Environment) and then try to import the pool in a 
zfscrypto BE it is faulted and the device is unavailable.

In my personal testing I had done all of it inside a zfscrypto BE, so I 
personally haven''t even looked at the import or upgrade cases..

Tony

Leon Versteeg wrote:
> Hello,
> 
> I did a bfu install from the current alpha release on build 69.
> After the reboot i had an error with not starting the HAL service, after
some searching i found that i was missing libexpat.so.1
> I found this thread :
http://www.opensolaris.org/jive/thread.jspa?threadID=34225&tstart=45, and
installed libexpat from source.
> After that HAL is running perfectly, but i am having another problem.
> All my current pools are marked as ''faulted''
> 
> I can reboot back to my normal build 69, where i can import the pools
without problems.
> Is the alpha release not working with zfs version 8? or do i have another
problem?
> greets Leon
I''ll look into this, but note that you should need to upgrade the pool 
to version 9 before crypto will work anyway.

-- 
Darren J Moffat

Leon Versteeg wrote:
> Hello,
> 
> I did a bfu install from the current alpha release on build 69.
> After the reboot i had an error with not starting the HAL service, after
some searching i found that i was missing libexpat.so.1
> I found this thread :
http://www.opensolaris.org/jive/thread.jspa?threadID=34225&tstart=45, and
installed libexpat from source.
> After that HAL is running perfectly, but i am having another problem.
> All my current pools are marked as ''faulted''
The "ZFS Crypto" binaries are using the kcf crypto_digest() functions
to
  do the sha256 checksums rather than the local copy of sha256 that is 
in ZFS normally.

Either there is a bug in how I''m using crypto_digest() or there is a
bug
in the original sha256 implementation in ZFS.   However running the 
zio_checksum_SHA256 code in userland and comparing it with SHA256 code 
from libmd (which is identical to what crypto_digest() ends up using) I 
don''t see any differences.

Still debugging but at least I know roughly where the issue is.

-- 
Darren J Moffat