public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Dewet Diener <linux-kernel@dewet.org>
Cc: Andrew Morton <akpm@zip.com.au>,
	linux-kernel@vger.kernel.org,
	"ext3-users@redhat.com" <ext3-users@redhat.com>
Subject: Re: ext3 partition unmountable
Date: Sun, 19 Aug 2001 12:00:13 -0400	[thread overview]
Message-ID: <20010819120013.B3504@thunk.org> (raw)
In-Reply-To: <20010818030321.A11649@darkwing.flatlit.net> <3B7EEC4C.D0127AB4@zip.com.au> <20010819160605.A9890@darkwing.flatlit.net>
In-Reply-To: <20010819160605.A9890@darkwing.flatlit.net>; from linux-kernel@dewet.org on Sun, Aug 19, 2001 at 04:06:05PM +0200

Andrew, for future reference, a much simpler way of debugging this
sort of problem (which doesn't require interpreting od -x dumps) is to
ask the user to use the command:

dumpe2fs -f -h /dev/hdd1

To clear the feature flag, you can use the debugfs program:

% debugfs
debugfs:  open -w -f /tmp/testfs
debugfs:  features   
Filesystem features: filetype FEATURE_I16 sparse_super
debugfs:  feature ^feature_i16
debugfs:  features
Filesystem features: filetype sparse_super
debugfs:  quit

> I managed to fix it by running e2fsck off one of the backup 
> superblocks - that seems to have repaired the broken bits:

> Then I just reran "tune2fs -j", and mounted it as ext3.  I hope that
> was the correct approach, but its working in any case :)  Don't quite
> know why/how the superblock got corrupted like that in the first
> place :-/

Well, sounds like the in-core copy of the superblock got corrupted
somehow, or perhaps a passing bit of cosmic radiation flipped the bit
as it was getting written back to disk.  If you can get it to do it
repeatably it, or if it even happens once or twice more, we'd
definitely want to know more about it.

							- Ted


      reply	other threads:[~2001-08-19 16:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-18  1:03 ext3 partition unmountable Dewet Diener
2001-08-18 11:07 ` Mike Black
2001-08-18 21:52   ` Dewet Diener
2001-08-18 22:04     ` Riley Williams
2001-08-18 23:40       ` Dewet Diener
2001-08-20 18:10       ` Stephen C. Tweedie
2001-08-20 21:37         ` Dewet Diener
2001-08-18 22:29 ` Andrew Morton
2001-08-18 23:35   ` Dewet Diener
2001-08-19 14:06   ` Dewet Diener
2001-08-19 16:00     ` Theodore Tso [this message]

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=20010819120013.B3504@thunk.org \
    --to=tytso@mit.edu \
    --cc=akpm@zip.com.au \
    --cc=ext3-users@redhat.com \
    --cc=linux-kernel@dewet.org \
    --cc=linux-kernel@vger.kernel.org \
    /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