Internal Error Failed To Initialize Zfs Library Solaris
] [ author ] Hi, even if the zfs module is loaded I get the error message: [norman at harmonia ~]$ kldstat | grep zfs 7 1 0xfffffffffcc1c000 80ee8 zfs.ko [norman at harmonia ~]$ zfs list internal error: failed to initialize ZFS library Anyway thx for the info.. At least now I know why it "should" not work ;-) bye Norman 2008/5/29 Pawel Jakub Dawidek : > On Fri, Apr 11, 2008 at 01:41:28PM -0500, Mark Kane wrote: >> On Fri, Apr 11, 2008, at 15:13:16 +0200, Norman Maurer wrote: >> > Hi all, >> > >> > is it normal that I can't do a 'zfs list' ( for example ) as non-root >> > user ? >> > >> > $ zfs list >> > internal error: failed to initialize ZFS library >> > >> > I think there is really a use case for use some zfs commands as >> > non-root user.. >> > >> > Thx >> > Norman >> >> Hi. >> >> One way to do this as a non-root user is to add the account to the >> "operator" group. This is what I do on my personal desktop machine >> and it has worked fine, but I understand that may not be best in all >> cases. >> >> You might also try changing the permissions on /dev/zfs. I don't do >> this method and I'm not sure if it's a proper way, but from trying it >> very briefly it seems to work correctly with the user not in the >> "operator" group. > > In Solaris anyone can open /dev/zfs and the kernel side of ZFS decides > if the user has permission to perform some action or not. In FreeBSD we > try to be more careful for now, but it will change soon, once we import > delegated administration functionality. > > Although... The error above (failed to initialize ZFS library) most > likely means that zfs.ko module wasn't loaded. zfs(8) tries to do that > automatically, but of course it will only succeed if we are root. In > this case zfs.ko has to be manually loaded by root and then members of > operator group can use zfs(8) command. > > -- > Pawel Jakub Dawidek http://www.wheel.pl > pjd at FreeBSD.org http://www.FreeBSD.org > FreeBSD committer Am I Evil? Yes, I Am! > Previous message: mpd5 stoped working after subnet change Next message: zfs list and non-root user Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the freebsd-questions mailing list
van GoogleInloggenVerborgen veldenZoeken naar groepen of berichten
Date: Mon, 30 Jan 2012 14:57:03 +0000 Hi, What is the current state of the ZFS port at https://mail-index.netbsd.org/current-users/2012/01/30/msg018958.html 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 internal error 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: internal error failed 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. Chavdar Ivanov -- ---- Follow-Ups: Re: State of the ZFS port From: Nicolas Joly Prev by Date: Re: System freeze w/display strangeness on amd64/current Next by Date: Re: System freeze w/display strangeness on amd64/current Previous by Thread: daily CVS update output Next by Thread: Re: State of the ZFS port Indexes: reverse Date reverse Thread Old Index Home | Main Index | Thread Index | Old Index