All of lore.kernel.org
 help / color / mirror / Atom feed
From: tytso@mit.edu
To: Justin Piszcz <jpiszcz@lucidpixels.com>,
	"Steven J. Magnani" <steve@digidescorp.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3.6.0 kernel - ext4 corruption, or?
Date: Wed, 24 Oct 2012 14:40:25 +0000	[thread overview]
Message-ID: <20121024144025.GA30955@thunk.org> (raw)
In-Reply-To: <1351085817.2362.2.camel@iscandar> <002101cdb1e1$47972c60$d6c58520$@lucidpixels.com>

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.

> # 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?

      	       	       	      	      		   - Ted


  parent reply	other threads:[~2012-10-24 14:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 12:15 3.6.0 kernel - ext4 corruption, or? Justin Piszcz
2012-10-24 13:36 ` Steven J. Magnani
2012-10-24 14:40 ` tytso [this message]
2012-10-24 15:53   ` Justin Piszcz
2012-10-24 18:39     ` Theodore Ts'o

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20121024144025.GA30955@thunk.org \
    --to=tytso@mit.edu \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=steve@digidescorp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.