public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Dmitry Bazhenov <atrey@emcraft.com>
To: linux-mtd@lists.infradead.org
Subject: JFFS2: scan leaves dirent for inode which has no valid data nodes
Date: Thu, 27 Apr 2006 11:40:37 +0400	[thread overview]
Message-ID: <200604271140.37488.atrey@emcraft.com> (raw)

Hi,

I am running Linux 2.4.26 for MIPS-4k custom board and has the problem wich 
appears from time to time on one of the JFFS2 partitions.

The partition is mounted to /etc mount point. The following screenshot shows 
the problem (I have changed the real file name for confidentiality).

# touch /etc/any.file
touch: /etc/any.file: Input/output error
# echo ddd > /etc/any.file
/etc/any.file: cannot create (Input/output error)

It is worth to note, that 'ls' utility doesn't show this file in the list.

I have made a dump of the partition and examined it. I have found that there 
is a valid dirent for the file and there is no valid data nodes (all are 
obsolete).

The curcumstances that proceeded the appearance of the situation are unknown. 
It is also unknown was it a powerfail or it was a normal functioning.

My questions are:

1. Should the scan process during mounting mark as obsolete dirent nodes which 
has no valid data nodes?
2. Is this a bug when such dirent exists and there is no chanse to 
create/read/write a file with the same name?

I have browsed the mailing list archive and haven't found (or just missed) the 
problem in it. Maybe the problem were resolved in more recent 2.4.x kernels.

Any information would be appreciated.

Thanks,
Dmitry

             reply	other threads:[~2006-04-27  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-27  7:40 Dmitry Bazhenov [this message]
2006-04-27 13:59 ` JFFS2: scan leaves dirent for inode which has no valid data nodes David Woodhouse
2006-04-27 14:19   ` Dmitry Bazhenov

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=200604271140.37488.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