[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#392818: marked as done (ext3 corruption issue in 2.6.18 found by RedHat)

Your message dated Thu, 2 Nov 2006 19:09:42 +0100
with message-id <20061102180942.GA11073@nancy>
and subject line Bug#392818: ext3 corruption issue in 2.6.18 found by RedHat
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: linux-2.6
Version: 2.6.18-1
Severity: critical
Justification: possible filesystem corruption

Hi release and kernel teams,

Following up to
http://lists.debian.org/debian-release/2006/10/msg00183.html :

Steve Langasek wrote:
> On Thu, Oct 12, 2006 at 10:11:06AM -0700, Kevin B. McCarty wrote:

>> Is this ext3 corruption issue also on the kernel team's radar?
> 
>> http://lwn.net/Articles/203536/
>> http://kernelslacker.livejournal.com/55309.html
> 
>> Apologies if it's a known and/or fixed issue.
>> best regards,
> 
> That would seem to warrant an RC bug?
> 
> Please, if you know of such issues that should prevent pushing the current
> 2.6.18 packages into testing, file them as bugs of the appropriate severity.

Unfortunately I know nothing about this issue beyond what's written in
the above URLs -- I don't even have any machines running on a 2.6.18
kernel.  This probably makes me not the best person to file a bug.  But
here goes anyway...

The last URL above includes a link to the issue in RedHat's bugzilla:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=209005
Apparently they are still trying to create a good test case for it.

Note that Fedora felt strongly enough about the problem that they are
delaying the release of FC6 in order to fix it:
http://fedoranews.org/cms/node/1668

-- 
Kevin B. McCarty <kmccarty@princeton.edu>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/    Princeton University
GPG: public key ID 4F83C751                 Princeton, NJ 08544

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message --- 
Version: 2.6.18-1

On Fri, 13 Oct 2006, maximilian attems wrote:

> On Fri, Oct 13, 2006 at 10:54:02AM -0700, Kevin B. McCarty wrote:
>  
> > Hi release and kernel teams,
> > 
> > Following up to
> > http://lists.debian.org/debian-release/2006/10/msg00183.html :
> > 
> > Steve Langasek wrote:
> > > On Thu, Oct 12, 2006 at 10:11:06AM -0700, Kevin B. McCarty wrote:
> > 
> > >> Is this ext3 corruption issue also on the kernel team's radar?
> > > 
> > >> http://lwn.net/Articles/203536/
> > >> http://kernelslacker.livejournal.com/55309.html
> > > 
> > >> Apologies if it's a known and/or fixed issue.
> > >> best regards,
> > > 
> > > That would seem to warrant an RC bug?

fixed with current linux-images in unstable, which all carry the jbd
upstream stable 2.6.18.1 patch

thus closing, thanks for your support.

-- 
maks

--- End Message ---
Reply to: