[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <009201cdb1ff$c33d8c60$49b8a520$@lucidpixels.com>
Date: Wed, 24 Oct 2012 11:53:47 -0400
From: "Justin Piszcz" <jpiszcz@...idpixels.com>
To: <tytso@....edu>, "'Steven J. Magnani'" <steve@...idescorp.com>
Cc: <linux-kernel@...r.kernel.org>
Subject: RE: 3.6.0 kernel - ext4 corruption, or?
-----Original Message-----
From: tytso@....edu [mailto:tytso@....edu]
Sent: Wednesday, October 24, 2012 10:40 AM
To: Justin Piszcz; Steven J. Magnani
Cc: linux-kernel@...r.kernel.org
Subject: Re: 3.6.0 kernel - ext4 corruption, or?
On Wed, Oct 24, 2012 at 08:15:37AM -0400, Justin Piszcz wrote:
>
> I read there was a bug in 3.6.2, is there also one in 3.6.0, or can
someone
> help explain this?
The problem which we are currently trying to investigate was
reportedly introduced in v3.6.1. So far that's about how we know; we
have two users who have reported it, but I and other ext4 developers
haven't been able to reproduce it yet.
Got it.
> # grep 10.0.0.11 -r /etc
> /etc/posfix.old/master.cf:10.0.0.11:smtp inet n - -
> - 1 postscreen
>
> # ls -l /etc/posfix.old/master.cf
> -rw-r--r-- 1 root root 13236 Oct 28 2011 /etc/posfix.old/master.cf
>
> # ls -ld /etc/postfix.old
> ls: cannot access /etc/postfix.old: No such file or directory
>
Looks like you or some script renamed /etc/postfix to /etc/posfix.old
as part some upgrade?
Whoops-- sorry about that, typo, so for now (concerning the other bug) it's
best to stay with 3.6.0 until the bug is found, thank you.
Justin.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists