From: Frank R Callaghan <f.callaghan@ieee.org>
To: linux-mtd@lists.infradead.org
Subject: Re: Please Help, problem mounting jffs2
Date: Fri, 13 Jun 2003 12:58:58 -0400 [thread overview]
Message-ID: <200306131258.58729.f.callaghan@ieee.org> (raw)
In-Reply-To: <1055521884.3632.158.camel@passion.cambridge.redhat.com>
On Friday 13 June 2003 12:31 pm, David Woodhouse wrote:
> On Fri, 2003-06-13 at 16:53, Frank R Callaghan wrote:
> > Thanks Sid, but I don't think I'm getting that far :(
> >
> > # mount -t jffs2 /dev/mtdblock0 /var/fixed_flash &
> > # mtdblock_open
> > ok
> >
> > # ps ax
> >
> > 6 root 0 D [kupdated]
> >
> > 87 ttyS1 root 468 D mount -t jffs2 /dev/mtdblock0
> > /var/fixed_fl
> > 88 ttyS1 root 468 R mount -t jffs2 /dev/mtdblock0
> > /var/fixed_fl
>
> Why are there two mounts running simultaneously? What if you compile
> with CONFIG_JFFS2_FS_DEBUG=1 and set the console loglevel to 9 before
> mounting? Is it actually _doing_ anything or is it just deadlocked?
>
> If it's just deadlocked (and you're not using 2.4.18) then what was the
> last thing it said _before_ stopping?
jffs2_dump_block_lists:
flash_size: 00100000
used_size: 00000000
dirty_size: 00000000
wasted_size: 00000000
unchecked_size: 00000000
free_size: 00100000
erasing_size: 00000000
bad_size: 00000000
sector_size: 00010000
jffs2_reserved_blocks size: 00050000
nextblock: NULL
gcblock: NULL
clean_list: empty
very_dirty_list: empty
dirty_list: empty
erasable_list: empty
erasing_list: empty
erase_pending_list: 000f0000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 000e0000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 000d0000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 000c0000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 000b0000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 000a0000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00090000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00080000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00070000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00060000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00050000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00040000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00030000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00020000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00010000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erase_pending_list: 00000000 (used 00000000, dirty 00000000, wasted 00000000,
un
checked 00000000, free 00010000)
erasable_pending_wbuf_list: empty
free_list: empty
bad_list: empty
bad_used_list: empty
Not rotating empty clean_list
Not rotating empty very_dirty_list
Not rotating empty dirty_list
Not rotating empty erasable_list
Rotating erase_pending_list by 0
Erase block at front of erase_pending_list is at 000e0000
Not rotating empty free_list
jffs2_do_fill_super(): Getting root inode
jffs2_read_inode(): inode->i_ino == 1
jffs2_do_read_inode(): getting inocache
jffs2_get_ino_cache(): ino 1
jffs2_get_ino_cache found 00000000 for ino 1
jffs2_do_read_inode(): Got inocache at 00000000
jffs2_do_read_inode(): Creating inocache for root inode
jffs2_add_ino_cache: Add c058d260 (ino #1)
jffs2_do_read_inode_internal(): ino #1 nlink is 1
jffs2_get_inode_nodes(): ino #1
jffs2_read_inode() returning
jffs2_do_fill_super(): d_alloc_root()
JFFS2: Garbage collect thread is pid 95
kernel 2.4.19 + RTAI + mtd<CVS> yesterday
Oops that was DEBUG=3 oh well the more info the better ;)
dmesg -n will only let me set level=8 max !
TIA,
Frank.
next prev parent reply other threads:[~2003-06-13 17:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-13 14:51 Please Help, problem mounting jffs2 Frank R Callaghan
2003-06-13 15:47 ` Sid Gluckman
2003-06-13 15:53 ` Frank R Callaghan
2003-06-13 16:31 ` David Woodhouse
2003-06-13 16:58 ` Frank R Callaghan [this message]
2003-06-13 17:39 ` David Woodhouse
2003-06-13 18:11 ` Frank R Callaghan
2003-06-13 18:28 ` David Woodhouse
2003-06-13 18:47 ` Frank R Callaghan
2003-06-13 19:18 ` David Woodhouse
2003-06-13 22:52 ` Thomas Gleixner
2003-06-13 22:54 ` Frank R Callaghan
2003-06-16 16:06 ` Frank R Callaghan
2003-06-16 16:25 ` David Woodhouse
2003-06-16 18:21 ` Frank R Callaghan
2003-06-16 20:21 ` Thomas Gleixner
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=200306131258.58729.f.callaghan@ieee.org \
--to=f.callaghan@ieee.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