On Mon, 17 Oct 2016, Eugene M. Zheganin wrote:
Thanks ! It does explain it. But then again, on a pool that has been just
created, I check the properties of the root dataset (I'm posting all the
properties, just to display there's no child datasets or data on the pool):
===Cut===
# zfs get all
Hi.
On 16.10.2016 23:42, Gary Palmer wrote:
You're confusing disk manufacturer gigabytes with real (power of two)
gigabytes. The below turns 960 197 124 096 into real gigabytes
Yup, I thought that smartctl is better than that and already displayed
the size with base 1024. :)
Thanks.
Eugene
Hi.
On 16.10.2016 22:06, Alan Somers wrote:
It's raw size, but the discrepancy is between 1000 and 1024. Smartctl
is reporting base 10 size, but zpool is reporting base 1024..
960197124096.0*6/1024**4 = 5.24 TB, which is pretty close to what
zpool says.
Thanks ! It does explain it. But then aga
On Sun, Oct 16, 2016 at 09:56:10PM +0500, Eugene M. Zheganin wrote:
> Hi.
>
> FreeBSD 11.0-RC1 r303979, zfs raidz1:
>
> ===Cut===
>
> # zpool status gamestop
>pool: gamestop
> state: ONLINE
>scan: none requested
> config:
>
> NAMESTATE READ WRITE CKSUM
>
On Sun, Oct 16, 2016 at 10:56 AM, Eugene M. Zheganin wrote:
> Hi.
>
> FreeBSD 11.0-RC1 r303979, zfs raidz1:
>
> ===Cut===
>
> # zpool status gamestop
> pool: gamestop
> state: ONLINE
> scan: none requested
> config:
>
> NAMESTATE READ WRITE CKSUM
> gamestopONLI
