From: Dmitry Bazhenov <atrey@emcraft.com>
To: linux-mtd@lists.infradead.org
Subject: Re: JFFS2: scan leaves dirent for inode which has no valid data nodes
Date: Thu, 27 Apr 2006 18:19:25 +0400 [thread overview]
Message-ID: <200604271819.25608.atrey@emcraft.com> (raw)
In-Reply-To: <1146146360.11909.456.camel@pmac.infradead.org>
On Thursday 27 April 2006 17:59, David Woodhouse wrote:
> You should still be able to unlink it.
I was not and I am still not able to do any operation upon the file. The
jffs2_read_inode() function marked the inode as bad and all I/O operations
return EIO, even unlink() does.
For the moment, I have to find and eliminate the reason(s) that could lead to
appearance of the situation. I think, there is some kind of a race here. My
experience with the filesystem is much to be desired and I would appreciate
any points to the possible places of error.
Thanks,
Dmitry
prev parent reply other threads:[~2006-04-27 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 7:40 JFFS2: scan leaves dirent for inode which has no valid data nodes Dmitry Bazhenov
2006-04-27 13:59 ` David Woodhouse
2006-04-27 14:19 ` Dmitry Bazhenov [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=200604271819.25608.atrey@emcraft.com \
--to=atrey@emcraft.com \
--cc=linux-mtd@lists.infradead.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