Samba + ZFS


Hello all

I am running a test machine (dual PIII 1Ghz HP Netserver E800) with Current as of yesterday

I have installed Samba 3.0.25,1And I have two scsi drives da1 and da2 as a zfs mirror. the base system is a another disk da0

My zfs output.



zfs list



NAME USED AVAIL REFER MOUNTPOINT
tank 19.2G 14.0G 18K /tank
tank/samba 19.2G 14.0G 18.1G /usr/local/samba
tank/samba@justincase 1.09G - 1.36G -


zpool status
pool: tank
state: ONLINE
scrub: none requested
config:

NAME STATE READ WRITE CKSUM
tank ONLINE 0 0 0
mirror ONLINE 0 0 0
da1 ONLINE 0 0 0
da2 ONLINE 0 0 0

errors: No known data errors


In my smb.conf i have the following share definition.



# directory, for media files
[mediafiles]
comment = mediafiles
path = /usr/local/samba
writable = yes
admin users = MYDOMAIN|administrator

this is a share on the zfs pool
The issue is that i can not access the share! i get the following error in /var/log/massages

May 31 14:09:44 sbsd001 smbd[60464]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(41)
May 31 14:09:44 sbsd001 kernel: pid 60464 (smbd), uid 0: exited on signal 6
May 31 14:09:44 sbsd001 smbd[60464]: ===============================================================
May 31 14:09:44 sbsd001 smbd[60464]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(42)
May 31 14:09:44 sbsd001 smbd[60464]: INTERNAL ERROR: Signal 6 in pid 60464 (3.0.25)
May 31 14:09:44 sbsd001 smbd[60464]: Please read the Trouble-Shooting section of the Samba3-HOWTO
May 31 14:09:44 sbsd001 smbd[60464]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(44)
May 31 14:09:44 sbsd001 smbd[60464]:
May 31 14:09:44 sbsd001 smbd[60464]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May 31 14:09:44 sbsd001 smbd[60464]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(45)
May 31 14:09:44 sbsd001 smbd[60464]: ===============================================================
May 31 14:09:44 sbsd001 smbd[60464]: [2007/05/31 14:09:44, 0] lib/util.c:smb_panic(1632)
May 31 14:09:44 sbsd001 smbd[60464]: PANIC (pid 60464): internal error
May 31 14:09:44 sbsd001 smbd[60464]: [2007/05/31 14:09:44, 0] lib/util.c:log_stack_trace(1786)
May 31 14:09:44 sbsd001 smbd[60464]: unable to produce a stack trace on this platform
May 31 14:09:44 sbsd001 smbd[60464]: [2007/05/31 14:09:44, 0] lib/fault.c:dump_core(181)
May 31 14:09:44 sbsd001 smbd[60464]: dumping core in /var/log/samba/cores/smbd
May 31 14:09:44 sbsd001 smbd[60464]:
May 31 14:09:44 sbsd001 smbd[60465]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(41)
May 31 14:09:44 sbsd001 kernel: pid 60465 (smbd), uid 0: exited on signal 6
May 31 14:09:44 sbsd001 smbd[60465]: ===============================================================
May 31 14:09:44 sbsd001 smbd[60465]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(42)
May 31 14:09:44 sbsd001 smbd[60465]: INTERNAL ERROR: Signal 6 in pid 60465 (3.0.25)
May 31 14:09:44 sbsd001 smbd[60465]: Please read the Trouble-Shooting section of the Samba3-HOWTO
May 31 14:09:44 sbsd001 smbd[60465]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(44)
May 31 14:09:44 sbsd001 smbd[60465]:
May 31 14:09:44 sbsd001 smbd[60465]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May 31 14:09:44 sbsd001 smbd[60465]: [2007/05/31 14:09:44, 0] lib/fault.c:fault_report(45)
May 31 14:09:44 sbsd001 smbd[60465]: ===============================================================
May 31 14:09:44 sbsd001 smbd[60465]: [2007/05/31 14:09:44, 0] lib/util.c:smb_panic(1632)
May 31 14:09:44 sbsd001 smbd[60465]: PANIC (pid 60465): internal error
May 31 14:09:44 sbsd001 smbd[60465]: [2007/05/31 14:09:44, 0] lib/util.c:log_stack_trace(1786)
May 31 14:09:44 sbsd001 smbd[60465]: unable to produce a stack trace on this platform
May 31 14:09:44 sbsd001 smbd[60465]: [2007/05/31 14:09:44, 0] lib/fault.c:dump_core(181)
May 31 14:09:44 sbsd001 smbd[60465]: dumping core in /var/log/samba/cores/smbd
May 31 14:09:44 sbsd001 smbd[60465]:
May 31 14:09:45 sbsd001 smbd[60474]: [2007/05/31 14:09:45, 0] lib/fault.c:fault_report(41)
May 31 14:09:45 sbsd001 smbd[60474]: ===============================================================
May 31 14:09:45 sbsd001 kernel: pid 60474 (smbd), uid 0: exited on signal 6
May 31 14:09:45 sbsd001 smbd[60474]: [2007/05/31 14:09:45, 0] lib/fault.c:fault_report(42)
May 31 14:09:45 sbsd001 smbd[60474]: INTERNAL ERROR: Signal 6 in pid 60474 (3.0.25)
May 31 14:09:45 sbsd001 smbd[60474]: Please read the Trouble-Shooting section of the Samba3-HOWTO
May 31 14:09:45 sbsd001 smbd[60474]: [2007/05/31 14:09:45, 0] lib/fault.c:fault_report(44)
May 31 14:09:45 sbsd001 smbd[60474]:
May 31 14:09:45 sbsd001 smbd[60474]: From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
May 31 14:09:45 sbsd001 smbd[60474]: [2007/05/31 14:09:45, 0] lib/fault.c:fault_report(45)
May 31 14:09:45 sbsd001 smbd[60474]: ===============================================================
May 31 14:09:45 sbsd001 smbd[60474]: [2007/05/31 14:09:45, 0] lib/util.c:smb_panic(1632)
May 31 14:09:45 sbsd001 smbd[60474]: PANIC (pid 60474): internal error
May 31 14:09:45 sbsd001 smbd[60474]: [2007/05/31 14:09:45, 0] lib/util.c:log_stack_trace(1786)
May 31 14:09:45 sbsd001 smbd[60474]: unable to produce a stack trace on this platform
May 31 14:09:45 sbsd001 smbd[60474]: [2007/05/31 14:09:45, 0] lib/fault.c:dump_core(181)
May 31 14:09:45 sbsd001 smbd[60474]: dumping core in /var/log/samba/cores/smbd
May 31 14:09:45 sbsd001 smbd[60474]:

If i copy the /usr/local/samba dir to /usr/ and edit my smb.conf file so the share location reads

path = /usr/samba

All is fine i can acces the share.
Al permissions on the directory are the same.


uname -a
FreeBSD sbsd001.double-l.local 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Wed May 30 11:42:26 CEST 2007 root@xxxxxxxxxxxxxxxxxxxxxx:/usr/obj/usr/src/sys/KRNL i386

Am i doing something wrong ?

regards,

Johan Hendriks








_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: ZFS: amd64, devd, root file system.
    ... I even performed a "boot -v" but did not see anything useful. ... replicas for the pool to continue functioning. ... It seems that ZFS "legacy" mounts are not supported under FreeBSD, ... no other way to mount it since we do not have a "mount_zfs", ...
    (freebsd-current)
  • Re: ZFS: amd64, devd, root file system.
    ... There after the pool could be mounted and I could manually set up the ... loaded with the kernel and the zfs module. ... It appears, that a zpool can be manually mounted if it resides on ad0s2, ... made me suspicious and I prepared a ZFS root in test2. ...
    (freebsd-current)
  • (no subject)
    ... My zfs output. ... mirror ONLINE 0 0 0 ... comment = mediafiles ... this is a share on the zfs pool ...
    (freebsd-current)
  • Re: ZFS: amd64, devd, root file system.
    ... There after the pool could be mounted and I could manually set up the ... tests) unused swap partition on my "normal" UFS system disk (which I ... or does ZFS mount them automatically when the pool "test" is mounted? ... I assume that "zfs mount -a" will ignore file systems that are ...
    (freebsd-current)
  • Re: Encrypted zfs?
    ... Afterwards they remove all of them, shuffle them, ... ZFS has no trouble ... If you don't export the pool before ... ATA disks. ...
    (freebsd-current)