From: Andreas Dilger <adilger@clusterfs.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>, ext2-devel@lists.sourceforge.net
Subject: Re: problems with ext3 fs, kernels up to 2.6.6-rc2
Date: Wed, 19 May 2004 11:06:04 -0600 [thread overview]
Message-ID: <20040519170604.GS18086@schnapps.adilger.int> (raw)
In-Reply-To: <20040519104152.GM19183@stingr.net>
On May 19, 2004 14:41 +0400, Paul P Komkoff Jr wrote:
> For a long time I'm sorta have the following problem.
>
> I have ext3 partition with dir_index turned on. I have programs, which
> store many files on it (for example, Maildir mailboxes for 500+ users,
> about 200k files).
>
> Sometimes something going wrong. I am noticing it by rdiff-backup on
> this partition producing the following output:
> ListError goloub/Maildir/cur/1082623479.1763_0.ns:2,S [Errno 5]
> Input/output error:
> +'/mnt/mail/goloub/Maildir/cur/1082623479.1763_0.ns:2,S'
>
> Yes, when I am doing strace ls -al (failed file), I am seeing -EIO
>
> lstat64("/mnt/mail/goloub/Maildir/cur/1082623479.1763_0.ns:2,S",
> 0x806408c) = -1 EIO (Input/output error)
>
> I know, so when I will e2fsck it it will be repaired. But how I can
> help debug it?
>
> Which on-disk structs I need to examine, maybe extract, and send to
> someone?
A problem with htree was recently discovered during Lustre testing when
files were being renamed within the same directory. In some cases the
addition of the new name caused a directory block split and the old
dir_entry was pointing at the wrong entry, and the wrong entry was removed.
This would seem entirely possible in a Maildir directory, since the MTA
will be doing a lot of renames within the same directory.
This seems to fix the majority of the problems, although there are still
some rare failures in the rename test.
===== fs/ext3/namei.c 1.52 vs edited =====
--- 1.52/fs/ext3/namei.c Mon May 10 05:25:34 2004
+++ edited/fs/ext3/namei.c Wed May 19 10:59:39 2004
@@ -2265,7 +2265,9 @@
* ok, that's it
*/
retval = ext3_delete_entry(handle, old_dir, old_de, old_bh);
- if (retval == -ENOENT) {
+ if (le32_to_cpu(old_de->inode) != old_inode->i_ino ||
+ (retval = ext3_delete_entry(handle, old_dir, old_de, old_bh)) ==
+ -ENOENT) {
/*
* old_de could have moved out from under us.
*/
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2004-05-19 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 10:41 problems with ext3 fs, kernels up to 2.6.6-rc2 Paul P Komkoff Jr
2004-05-19 17:06 ` Andreas Dilger [this message]
2004-05-20 6:40 ` Paul P Komkoff Jr
2004-05-20 9:22 ` [Ext2-devel] " Andreas Dilger
2004-05-25 16:58 ` Andreas Dilger
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=20040519170604.GS18086@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox