Hi,
Thanks for the prompt response.
I tried using digest with sha256 to calculate the uberblock checksum. Now,
digest gives me a 65 char's ouput, while zdb -uuu pool-name, gives me only 49
char output.
how can this be accounted?
I'm trying to understand how the checksum is calculated and
14408718082181993222 + 4867536591080553814 - 2^64 + 4015976099930560107 =
484548669948327
there was an overflow inbetween, that I overlooked.
pak
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
Hi,
bash-3.2# isainfo
amd64 i386
The above output shows amd64 is available. But how can I now overcome the
compilation failure issue?
Regards,
pak
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
I just added -xarch=amd64 in Makefile.master and then could compile the driver
without any issues.
Regards,
pak.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
Hi,
I added a vdev(file) to the zpool and then, and using hexedit modified the guid
of the vdev in all four labels. I also, caluculated the new ub_guid_sum and
updated all uberblock guid_sum values. Now, when I try to import this modified
file into the zpool, it says the device is
I'm trying to compile zfs kernel on the following machine
bash-3.2# uname -a
SunOS solaris-b119-44 5.11 snv_119 i86pc i386 i86pc
I set the env properly using bldenv -d ./opensolaris.sh.
bash-3.2# pwd
/export/testws/usr/src/uts
bash-3.2# dmake
dmake: defaulting to parallel mode.
See the man
I've a zfs pool named 'ppool' with two vdevs(files) file1, file2 in it.
zdb -l /pak/file1 output:
version=16
name='ppool'
state=0
txg=3080
pool_guid=14408718082181993222
hostid=8884850
hostname='solaris-b119-44'
top_guid=4867536591080553814
