Your message dated Thu, 3 Jul 2008 16:15:59 +0200
with message-id <20080703141559.GI13910@stro.at>
and subject line Re: Reiserfs: kernel panic with corrupted home filesystem
has caused the Debian Bug report #467405,
regarding Reiserfs: kernel panic with corrupted home filesystem
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 owner@bugs.debian.org
immediately.)


--
467405: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467405
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

On 7/3/08, Debian Bug Tracking System <owner@bugs.debian.org> wrote:
> ---------- Forwarded message ----------
> From: maximilian attems <max@stro.at>
> To: 467405-done@bugs.debian.org
> Date: Thu, 3 Jul 2008 16:15:59 +0200
> Subject: Re: Reiserfs: kernel panic with corrupted home filesystem
> Version: 2.6.24-1
>
> the suse reiserfs patches got all merged for .20.
> still a strange fs choice, but..

Hi Maks. I've seen in several bug reports that you advice against
'reiserfs' and this got my attention since we're using it on almost
all the hosts running Debian.

I've searched for any technical reasons why not using 'reiserfs'
didn't found an example of concrete fs corruption.
Can you send us a short message why you don't recommend it?

Thanks



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org