Your message dated Fri, 20 Apr 2007 20:05:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#410975: evms-2.5.2-1.sarge2: expand a RAID5 device using
evmsn (ncurses gui) it eats up all the memory.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: evms-2.5.2-1.sarge2
Version: 2.5.2-1
Severity: important
When expanding a RAID5 device using evmsn (ncurses gui) it eats up all the
memory and the process
gets killed by the kernel, leaving the RAID5 array corrupt.
Has been tested on this server and in vmware to make sure it's wasn't hardware
related, i fixed this
by doing the following:
- remove all sarge evms related packages and delete config files
- add sources for debian etch (testing in /etc/apt/sources.list)
- apt-get install libncurses5-dev libglib1.2-dev uuid-dev libglib2.0-dev
- apt-get source evms
- cd evms-2.5.5
- ./configure --with-static-glib --disable-gui --disable-ntfs
- make all
- make install
- ldconfig
So using the patched version from Etch resolved this issue, now running self
compiled evms-2.5.5-18
and hoping it would remain stable.
And good luck with the Etch release, looking forward to it
-- System Information:
Debian Release: 3.1
Architecture: i386 (i686)
Kernel: Linux 2.6.8-3-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
--- End Message ---
--- Begin Message ---
On Wed, Feb 14, 2007 at 11:32:30PM +0100, mastrboy wrote:
> Package: evms-2.5.2-1.sarge2
> Version: 2.5.2-1
> Severity: important
>
> When expanding a RAID5 device using evmsn (ncurses gui) it eats up all the
> memory and the process
> gets killed by the kernel, leaving the RAID5 array corrupt.
As sarge is now oldstable and you say it's fixed in etch, I'm closing this --
there's no way there's going to be a sarge update for this. :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
--- End Message ---
