From: Duncan Sands <baldrick@wanadoo.fr>
To: Dave Jones <davej@codemonkey.org.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Htree ate my hard drive, was: post-halloween 0.2
Date: Thu, 31 Oct 2002 07:27:52 +0100 [thread overview]
Message-ID: <200210310727.52636.baldrick@wanadoo.fr> (raw)
In-Reply-To: <20021030171149.GA15007@suse.de>
> EXT3 Htree support.
> ~~~~~~~~~~~~~~~~~~~
> The ext3 filesystem has gained indexed directory support, which offers
> considerable performance gains when used on filesystems with large
> directories. In order to use the htree feature, you need at least version
> 1.29 of e2fsprogs. Existing filesystems can be converted using the command
> "tune2fs -O dir_index /dev/hdXXX" The latest e2fsprogs can be found at
> http://prdownloads.sourceforge.net/e2fsprogs
I ran this (tune2fs -O dir_index /dev/hdXXX).
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. Very strange. On rebooting, fsck found a
gazillion bad inodes. They all turned out to be from the 2.5.44 tree -
poetic justice I suppose! But this did not suffice. Rebooting, I got
"optimizing directories" again. Next fsck showed up more dud inodes.
After a few cycles of this, I ran
tune2fs -O ^dir_index /dev/hdXXX
to remove htree support. No problems since then.
Duncan.
PS: UP, no preempt.
tune2fs 1.30-WIP (30-Sep-2002)
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: ee433ceb-6b14-45b1-894c-2a8aad1e280f
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal needs_recovery
Filesystem state: clean
Errors behavior: Unknown (continue)
Filesystem OS type: Linux
Inode count: 290816
Block count: 2315368
Reserved block count: 115768
Free blocks: 871842
Free inodes: 36718
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 4096
Inode blocks per group: 128
Last mount time: Thu Oct 31 06:37:46 2002
Last write time: Thu Oct 31 06:37:46 2002
Mount count: 7
Maximum mount count: 30
Last checked: Wed Oct 30 11:50:37 2002
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: <none>
Journal inode: 493
Journal device: 0x0000
First orphan inode: 139500
next prev parent reply other threads:[~2002-10-31 6:21 UTC|newest]
Thread overview: 35+ 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 ` Duncan Sands [this message]
2002-10-31 8:07 ` Htree ate my hard drive, was: " Andreas Dilger
2002-10-31 8:20 ` Duncan Sands
2002-11-04 22:42 ` [Ext2-devel] " Stephen C. Tweedie
2002-11-04 22:59 ` 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
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=200210310727.52636.baldrick@wanadoo.fr \
--to=baldrick@wanadoo.fr \
--cc=davej@codemonkey.org.uk \
--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