Problem with SMB2 and Windows 8

[OlaNys]

I have a problem with Samba crashing now and then,
Nas4Free 9.1.0.1 - Sandstorm (revision 573)
Client is Windows 8.

It probabably is this bug:
https://bugzilla.samba.org/show_bug.cgi?id=8726
(Bug 8726 - SMB2 protocol crashes smbd inconsistently without any reasons)

Just wanted to show you others it is with samba the bug is.

[raulfg3]

replace in your browser index.php by status.php this generate a complete report of your NAS, zip it and atach to this post, perhaps you have tune problems, not necesary SMB bugs.

[OlaNys]

Ok, attached status report as zip.

BR
Ola

[raulfg3]

OK several issues:
1 do you use raid5 , is recomended to use raidZ1 , that is simmilar but more robust:
this can cause problems like:

Code: Select all

Trying to mount root from ufs:/dev/ufsid/50d76da10db7d214 [rw]...
GEOM_RAID5: registered shutdown event handler.
GEOM_RAID5: bigdisk: device created (stripesize=131072).
GEOM_RAID5: bigdisk: ada4(3): newest disk data (CALM): 0.
GEOM_RAID5: bigdisk: ada4(3): disk attached.
GEOM_RAID5: bigdisk: ada3(2): newest disk data (CALM): 0.
GEOM_RAID5: bigdisk: ada3(2): disk attached.
GEOM_RAID5: bigdisk: ada2(1): newest disk data (CALM): 0.
GEOM_RAID5: bigdisk: ada2(1): disk attached.
GEOM_RAID5: bigdisk: ada0(0): newest disk data (CALM): 0.
GEOM_RAID5: bigdisk: ada0(0): disk attached.
GEOM_RAID5: bigdisk: activated.
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 12.05% p:0 ETA:5min (cause: store verify progress).
aesni0: No AESNI support.
GEOM_ELI: Device raid5/bigdisk.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: software
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 12.88% p:15 ETA:354min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 13.72% p:24 ETA:348min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 14.57% p:16 ETA:340min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 15.41% p:24 ETA:337min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 16.26% p:17 ETA:333min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 17.11% p:22 ETA:330min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 17.96% p:13 ETA:323min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 18.79% p:29 ETA:327min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 19.63% p:21 ETA:320min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 20.48% p:16 ETA:313min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 20.56% p:20 ETA:445min (cause: state hot).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 21.37% p:43 ETA:324min (cause: store verify progress).
GEOM_RAID5: bigdisk: ada0(0): re-sync in progress: 22.21% p:25 ETA:313min (cause: store verify progress).

2 YOU use SMB2:

Code: Select all

global]
encrypt passwords = yes
netbios name = nas4free
workgroup = NYNET
server string = NAS4Free Server
security = ads
max protocol = SMB2

Please use NT1 instead

3 you have this error:

Code: Select all

Jan 10 19:33:54 nas4free smbd[80452]:   ===============================================================
Jan 10 19:33:54 nas4free smbd[80452]: [2013/01/10 19:33:54.204250,  0] lib/fault.c:52(fault_report)
Jan 10 19:33:54 nas4free smbd[80452]:   INTERNAL ERROR: Signal 11 in pid 80452 (3.6.10)
Jan 10 19:33:54 nas4free smbd[80452]:   Please read the Trouble-Shooting section of the Samba3-HOWTO
Jan 10 19:33:54 nas4free smbd[80452]: [2013/01/10 19:33:54.204276,  0] lib/fault.c:54(fault_report)
Jan 10 19:33:54 nas4free smbd[80452]:
Jan 10 19:33:54 nas4free smbd[80452]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Jan 10 19:33:54 nas4free smbd[80452]: [2013/01/10 19:33:54.204297,  0] lib/fault.c:55(fault_report)
Jan 10 19:33:54 nas4free smbd[80452]:   ===============================================================

Not sure, try NT1 & AIO if not works, perhaps you have reason and SMB have a bug.

viewtopic.php?f=57&t=2286

[OlaNys]

OK several issues:
1 do you use raid5 , is recomended to use raidZ1 , that is simmilar but more robust:

I have GEOM-encruption on top of my raid5. Can I have than on Raidz1 too?

2 YOU use SMB2:

Code: Select all

global]
encrypt passwords = yes
netbios name = nas4free
workgroup = NYNET
server string = NAS4Free Server
security = ads
max protocol = SMB2

Please use NT1 instead

I know, smb2 is faster and, worked fine before.
I will change to see is smb1/NT1 is more stable.

3 you have this error:

Code: Select all

Jan 10 19:33:54 nas4free smbd[80452]:   ===============================================================
Jan 10 19:33:54 nas4free smbd[80452]: [2013/01/10 19:33:54.204250,  0] lib/fault.c:52(fault_report)
Jan 10 19:33:54 nas4free smbd[80452]:   INTERNAL ERROR: Signal 11 in pid 80452 (3.6.10)
Jan 10 19:33:54 nas4free smbd[80452]:   Please read the Trouble-Shooting section of the Samba3-HOWTO
Jan 10 19:33:54 nas4free smbd[80452]: [2013/01/10 19:33:54.204276,  0] lib/fault.c:54(fault_report)
Jan 10 19:33:54 nas4free smbd[80452]:
Jan 10 19:33:54 nas4free smbd[80452]:   From: http://www.samba.org/samba/docs/Samba3-HOWTO.pdf
Jan 10 19:33:54 nas4free smbd[80452]: [2013/01/10 19:33:54.204297,  0] lib/fault.c:55(fault_report)
Jan 10 19:33:54 nas4free smbd[80452]:   ===============================================================

Not sure, try NT1 & AIO if not works, perhaps you have reason and SMB have a bug.
viewtopic.php?f=57&t=2286

It looks like the bug I was linking in to in my first post.

[raulfg3]

I have GEOM-encruption on top of my raid5. Can I have than on Raidz1 too?

NO in native ZFS mode , you need to wait to ZFS v30 to have this option: http://en.wikipedia.org/wiki/ZFS

http://www.oracle.com/technetwork/artic ... 15034.html


But you can use geli like actually you do: http://forums.freebsd.org/showthread.php?t=12503

http://unix.stackexchange.com/questions ... uggestions


PD: I do not use encrytion, so I can't help you more.