[debian-mysql] Bug#617796: Bug#617796: mysql-server-5.1: Upgrade of debian stable silently ERASED my years old mysql database (no backup)

[Carlo Wood]

On Fri, 11 Mar 2011 16:55:51 +0100
Norbert Tretkowski <norbert at tretkowski.de> wrote:

Well... I guess I did that -- at the moment not
thinking / remembering what I needed a sql database
for... But I feel still pissed that it didn't warn
me a little bit more clear before actually deleting
database files :/... I mean... It should be possible
to ask for confirmation in a way that I would have
hesitated right? Like when you try to format a
harddisk: *** ALL DATA WILL BE LOST *** kind of thing?

Nevertheless, you say you just purged a package
and the database is still there? It definitely isn't
here :/ So, when did it get deleted? And by what?

If reinstalling the package simply overwrote the old
database then that is bug: it should never do that.

Also, I looked with ext3grep if I could see anything
(although I wasn't, and still am, not even sure what
file to look for) and I could find any trace of anything
deleted in /var/lib/mysql.

> Am Freitag, den 11.03.2011, 16:22 +0100 schrieb Carlo Wood:
> > Hi, the upgrade was done on Feb 2, 2011. The logs
> > of that are attached as dpkg.log.2.gz
> 
> If you mean Feb 7, then mysql-server-5.0 was purged at that day:
> 
> 2011-02-07 21:03:29 purge mysql-server-5.0 5.0.51a-24+lenny4
> 5.0.51a-24+lenny4
> 
> According to your debconf settings, you will see a question asking you
> if you want to purge the databases as well, but it only removes the
> database files if you explicitly tell debconf to do so, the default is
> to keep the database files.
> 
> I just purged the mysql-server* packages from one of my systems, but
> after that it still has the /var/lib/mysql/ directory containing the
> databases.
> 
> 
> Regards
> 
> Norbert
> 



-- 
Carlo Wood <carlo at alinoe.com>