Your message dated Fri, 10 Oct 2014 20:08:09 -0400
with message-id <[email protected]>
and subject line FWD: Bug#764542: debconf: potential filesystem corruption
has caused the Debian Bug report #764542,
regarding debconf: potential filesystem corruption
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
764542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764542
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debconf
Version: 1.5.49
Severity: important
when there's low ram available and dpkg-reconfigure is issued (eg,
dpkg-reconfigure locales), if there are premature "exits" when building
locales it could lead to a filesystem corruption.
This happened to me more than once where I was using a 128MB ram for
kvm, and there was less than 64 megs of ram available for
dpkg-reconfigure..
I wouldn't expect filesystem corruption but there was something of it as
I was forced to use fsck on boot-up.
There is a filesystem issue, I didn't want to believe it until it
happened twice with two separate kvm VMs. The disks are "virtual"
isolating the diagnosis it could be a potential hardware problem. It
could also be replicated more than once.
Steps
->dpkg-reconfigure locales would run but would have crash-exits when
when trying to generate locales.
->type "reboot". On the next boot-up there would be complaint of
filesystem integrity and fsck would run.
^ These two steps was tried on two different kvms but with the same
Debian, and same amount of ram reservation.
(Note: the "free" ram available is less than 64 MB, locales tried were
en_CA.UTF-8 and en_US.UTF-8)
If more logging data is needed, I can try to see if I can do that.
thanks
--- End Message ---
--- Begin Message ---
----- Forwarded message from westlake <[email protected]> -----
Date: Fri, 10 Oct 2014 18:28:11 -0400
From: westlake <[email protected]>
To: Joey Hess <[email protected]>, [email protected]
Subject: Bug#764542: debconf: potential filesystem corruption
Reply-To: westlake <[email protected]>, [email protected]
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101
Icedove/31.0
ok i'm not seeing this anymore in one of the latest jessie builds. whether if
I recall the details or not, I just tried to replicate this. I get "killed"
out of ram issues and no filesystem corruption. Please close this report
thanks.
----- End forwarded message -----
--
see shy jo
signature.asc
Description: Digital signature
--- End Message ---
