All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Duncan Sands <baldrick@wanadoo.fr>,
	Dave Jones <davej@codemonkey.org.uk>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	ext2-devel@lists.sourceforge.net
Subject: Re: [Ext2-devel] Re: Htree ate my hard drive, was: post-halloween 0.2
Date: Mon, 4 Nov 2002 22:42:13 +0000	[thread overview]
Message-ID: <20021104224213.F14318@redhat.com> (raw)
In-Reply-To: <20021031080717.GF28982@clusterfs.com>; from adilger@clusterfs.com on Thu, Oct 31, 2002 at 01:07:17AM -0700

Hi,

On Thu, Oct 31, 2002 at 01:07:17AM -0700, Andreas Dilger wrote:
> On Oct 31, 2002  07:27 +0100, Duncan Sands wrote:

> > After a bit of switching back and forth between 2.4.19 and 2.5.44,
> > fsck was run while booting 2.4.19 (the usual check because of >30
> > mounts).  There was a message about optimizing directories.  Booting
> > continued but (big surprise) X refused to run.  It turned out that some
> > device files had vanished.

> > tune2fs -O ^dir_index /dev/hdXXX
> > to remove htree support.  No problems since then.

> I wonder if there is still a bug in the e2fsck code for re-hashing
> directories?

Possibly, but I'm more worried about why the fsck did a directory
optimise on reboot, especially on the root filesystem (where /dev is
usually stored).  Doing major fs surgery on a mounted, readonly
filesystem is sort-of safe, but only if you reboot afterwards.
Continuing and remounting read-write can cause all sorts of damage as
the cached fs data no longer matches what's on disk.

Duncan, did you have fsck set up to do a forced htree rebuild on
reboot?

Cheers,
 Stephen

  parent reply	other threads:[~2002-11-04 22:35 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-30 17:11 post-halloween 0.2 Dave Jones
2002-10-30 18:47 ` Ian Soboroff
2002-10-30 18:52   ` Greg KH
2002-10-30 19:02     ` Ian Soboroff
2002-10-30 19:08       ` Greg KH
2002-10-30 19:13       ` Patrick Mochel
2002-10-30 19:16         ` Ian Soboroff
2002-10-30 19:23           ` Patrick Mochel
2002-10-30 19:17         ` Ian Soboroff
2002-10-30 19:33 ` Alan Cox
2002-10-30 19:17   ` Martin J. Bligh
2002-10-30 19:50     ` Tom Rini
2002-10-30 19:57       ` Martin J. Bligh
2002-10-30 20:23         ` Tom Rini
2002-10-30 20:50         ` Arador
2002-10-30 21:03           ` Martin J. Bligh
2002-10-31  0:12         ` Alan Cox
2002-10-31  0:47   ` Dave Jones
2002-10-31 11:48     ` Alan Cox
2002-11-01  1:29       ` Bill Davidsen
2002-10-30 23:09 ` Pavel Machek
2002-10-31  0:35 ` Skip Ford
2002-10-31  6:27 ` Htree ate my hard drive, was: " Duncan Sands
2002-10-31  8:07   ` Andreas Dilger
2002-10-31  8:20     ` Duncan Sands
2002-11-04 22:42     ` Stephen C. Tweedie [this message]
2002-11-04 22:59       ` [Ext2-devel] " Duncan Sands
2002-11-04 23:22       ` Udo A. Steinberg
2002-10-31 23:05   ` Mike Civil
2002-11-03 20:42     ` Duncan Sands
2002-11-03 22:00       ` Mike Civil
2002-11-03 22:11   ` Martin Waitz
2002-11-07 15:36 ` Jan Kara
2002-11-07 15:44   ` Dave Jones
  -- strict thread matches above, loose matches on Subject: below --
2002-10-31 11:19 Htree ate my hard drive, was: " Petr Vandrovec
2002-10-31 21:42 ` [Ext2-devel] " chrisl
2002-10-31 22:03 ` 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=20021104224213.F14318@redhat.com \
    --to=sct@redhat.com \
    --cc=baldrick@wanadoo.fr \
    --cc=davej@codemonkey.org.uk \
    --cc=ext2-devel@lists.sourceforge.net \
    --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 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.