Re: State of the ZFS port

[christos%astron.com@localhost (Christos Zoulas)]

In article 
<CAG0OUxgLdPe=Ep-e36dZ=zy+vApFUvePn+9ULQuhXwzVGvaPEw%mail.gmail.com@localhost>,
Chavdar Ivanov  <ci4ic4%gmail.com@localhost> wrote:
>On 30 January 2012 15:23, Nicolas Joly <njoly%pasteur.fr@localhost> wrote:
>> On Mon, Jan 30, 2012 at 02:57:03PM +0000, Chavdar Ivanov wrote:
>>> Hi,
>>>
>>> What is the current state of the ZFS port at the moment? is it good
>>> enough at least for testing (I've read the TODO file and realize it is
>>> not yet production quality).
>>>
>>> I am getting:
>>>
>>>
>>> root@nex07 /home/xci # uname -a
>>> NetBSD nex07 5.99.62 NetBSD 5.99.62 (GENERIC) #0: Sun Jan 29 14:26:24
>>> GMT 2012
> root@nex07:/usr/obj/auto-current/amd64/sys/arch/amd64/compile/GENERIC
>>> amd64
>>> root@nex07 /home/xci # zpool status
>>> internal error: failed to initialize ZFS library
>>> 1 root@nex07 /home/xci # modload solaris
>>> modload: File exists
>>> 1 root@nex07 /home/xci # modload zfs
>>> modload: Cannot allocate memory
>>> 1 root@nex07 /home/xci # dmesg | tail -3
>>> uid 0, pid 28945, command ld, on /usr: file system full
>>> kobj_load, 416: [%M/zfs/zfs.kmod]: linker error: out of memory
>>> kobj_load, 416: [%M/zfs/zfs.kmod]: linker error: out of memory
>>> root@nex07 /home/xci # dmesg | grep -i mem
>>> total memory = 20471 MB
>>> avail memory = 19832 MB
>>>
>>>
>>> I've seen some discussions about this; earlier the problem seemed to
>>> be that one had to manually create /etc/zfs, then it worked; now this
>>> is in place, but the module does not load.
>>
>> IIRC the zfs module is build with debug information turned on, which
>> makes it too big to be loaded on, at least, amd64. Could you try with
>> a stripped version ?
>
>If you mean just to strip zfs.kmod, I tried this and am getting
>
>root@nex07 /stand/amd64/5.99.62/modules/zfs # modload ./zfs.kmod
>modload: Exec format error

no, either just strip the debugging symbols or rebuild it without debugging.
Stripping everything does not work.

christos