linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Theodore Ts'o <tytso@mit.edu>
To: George Spelvin <linux@horizon.com>
Cc: sandeen@redhat.com, dreusser@gmail.com, linux-ext4@vger.kernel.org
Subject: Re: Issue with bad file system
Date: Mon, 19 Nov 2012 14:36:46 -0500	[thread overview]
Message-ID: <20121119193646.GB30091@thunk.org> (raw)
In-Reply-To: <20121119191505.24680.qmail@science.horizon.com>

On Mon, Nov 19, 2012 at 02:15:05PM -0500, George Spelvin wrote:
> 
> Oh, more enthusiastic users are *already* trying out metadata_csum
> on production file systems.  And finding lots of bugs doing so!
> 
> My latest is a file system where e2fsck can find the problem, but
> can't fix it.

Is this a file system suffering from the aftermath of the off-line
resizing with the 64-bit file system feature?  Or is this some other
unrelated problem?

Thanks,

						- Ted



  reply	other threads:[~2012-11-19 19:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19  6:30 Issue with bad file system George Spelvin
2012-11-19  7:23 ` Drew Reusser
2012-11-19  8:32   ` George Spelvin
2012-11-19 15:29     ` Eric Sandeen
2012-11-19 17:00       ` Drew Reusser
2012-11-19 16:57     ` Drew Reusser
2012-11-19 17:14       ` Eric Sandeen
2012-11-19 18:41         ` Theodore Ts'o
2012-11-19 19:15           ` George Spelvin
2012-11-19 19:36             ` Theodore Ts'o [this message]
2012-11-19 19:53           ` Drew Reusser
2012-11-19 20:24             ` Theodore Ts'o
2012-11-19 19:54         ` Drew Reusser
2012-11-19 21:15           ` George Spelvin
2012-11-19 21:30             ` Eric Sandeen
  -- strict thread matches above, loose matches on Subject: below --
2012-11-19  4:46 Drew Reusser
2012-11-19 15:18 ` Eric Sandeen

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=20121119193646.GB30091@thunk.org \
    --to=tytso@mit.edu \
    --cc=dreusser@gmail.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux@horizon.com \
    --cc=sandeen@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).