Jaunty 64bit mdadm, lvm, ext 4, samba huge memory use and crashing

Bug #366424 reported by Matthew Durkin
4
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

I am running Jaunty 64 bit (amd) on an atom 330 intel board with 2GB of memory and 8GB swap (2GB on 4 HDD). I have mdadm running a raid 5 array across 4 disks (3TB total capacity array), lvm on top of this, with ext4 as the file system. This is used for storage only - I'm booting off a different ext4 drive with no lvm on the boot partition.
I have samba set up to share a single directory on the raid5/lvm/ext4 setup. When I transfer a file from my windows machine to the samba share, memory use increases by the size of the file I am transferring. memory is not released until I delete the file (through samba or using rm on the command line). If I turn off swap, the box eventually uses all physical memory, crashes, and reboots.
valgrind shows no excessive samba memory use. I'm not sure where the memory is being used, and why it isn't being released. And no - I'm not transferring to tmpfs - this is definitely to the mounted raid 5 array as described.
I can't identify the particular package that is causing the problem, but I've described the setup as a whole and the symptoms.
This is a clean install of Ubuntu jaunty (30 minutes ago), using the alternate installer to create the custom disk setup. All I have done since install is to add samba, webmin, and openssh. This is the desktop version of ubuntu.

Tags: jaunty
Monkey (monkey-libre)
tags: added: jaunty
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Is this bug reproducible with the latest Lucid packages ?
Tanks in advance.

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

 Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage .

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Matthew Durkin (matthew-durkin) wrote : Re: [Bug 366424] Re: Jaunty 64bit mdadm, lvm, ext 4, samba huge memory use and crashing

This is an old bug now. I don't have the same motherboard as I got bored of
this problem, and another one with the nic drivers (different bug report).
On my latest setup everything runs without issue, so I can't help with this
report any more! Perhaps close it and hope someone else reports it if it's
still valid?
Thanks

On 16 August 2010 21:23, Fabio Marconi <email address hidden> wrote:

> We'd like to figure out what's causing this bug for you, but we haven't
> heard back from you in a while. Could you please provide the requested
> information? Thanks!
>
> --
> Jaunty 64bit mdadm, lvm, ext 4, samba huge memory use and crashing
> https://bugs.launchpad.net/bugs/366424
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

Hello Mettew Durkin

Thanks for the reply
As this bug is not reproducible by the reporter i close this report. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!
Fabio

Changed in ubuntu:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.