public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
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 11:53:42 -0400	[thread overview]
Message-ID: <200306131153.42657.f.callaghan@ieee.org> (raw)
In-Reply-To: <OOEOKBMECIFAEPIMFOGIMEPICBAA.sgluckman@omnitech.com>

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
  PID TTY     Uid        Size State Command
    1         root        468   S   init
    2         root          0   S   [keventd]
    3         root          0   S   [ksoftirqd_CPU0]
    4         root          0   S   [kswapd]
    5         root          0   S   [bdflush]
    6         root          0   D   [kupdated]
    7         root          0   S   [mtdblockd]
   11         root          0   S   [kjournald]
   35         root        376   S   /sbin/udhcpc -n -s 
/etc/udhcpd/default.scri
   41         nobody      472   S   /sbin/boa
   46         root        492   S   /sbin/bftpd -d
   50         root          0   S   [rpciod]
   54         root          0   S   [kjournald]
   81         root       1528   R   /myapp/hiresprinthead
   83         root        656   R   /myapp/hires_controler
   85 ttyS1   root        488   S   -sh
   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
   92 ttyS1   root        460   R   ps ax



On Friday 13 June 2003 11:47 am, Sid Gluckman wrote:
> I am kind of a newbie to the jffs2 thing but are you sure that it is just
> "sitting" there?  I found that when a jffs2 system is mounted for the first
> time with something in the filesystem it goes through some kind of
> cataloging function where I'm guessing it is characterizing the device for
> bad flash bytes?  Anyways, if you do a 'df' in another shell while it is
> sitting there you will see that the device is mounted and that the used
> space first slowly cycles to fully used then slowly back down to the
> correct used space.  I'm sure someone else could enlighten us both as to
> what it is actually doing during this time.  Once it completes this cycle
> everything is fine and it doesn't do it on subsequent mounts.  Depending on
> the flash size this could take quite a while.
>
> Hope this helps.
>
> Sid
>
> -----Original Message-----
> From: linux-mtd-bounces@lists.infradead.org
> [mailto:linux-mtd-bounces@lists.infradead.org]On Behalf Of Frank R
> Callaghan
> Sent: Friday, June 13, 2003 8:52 AM
> To: linux-mtd@lists.infradead.org
> Subject: Please Help, problem mounting jffs2
>
>
> Hi All,
>
> I have a problem with mounting my new mtd/jffs2 system
> after lots of experiment I have found the after doing
> 'eraseall /dev/mtd0' I can 'mount -t jffs2 /dev/mtdblock0 /mnt/flash'
> with no problem :) but if I umount it and try to re-mount it
> will sit there forever !
> If I cp a jffs2.img to the device the mount will also lockup
> If I erase -> mount I can create files df with no problems,
>
> It seem like the mount does not like mounting with anything
> in the filesystem !
>
> What infomation should I gather to find out whats gonig on here ?
>
> Any help greatly appreciated,
>
> TIA,
>         Frank.
>
>
>
>
>
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2003-06-13 16:05 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 [this message]
2003-06-13 16:31     ` David Woodhouse
2003-06-13 16:58       ` Frank R Callaghan
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=200306131153.42657.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