TC 4.2 + Samba - RAM usage & CPU stall

[dormof]

remus is right, I was configuring a trivial SAMBA based sharing, and almost broke my head revising the SAMBA documentation for this constant halting with TC 4.2.1 and SAMBA 3.6.1. I even resorted to put a hole 1 GB of RAM to the server machine, but it still went unresponsive after a few seconds!

On the other hand, and even downgrading to just 128 MB of RAM, TC 3.8.4 + SAMBA 3.4.5 allowed me to  transfer a 16 GB file from a Windows machine, without a hassle. Hope this gets a workaround for an upcoming 4.x release, either it's caused by SAMBA or the TC kernel. Anyways, thanks for the effort to everyone involved.

[martin]

I thought I would just pitch in and confirm that I am successfully running the latest samba3 in the repository on Core 4.2 and having no problems, regardless of file size. Reading from a mounted XFS partition.

[curaga]

I too had tried to test both Samba problems at once (this and the cifs mount one), by setting up two TC 4.2 VMs, one serving via samba3 and one reading with only filesystems- loaded.

I couldn't see either issue, both the server and client ran fine for me.

--

We have confirmation that the cifs client issue is fixed in 3.0.9, so perhaps the server issue too will be resolved in TC 4.4.

[dormof]

I thought I would just pitch in and confirm that I am successfully running the latest samba3 in the repository on Core 4.2 and having no problems, regardless of file size. Reading from a mounted XFS partition.

I too had tried to test both Samba problems at once (this and the cifs mount one), by setting up two TC 4.2 VMs, one serving via samba3 and one reading with only filesystems- loaded.

I couldn't see either issue, both the server and client ran fine for me.

--

We have confirmation that the cifs client issue is fixed in 3.0.9, so perhaps the server issue too will be resolved in TC 4.4.

Totally true. Just finished testing a >10 GB transfer with TC 4.2.1 + SAMBA 3.6.1 (updated on Jan 20), over several filesystems (xfs, ext3, ext4, reiserfs, ntfs) and it all worked like a charm.

I'd have to note that I had the samba3.tcz extension already downloaded by Jan 18, along with its dependencies -except samba3-libs- to have it ready for installation. Simply my bad, for what I was considering to stick with TC 3.8.4 meanwhile...

Oh, and my testing was succesful with only 96 MB of RAM.

[Kenavru]

TC 4.2.1 + SAMBA 3.6.1 = still the same bug
only 3.x.x works fine for me

[dormof]

TC 4.2.1 + SAMBA 3.6.1 = still the same bug
only 3.x.x works fine for me

I think it has something to do with the external 1 TB drive, for which TC 3 might have the most appropiate code to manage the USB interfacing, or something like that. I guess it might have an explanation from the experts in this regard, which I'm not one of.

Anyway, it's good to know there's at least a reliable option that lets you accomplish your NAS needs with the thin client. Hopefully the upcoming TC 4.x updates will fix the bug.

[dacoon]

Hi,

any news to this problem? I have the same issue, i think it have nothing to do with samba3. If I copy a big file form the external drive from on directory to another, also the ram get eaten and TC hang/freeze because it's running out of ram.

I think, it have to do only with mount on TC 4.2. I have this problem nearly 6 Month ago but get it fixed, but now after a backup crash (don't know how this could happen  ) i had forgotten how. I think, because TC is loading with all directories into the RAM (usr/etc/mnt/bin ..), all mounting points also get redirected to this.

If i copy the file like "cp /mnt/sdb1/bigfile /mnt/sdb1/bigfile_new" and view with an other terminal "free -m" and "df | grep -v "loop"", written into a endless loop with "sleep 1". I see only how the ram is dropping but nothing on sdb1.

[remus]

The solution I found was to use

Microcore 3.8.4 + Samba 3.4.5 = Stable