Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Sep 2017 16:51:41 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 222199] zfs command crashed with option checksum=skein
Message-ID:  <bug-222199-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D222199

            Bug ID: 222199
           Summary: zfs command crashed with option checksum=3Dskein
           Product: Base System
           Version: 11.1-STABLE
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: bin
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: sternix@gmail.com

Hi=20

My FreeBSD version is:
FreeBSD ... 11.1-RELEASE-p1 FreeBSD 11.1-RELEASE-p1 #0: Wed Aug  9 11:55:48=
 UTC
2017     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  a=
md64

i want to to test zfs's skein checksum option

in man page ( man 8 zfs )
"The sha512, and skein checksum algorithms require enabling the appropriate
features on the pool."

The feature is enabled i think

# zpool get feature@skein
NAME   PROPERTY       VALUE          SOURCE
zroot  feature@skein  enabled        local

when i want to create a test dataset with the command
# zfs create -o checksum=3Dskein zroot/test
 internal error: Result too large
 Abort (core dumped)

trying create a dataset and set property is not work either
# zfs create zroot/test
# zfs set checksum=3Dskein zroot/test
cannot set property for 'zroot/test': property setting is not allowed on ro=
ot
pools

and=20

# zfs set checksum=3Dskein zroot
Cannot set property for 'zroot': property setting is not allowed on root po=
ols

am i doing something wrong or is this a bug ?
Can you help?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-222199-8>