NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ZFS Howto first cut



Chavdar Ivanov <ci4ic4%gmail.com@localhost> writes:

[snip]

> Oh, dear; I was way too quick.
>
> The zfs file system is thus mounted on the remote system, but any
> operation on it panics the NFS ZFS server:
>
> ...
> (gdb) target kvm netbsd.14.core
> 0xffffffff80224235 in cpu_reboot ()
> (gdb) bt
> #0  0xffffffff80224235 in cpu_reboot ()
> #1  0xffffffff809fe1cf in kern_reboot ()
> #2  0xffffffff80a40649 in vpanic ()
> #3  0xffffffff80a4070d in panic ()
> #4  0xffffffff802266ad in trap ()
> #5  0xffffffff8021ed43 in alltraps ()
> #6  0xffffffff81f05091 in zfs_log_create ()
> #7  0xffffffff81f1209a in zfs_netbsd_mkdir ()
> #8  0xffffffff80ab1b89 in VOP_MKDIR ()
> #9  0xffffffff8090e0e1 in nfsrv_mkdir ()
> #10 0xffffffff80922482 in do_nfssvc ()
> #11 0xffffffff80255cf9 in syscall ()
> #12 0xffffffff802096ad in handle_syscall ()
> ...
>
> So, for now, it doesn't seem to work at all for me on -current from
> 29/02/2020. The sharenfs attribute doesn't matter.
>
> If I use netbsd.gdb, it doesn't show the symbols from below alltraps -
> from modules, methinks.
>
> As the client had the filesystem mounted still, the panic became
> cyclic and I had to break single user and disable zfs and remove the
> filesystem from /etc/exports to be able to continue; the latter would
> have been enough.


I am able to use NFS against ZFS filesets in NetBSD 9.0_STABLE.
Operations appear to work and it doesn't panic the server.



-- 
Brad Spencer - brad%anduin.eldar.org@localhost - KC8VKS - http://anduin.eldar.org



Home | Main Index | Thread Index | Old Index