From: David Woodhouse <dwmw2@infradead.org>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2: cannot execute /bin/bash: Permission denied
Date: Sat, 01 Dec 2001 18:01:32 +0000 [thread overview]
Message-ID: <29225.1007229692@redhat.com> (raw)
In-Reply-To: <1007229199.1713.4.camel@gromit>
Dec 1 12:43:51 gromit kernel: Argh. Special inode #1589 had more than
one node
Dec 1 12:48:43 gromit kernel: Eep. read_inode() failed for ino #1589
Dec 1 12:48:43 gromit last message repeated 96 times
Hmmm. Device nodes, symlinks etc should have only one valid physical node at
any time. It's strange that your filesystem has violated that. Can I have a
complete copy of the JFFS2 filesystem?
I should make jffs2_read_inode() recover better from this situation.
Currently, it's just failing to read that inode, and the GC then gets stuck
because it requires jffs2_read_inode() to succeed. I need to make the GC
deal with that situation too.
--
dwmw2
prev parent reply other threads:[~2001-12-01 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-01 16:27 JFFS2: cannot execute /bin/bash: Permission denied Michael Rothwell
2001-12-01 16:57 ` David Woodhouse
2001-12-01 17:53 ` Michael Rothwell
2001-12-01 18:01 ` David Woodhouse [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=29225.1007229692@redhat.com \
--to=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rothwell@holly-springs.nc.us \
/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