From: Michael Rothwell <rothwell@holly-springs.nc.us>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "'linux-mtd@lists.infradead.org'" <linux-mtd@lists.infradead.org>
Subject: Re: JFFS2: cannot execute /bin/bash: Permission denied
Date: 01 Dec 2001 12:53:19 -0500 [thread overview]
Message-ID: <1007229199.1713.4.camel@gromit> (raw)
In-Reply-To: <27599.1007225846@redhat.com>
On Sat, 2001-12-01 at 11:57, David Woodhouse wrote:
> chmod +x /mnt/flash/lib/*.so*
Not the problem. I did look in lib/ though, and all the symlinks were
wrong. In the "source" tree, the one that I used mkfs.jffs2 on, the
symlinks were correct (produced by chrooted ldconfig).
I'm using 2.4.13.
I tried copying data to the fs, and now I'm getting a disk-pounding
amount of this:
Dec 1 12:43:51 gromit kernel: Argh. Special inode #1589 had more than
one node
Dec 1 12:46:32 gromit kernel: Argh. Special inode #1431 had more than
one node
Dec 1 12:46:33 gromit kernel: Argh. Special inode #1435 had more than
one node
Dec 1 12:46:33 gromit kernel: Argh. Special inode #1437 had more than
one node
Dec 1 12:46:33 gromit kernel: Argh. Special inode #1438 had more than
one node
Dec 1 12:46:33 gromit kernel: Argh. Special inode #1439 had more than
one node
Dec 1 12:46:34 gromit kernel: Argh. Special inode #1443 had more than
one node
Dec 1 12:46:35 gromit kernel: Argh. Special inode #1452 had more than
one node
Dec 1 12:47:01 gromit kernel: Eep. read_inode() failed for ino #1589
[...]
Dec 1 12:48:43 gromit last message repeated 96 times
Dec 1 12:48:43 gromit kernel: Eep. read_inod589
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
Dec 1 12:48:43 gromit kernel: Eep. read_inod589
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
Dec 1 12:48:43 gromit kernel: Eep. read_inod589
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
Dec 1 12:48:43 gromit kernel: Eep. read_inod589
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
Dec 1 12:48:43 gromit kernel: Eep. read_inod589
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
Dec 1 12:48:43 gromit kernel: Eep. read_inod589
next prev parent reply other threads:[~2001-12-01 17:41 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 [this message]
2001-12-01 18:01 ` David Woodhouse
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=1007229199.1713.4.camel@gromit \
--to=rothwell@holly-springs.nc.us \
--cc=dwmw2@infradead.org \
--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