NAS4Free 9.1.0.1.690 Released (FreeBSD 9.1-RELEASE p3)

[kkd]

u cant edit non ut8 files. that's a limitation.

[kko]

u cant edit non ut8 files. that's a limitation.

ok. it is true.

Why i can't edit loader.conf?
How i can edit it?

[kko]

u cant edit non ut8 files. that's a limitation.

ok. it is true.

Why i can't edit loader.conf?
How i can edit it?

Update: there is no file loader.conf in /cf/boot/
i found it in /boot/ and i successfully edited it

[dnar]

You must be running the full install then. /cf only exists in embedded.

[kkd]

You must be running the full install then. /cf only exists in embedded.

i think ur wrong, if i remember well there is on em. sys.

[MattTrent]

Rev 621 is now released!

- Fix AIO SMB2 broken file transfers.

Regards,
zoon01

Hi there. Would you mind pointing me towards what the AIO/SMB2 fix was? There's a Samba bug open for this issue (https://bugzilla.samba.org/show_bug.cgi?id=8726), and I was hoping to update/close the bug as appropriate. Not sure if something was committed upstream in Samba, the FreeBSD port, or if this is a NAS4Free specific fix.

Thanks!!

[zoon01]

Rev 621 is now released!

- Fix AIO SMB2 broken file transfers.

Regards,
zoon01

Hi there. Would you mind pointing me towards what the AIO/SMB2 fix was? There's a Samba bug open for this issue (https://bugzilla.samba.org/show_bug.cgi?id=8726), and I was hoping to update/close the bug as appropriate. Not sure if something was committed upstream in Samba, the FreeBSD port, or if this is a NAS4Free specific fix.

Thanks!!

You can close that bug report if it is on me. Samba 3.6.12 release did the trick, an upstream file change in samba was responsible for this.
From the beginning of this bug, I have reported you that all time long something in samba did get broken and was responsible for this particular bug.
I'm glad it is fixed, its hard to tell you exactly what commit change in the source of samba made it right.
After the releases of NAS4Free containing any version higher than 3.6.12 has not given any bug report about a broken smb2/aio configuration.

Regards,
zoon01

[MattTrent]

You can close that bug report if it is on me. Samba 3.6.12 release did the trick, an upstream file change in samba was responsible for this.
From the beginning of this bug, I have reported you that all time long something in samba did get broken and was responsible for this particular bug.
I'm glad it is fixed, its hard to tell you exactly what commit change in the source of samba made it right.
After the releases of NAS4Free containing any version higher than 3.6.12 has not given any bug report about a broken smb2/aio configuration.

Regards,
zoon01

Thanks for the quick reply. I added those thoughts to the Samba bug. I haven't been able to crash Samba 3.6.13 with SMB2+AIO yet, unless I enable the sendfile option, and that seems like a separate issue since it used to crash with or without sendfile when SMB2+AIO were enabled on pre-3.6.12 versions..

[kkd]

You can close that bug report if it is on me. Samba 3.6.12 release did the trick, an upstream file change in samba was responsible for this.
From the beginning of this bug, I have reported you that all time long something in samba did get broken and was responsible for this particular bug.
I'm glad it is fixed, its hard to tell you exactly what commit change in the source of samba made it right.
After the releases of NAS4Free containing any version higher than 3.6.12 has not given any bug report about a broken smb2/aio configuration.

Regards,
zoon01

Thanks for the quick reply. I added those thoughts to the Samba bug. I haven't been able to crash Samba 3.6.13 with SMB2+AIO yet, unless I enable the sendfile option, and that seems like a separate issue since it used to crash with or without sendfile when SMB2+AIO were enabled on pre-3.6.12 versions..

according to my best knowledge sendfile option is not working at all. am i right mr zoon?

[030-NL]

What are your plans to include Netatalk 3.0.4 in the coming releases?

[sfranzis]

What are your plans to include Netatalk 3.0.4 in the coming releases?

I would also be glad seeing netatalk 3.0.x in one of the coming versions.
But as far as I know it may be difficult because the format of the config files have changed.

Stefan