This is really strange... You get 100MB read with 8.0.3 and I get a maximum of 50MB with all tweaks enabled... And my CPU is 98% idle...
-
Important Announcement for the TrueNAS Community.
The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums
- Status
This is really strange... You get 100MB read with 8.0.3 and I get a maximum of 50MB with all tweaks enabled... And my CPU is 98% idle...
It strange... Sorry, but i'm happy with my system now :)
My smb.conf looks like this:
Code:
cat /usr/local/etc/smb.conf
[global]
encrypt passwords = yes
dns proxy = no
strict locking = no
read raw = yes
write raw = yes
oplocks = yes
max xmit = 65535
deadtime = 15
display charset = LOCALE
max log size = 10
syslog only = yes
syslog = yes
load printers = no
printing = bsd
printcap name = /dev/null
disable spoolss = yes
smb passwd file = /var/etc/private/smbpasswd
private dir = /var/etc/private
getwd cache = yes
guest account = nobody
map to guest = Bad Password
netbios name = freenas
workgroup = WORKGROUP
server string = FreeNAS Server
use sendfile = yes
ea support = yes
store dos attributes = yes
local master = yes
time server = yes
security = user
create mask = 0666
create mask = 0666
directory mask = 0777
client ntlmv2 auth = yes
dos charset = CP437
unix charset = UTF-8
log level = 1
aio read size = 1
aio write size = 1
[Video]
path = /mnt/pool/Video
printable = no
veto files = /.snap/.windows/
writeable = no
browseable = yes
inherit owner = no
inherit permissions = no
vfs objects = zfsacl
inherit acls = Yes
map archive = No
map readonly = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = yes
valid users=@Eltern,oplay
invalid users=@Kinder
write list=gerd
[Musik]
path = /mnt/pool/Musik
printable = no
veto files = /.snap/.windows/
writeable = no
browseable = yes
inherit owner = no
inherit permissions = no
vfs objects = zfsacl
inherit acls = Yes
map archive = No
map readonly = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = yes
valid users=@Eltern
invalid users=@Kinder
write list=gerd
[Public]
path = /mnt/pool/Public
printable = no
veto files = /.snap/.windows/
writeable = yes
browseable = yes
inherit owner = no
inherit permissions = no
vfs objects = zfsacl
inherit acls = Yes
map archive = No
map readonly = no
nfs4:mode = special
nfs4:acedup = merge
nfs4:chown = yes
valid users=@Eltern,@Kinder
Remark: I've not upgraded my zpool from rev. 13 to 15 after installing the new freenas system. That way i could go down to 0.7.2 (plug in different usb stick).
Code:
zpool status
pool: pool
state: ONLINE
status: The pool is formatted using an older on-disk format. The pool can
still be used, but some features are unavailable.
action: Upgrade the pool using 'zpool upgrade'. Once this is done, the
pool will no longer be accessible on older software versions.
scrub: scrub completed after 4h10m with 0 errors on Sat Jan 7 07:13:17 2012
config:
NAME STATE READ WRITE CKSUM
pool ONLINE 0 0 0
raidz1 ONLINE 0 0 0
ada0 ONLINE 0 0 0 43K repaired
ada1 ONLINE 0 0 0
ada2 ONLINE 0 0 0 43K repaired
ada3 ONLINE 0 0 0
errors: No known data errors
- Joined
- May 28, 2011
- Messages
- 10,994
Still not sure what is going on. I built r9453 of 8.0.3 and set Multimedia = 1. I even reset all settings to default and I still am having Dyndns issues.
There were no problems reported during the build. This is two builds I've created that have had this problem. Some how it looks like build issues have crept into the code somewhere.
There were no problems reported during the build. This is two builds I've created that have had this problem. Some how it looks like build issues have crept into the code somewhere.
Code:
Jan 8 11:55:51 freenas freenas[1681]: Executing: /usr/sbin/service ix-inadyn quietstart
Jan 8 11:55:51 freenas freenas[1681]: Executing: /usr/sbin/service inadyn restart
Jan 8 11:55:51 freenas freenas: inadyn not running?
Jan 8 11:55:51 freenas freenas: Starting inadyn.
Jan 8 11:55:51 freenas freenas: /usr/local/bin/inadyn: 1: Syntax error: "(" unexpected
Jan 8 11:55:51 freenas root: /usr/local/etc/rc.d/inadyn: WARNING: failed to start inadyn
Jan 8 11:55:51 freenas freenas: /usr/local/etc/rc.d/inadyn: WARNING: failed to start inadyn
Jan 8 11:55:52 freenas freenas[1681]: Executing: /bin/pgrep inadyn
G
gcooper
Guest
I believe I fixed the inadyn and xvid build issues. Please update and let me know how things go.
G
gcooper
Guest
Reading these values is only valid when transferring data to/from Samba, not before or after; it might help to note the before and after when factoring in additional sources for the AIO numbers, but if we were doing proper performance analysis we need to do everything in single-user mode, with minimal processes running, etc.
- Joined
- May 28, 2011
- Messages
- 10,994
First build failed:
Code:
02:06:42 ## [176/177] customize "fix_easy_install_pth" 02:06:42 ### log: /usr/local/freenas/trunk/obj.amd64/_.cust.fix_easy_install_pth do_build.sh: ERROR: FreeNAS build FAILED; please check above log for more details
Contents of _.cust.fix_easy_install_pth
Code:
+ fix_easy_install_pth + local site_packages + site_packages=/usr/local/freenas/trunk/obj.amd64/_.w/usr/local/lib/python2.7/site-packages + env PYTHONPATH=/usr/local/freenas/trunk/obj.amd64/_.w/usr/local/lib/python2.7/site-packages python /usr/local/freenas/trunk/tools/sanitize_pth.py -f /usr/local/freenas/trunk/obj.amd64/_.w/usr/local/lib/python2.7/site-packages env: python: No such file or directory
I will rebuild one more time to confirm the failure.
EDIT: I will update FreeBSD and the ports collection before I build again but below is the configuration I used for the first build.
Are you expecting python to be installed on the build system now?
This is what I currently have for packages installed on my build system:
Code:
apr-ipv6-devrandom-gdbm-db42-1.4.2.1.3.10 Apache Portability Library bash-4.1.9 The GNU Project's Bourne Again SHell cdrtools-3.00_1 CD/DVD/BluRay and ISO-9660 image creation and extraction to db42-4.2.52_5 The Berkeley DB package, revision 4.2 expat-2.0.1_1 XML 1.0 parser written in C gdbm-1.8.3_3 The GNU database manager gettext-0.18.1.1 GNU gettext package libiconv-1.13.1_1 A character set conversion library neon29-0.29.5 An HTTP and WebDAV client library for Unix systems pkg-config-0.25_1 A utility to retrieve information about installed libraries sqlite3-3.7.4 An SQL database engine in a C library subversion-1.6.15 Version control system
ApolloDS
Dabbler
- Joined
- Jan 6, 2012
- Messages
- 13
Could not receive trustdoms
Hi all
I think I found a bug in FreeNAS 8.0.3.
I activated the Active Directory Integration which was working fine.
After a reboot I always get the message "Could not receive trustdoms" in /var/log/samba/log.winbindd and in the console log.
I stop and start Active Directory but this doesn't help.
I checked the time is in sync to the Domain Controller of the AD.
Any hint how to solve this?
Hi all
I think I found a bug in FreeNAS 8.0.3.
I activated the Active Directory Integration which was working fine.
After a reboot I always get the message "Could not receive trustdoms" in /var/log/samba/log.winbindd and in the console log.
I stop and start Active Directory but this doesn't help.
I checked the time is in sync to the Domain Controller of the AD.
Any hint how to solve this?
G
gcooper
Guest
Yeah, it needs python now. I'll update the docs.
G
gcooper
Guest
Docs updated, s.t. README now notes what tools are required to build FreeNAS.
- Joined
- May 28, 2011
- Messages
- 10,994
Builds fine first go around with the addition of Python. I'm going to build it twice more just to ensure no glitches. Dyndns worked fine. Still need to configure minidlna and test. I don't use the other multimedia applications so I can't really test those. I'll post when I'm completed. I also do not expect to test any other functionality such as how fast or slow Samba is or isn't. I'll leave that up to someone else. I've got a funeral to attend shortly and it's going to be a long evening.
G
gcooper
Guest
Check and see if you can resolve the PDC via DNS. If not, it's an issue that will be fixed shortly in 8.0.3-RELEASE-p1 (I can point you to the ticket if interested).
G
gcooper
Guest
Thanks for the help and sorry to hear about that :(..
- Joined
- May 28, 2011
- Messages
- 10,994
FreeNAS-8.0.3-RELEASE-p1-x64 (9470) appears to be working fine for me, well on my VM, I'll place on the real deal possibly tomorrow and report any abnormalities. Built three times in a row without a single failure. Runs DYNDNS and minidlna fine too. It was a friends father. The fella retained his wits (sharp as a tack) and was fun to be around. I hope my buddy lasts as long, a few weeks shy of 92.
Might I recommend you place this a new version up on the main FreeNAS webpage unless you know of some main issue with it. I think it's ready.
Might I recommend you place this a new version up on the main FreeNAS webpage unless you know of some main issue with it. I think it's ready.
G
gcooper
Guest
Thanks for the clarification. Each time you build though, you need to do it from a fresh workspace or delete the package, else it'll pick up the original package.
FWIW it turns out it was a ports Makefile bug too -- but that's just a sidenote: ports/163942 .
Sorry to hear that man :(.. I could only hope to live that long.
Someone reported that ZFS + shadow copy functionality is broken because of a secret sauce patch gone missing from the samba35 patchset, but I need to verify this first.
That and setup the SPEC benchmark on 4GbE to generate new numbers; the last numbers I got were ok several months ago with absolute minimal tuning, but the new ones will probably be better now.
- Joined
- May 28, 2011
- Messages
- 10,994
For the past several months I have been deleting the entire trunk and download it all again. In this instance I deleted the entire trunk and built the same version each time vice just downloading the latest version because I wanted to compare apples to apples. You did stick an orange in there with the updated instructions and then the two other changes adding and deleting same data. None of those changes should have made a difference BUT things bite you when you least expect it. I'll have to look up what a shadow copy is so I can possibly test it out myself.
G
gcooper
Guest
gcooper said:
shadow_copy* is indeed broken in samba36. I've filed a ticket here: http://support.freenas.org/ticket/1186.
G
gcooper
Guest
Sorry for taking so long. I've been busy with work and my iX workstation tanked so it's going to take me until Tuesday to set everything up again to run the SPEC-SFS tests. I'm frustrated that I'm hitting so many speedbumps trying to get this work finalized...
Just tried to upgrade from 8.0.2 to 8.0.3 with the GUI ugrade option and the system frooze, tried to reboot and it did not. Unplugged my USB stick and put in another computer, and it wont be recognized, not by diskpart and not by BIOS, so it seems the upgrade destroyed it somehow :( Have no logs.
- Joined
- May 28, 2011
- Messages
- 10,994
There is no way the upgrade could physically destroy your USB stick. It's not possible, well unless you did the upgrade during the leap second adjustment (compensates for the slowing earth rotation) at which point the software builds up a very small charge of gamma radiation and it has been know to slip out of the containment field and destroy nearby electronics or cause small animals to glow green for a few hours. I would suggest that either the USB stick was exposed to this rare phenomenon causing a hardware failure or you need to plug the USB stick into another USB port on a computer, directly to a MB connection is the best, and format the stick. If Windoze doesn't see it, try booting gparted being careful and knowing what drive you are going to format. In fact, use gparted on your NAS but unplug the hard drives first to keep you from making a bad mistake.
In either case I would recommend replacing the USB stick. You haven't given any details on your system nor what brand/model USB stick you have. Do not use USB3 (just my recommendation, not the port, not the USB stick) because support is spotty. It will work for some, fail for others. Please provide your details on your hardware.
Thanks
Good to hear you so absolute 100% sure about that.
Must be one of the most useless and stupid answers i have ever seen on a forum.
Anyway, i rebooted before doing the upgrade and it booted just fine, tried the upgrade and the machine froze up, and after that the USB stick cant be recognized in any system i try it, and i tried in 3 different systems, both Windows and Linux without success. The stick was a "LACIE USB MOSKEYTO 4GB USB 2.0" plugged in to the back of a ASUS P5Q Deluxe.
Perhaps the stick was bad, i don't know, but it still worked before the unsuccessful upgrade process, and did not after.
- Status
