CIFS will not start

[SilverJS]

Hi there,

Had some problems with my jail's IP address having to change since I moved in with my wife - couldn't change it (was giving me a dialog concerning the NAME of the jail, which was grayed-out anyways, so I couldn't save) - anyways, decided to upgrade to 9.2.1.2 to start fresh.

But, that resuscitated a bunch of permissions issues that I remember having....and I'm now worse off than I was, as my CIFS won't even start. What I've done so far :

1. Tried what I remember (sorta) from the last time I built this machine, which was about a year and a half ago. That meant creating the share, and hoping everything worked;

2. Then, I followed the guide at

http://doc.freenas.org/index.php/Windows_(CIFS)_Shares

to the letter - the part about anonymous sharing. So now, I could create new files, but still couldn't overwrite current existing ones;

3. Out of desperation, I just SSH'd to the root folder of my share and went

chmod -R 777 *.*

Not sure if that's what it didn't like, but somewhere in my tinkering, my server got mad at me - and now, I can't even start CIFS! Testparm results :

Load smb config files from /usr/local/etc/smb4.conf
max_open_files: increasing sysctl_max (11095) to minimum Windows limit (16384)
rlimit_max: increasing rlimit_max (11095) to minimum Windows limit (16384)
Loaded services file OK.
WARNING: lock directory /var/db/samba4 should have permissions 0755 for browsing to work
WARNING: state directory /var/db/samba4 should have permissions 0755 for browsing to work
WARNING: cache directory /var/db/samba4 should have permissions 0755 for browsing to work
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions

[global]
dos charset = CP437
server string = FreeNAS Server
server role = standalone server
map to guest = Bad User
obey pam restrictions = Yes
smb passwd file = /var/etc/private/smbpasswd
private dir = /var/etc/private
max log size = 51200
time server = Yes
deadtime = 15
hostname lookups = Yes
load printers = No
printcap name = /dev/null
disable spoolss = Yes
dns proxy = No
pid directory = /var/run/samba
panic action = /usr/local/libexec/samba/samba-backtrace
idmap config * : backend = tdb
create mask = 0666
directory mask = 0777
directory name cache size = 0
map archive = No
map readonly = no
store dos attributes = Yes
strict locking = No

Please help - this is enormously frustrating. One more note about the whole "too many files open" thing : if I tried opening files on the share (during the time it was available, of course) and I'd get a notification in Windows that the file was already open by another user, that I could only open a read-only copy.

Looking forward to your replies!

 

[cyberjock]

Can you provide stuff like FreeNAS version, windows versions, hardware on your server, etc?

Just for curiosity, have you tried rebooting FreeNAS?

 

[SilverJS]

Apologies, I should have done that from the beginning.

FreeNAS version : as per text, 9.2.1.2. Although, that's also something interesting : GUI upgrades from my 8.2 to 9.2.1.2 failed, so I had to do a clean install. The ISO for 9.2.1.2 was giving me hardware faults for some reason, so I had to go 9.2.1.1 ISO -> 9.2.1.2 GUI. When my CIFS problems were persisting, I actually did the whole 9.2.1.1 ISO -> 9.2.1.2 GUI a SECOND time - no change;

Windows 7 on all computers;

Server hardware : I have 7 X Hitachi 3TB hard drives in a RaidZ2 config. Asus motherboard with an Athlon X2 255 processor, 8GB ECC RAM.

I did try to reboot, yes. No issues. One more thing : I did have to interrupt a scrub to try to re-install the whole thing (a scrub typically lasts 12h or so, seems like).

 

[cyberjock]

8GB of RAM is a bit short for a pool of that size. Definitely not a good choice, but that's not likely your problem(but it could be).

I can't do much else for you.. I don't use 9.2.1.x because it's had so many problems. I'm still on 9.2.0 and not sure if I'll go to 9.2.1.3 or not. My advice would be to go to 9.2.0 and upload your config file if you still have the old config file from 8.2.

 

[SilverJS]

The pool itself is 10.7 TB. One of the drives is on standby. The pool has been running fine for the last 2 years - that's why this is super frustrating....I just wish I could have what I had two days ago! =)

Anyhow - I actually hadn't thought of 9.2.0. I guess I could try it - nothing to lose at this point!

 

[SilverJS]

But does anybody have any ideas with regards to this whole "too many files open" stuff? Is this something on my end, or most likely some bug of some sort in FreeNAS?

 

[Yatti420]

Is it a SMB error in messages log? As cyberjock said.. Alot of issues with 9.2.1.1/9.2.1.2 espescially SMB/CIFS.. I'm thinking 9.2.1.3 will clean it all up (and be the final build for UFS/x86 hardware) and 9.2.2 will be new & cool..

 

[SilverJS]

SO - two things solved it.

1. 9.2.0;¸

2. Not sure how this played, but I just did it the quick and dirty way. Created a share, allowed guests, done. In other words : didn't follow the guide too closely. But hey, it all works now. I think I'll stick to 9.2 for a while. =)

Thanks for the suggestion!

 

[SilverJS]

OK...so, everything's back to working peachy, except this :

[root@freenas] ~# zpool status
pool: Raidz2
state: ONLINE
status: One or more devices are configured to use a non-native block size.
Expect reduced performance.
action: Replace affected devices with devices that support the
configured block size, or migrate data to a properly configured
pool.
scan: scrub in progress since Sun Mar 16 15:43:59 2014
1.74T scanned out of 7.44T at 286M/s, 5h48m to go
0 repaired, 23.44% done
config:

NAME STATE READ WRITE CKSUM
Raidz2 ONLINE 0 0 0
raidz2-0 ONLINE 0 0 0
gptid/2667ab53-cabf-11e0-90d6-f46d04ee3b78 ONLINE 0 0 0 block size: 512B configured, 4096B native
gptid/278855cd-cabf-11e0-90d6-f46d04ee3b78 ONLINE 0 0 0 block size: 512B configured, 4096B native
gptid/28ba1288-cabf-11e0-90d6-f46d04ee3b78 ONLINE 0 0 0 block size: 512B configured, 4096B native
gptid/29dd22a5-cabf-11e0-90d6-f46d04ee3b78 ONLINE 0 0 0 block size: 512B configured, 4096B native
gptid/fd2ee8c9-e38c-11e2-bc79-f46d04ee3b78 ONLINE 0 0 0 block size: 512B configured, 4096B native
gptid/2f756925-9267-11e2-aed5-f46d04ee3b78 ONLINE 0 0 0 block size: 512B configured, 4096B native
spares
ada7p2 AVAIL

No known data errors.

So - any ideas? Is this a big deal? As you saw, it's in the process of scrubbing right now. Obviously, I never had this problem before. The disks I'm using are perfectly compatible with ZFS.

 

[DJ9]

CJ covered this one pretty good. Here's the link: http://forums.freenas.org/index.php?threads/9-2-non-native-block-size-error.16883/

 

[SilverJS]

Awesome, thanks! Weird that I didn't get that with 9.2.1.1 and .2, though....? Either way, everything works now. =) Thanks for the link.

EDIT : did the zdb -C | grep ashift thing. Turns out I'm at 9. So I'm one of those that, if I understand correctly, should NOT get the warning cuz my ashift and sector size actually match. Am I getting this right?

Either way, safe to ignore by the looks of it. Thanks again for the swift replies.