From: Marc-Christian Petersen <m.c.p@gmx.net>
To: "Theodore Ts'o" <tytso@mit.edu>,
"Christopher Li" <chrisl@gnuchina.org>,
"Ryan Cumming" <ryan@completely.kicks-ass.org>
Cc: linux-kernel@vger.kernel.org, ext3-users@redhat.com
Subject: Re: ARGS [PATCH] fix htree dir corrupt after fsck -fD
Date: Sun, 29 Sep 2002 19:19:14 +0200 [thread overview]
Message-ID: <200209291918.55303.m.c.p@gmx.net> (raw)
Hi Ryan,
> I am running your program now over an hour without any corruption on the
> loopback mounted ext3 filesystem.
shit, I thought testing over an hour (10mins your program, umount, fsck -fD
test.img in a loop) is enough but it isn't. Damn f*ck :(
root@codeman:[/] # fsck -fD test.img
fsck 1.29 (24-Sep-2002)
e2fsck 1.29 (24-Sep-2002)
Truncating orphaned inode 6871 (uid=0, gid=0, mode=0103244, size=0)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Problem in HTREE directory inode 2 (/): bad block number 3291184.
Clear HTree index<y>? yes
Pass 3: Checking directory connectivity
/lost+found not found. Create<y>? yes
Pass 3A: Optimizing directories
Optimizing directories: 2
Pass 4: Checking reference counts
Pass 5: Checking group summary information
this occured just after I sent my first mail :((
--
Kind regards
Marc-Christian Petersen
http://sourceforge.net/projects/wolk
PGP/GnuPG Key: 1024D/569DE2E3DB441A16
Fingerprint: 3469 0CF8 CA7E 0042 7824 080A 569D E2E3 DB44 1A16
Key available at www.keyserver.net. Encrypted e-mail preferred.
next reply other threads:[~2002-09-29 17:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 17:19 Marc-Christian Petersen [this message]
2002-09-29 21:54 ` Ryan Cumming
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=200209291918.55303.m.c.p@gmx.net \
--to=m.c.p@gmx.net \
--cc=chrisl@gnuchina.org \
--cc=ext3-users@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ryan@completely.kicks-ass.org \
--cc=tytso@mit.edu \
/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
Powered by JetHome