From: Carsten Otte <cotte@de.ibm.com>
To: Vasily Averin <vvs@sw.ru>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
devel@openvz.org, linux-ext4@vger.kernel.org,
Stephen Tweedie <sct@redhat.com>,
adilger@clusterfs.com
Subject: Re: [PATCH] [RESEND] ext[34] orphan list check on destroy_inode
Date: Tue, 05 Jun 2007 12:34:31 +0200 [thread overview]
Message-ID: <46653C37.7040303@de.ibm.com> (raw)
In-Reply-To: <466538C9.8080104@sw.ru>
Vasily Averin wrote:
> Customers claims to ext3-related errors, investigation showed that ext3 orphan
> list has been corrupted and have the reference to non-ext3 inode. The following
> debug helps to understand the reasons of this issue.
This looks like it might be related to the -as far as I recall-
unfixed issue we've noticed some time ago:
http://osdir.com/ml/file-systems/2004-02/msg00033.html
I have'nt heard any reports of a reproduction on modern kernels on
390 lately, our issue seems to have disappeared.
so long,
Carsten
prev parent reply other threads:[~2007-06-05 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 10:19 [PATCH] [RESEND] ext[34] orphan list check on destroy_inode Vasily Averin
2007-06-05 10:34 ` Carsten Otte [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=46653C37.7040303@de.ibm.com \
--to=cotte@de.ibm.com \
--cc=adilger@clusterfs.com \
--cc=akpm@linux-foundation.org \
--cc=carsteno@de.ibm.com \
--cc=devel@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
--cc=vvs@sw.ru \
/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