From: Michael Michael <memmel2@yahoo.com>
To: linux-mtd@lists.infradead.org
Subject: Re: Slow jffs2 startup on DOM
Date: Wed, 20 Feb 2002 23:35:59 -0800 (PST) [thread overview]
Message-ID: <20020221073559.89225.qmail@web14703.mail.yahoo.com> (raw)
In-Reply-To: <441701c1ba2c$2cf1dc60$1900000a@v.vmanage.com>
Ahh thanks I know what it is. I'm using a nfs root and
have modified nfs to read the DOM as a persistant
local cache at boot (cool IMHO). So I'm not unmounting
the DOM clean when I unmount the NFS root. Thanks just
needed to look in the right place and "know" for sure
that it can be fast.
I had already tested and seen that if you mount/umount
its fast the second time but I guess I'm always
unclean it the case of the NFS root since I can't
manually unmount the Cache in this case oops. Of
course a nice message from JFF2 saying its doing a
clean/dirty mount would be nice of maybe I missed that
to : )
Thanks agian I'll go back into hiding
Mike
--- Gad Hayisraeli <gad@syete.co.il> wrote:
>
> ----- Original Message -----
> From: "Michael Michael" <memmel2@yahoo.com>
> To: <linux-mtd@lists.infradead.org>
> Sent: Wednesday, February 20, 2002 8:33 AM
> Subject: Slow jffs2 startup on DOM
>
>
> > Hello I'm using jffs2 on a DOM with the block
> device
> > driver. I find the startup times very slow. It
> seams
> > to me from reading the source that jffs2 may be
> > scanning every block with this driver. It takes
> about
> > 3 min for the first mount. Is there anyway to fix
> this
> > ?
> > Would it be possible to add say a checkpoint such
> > that if the disk is "clean" we proceed with
> normal
> > startup ?
> > I do write to the DOM but I can certianly ensure
> that
> > its clean except on sudden power downs. I suspect
> > that a lot of people who write to the devices can
> > ensure that the writes are checkpointed so we
> don't
> > have to do a full scan.
> >
> > Mike
> >
>
> in my case (mediaEngine + assabet), i encountered
> some slowness like you
> did, just when i previously shutdown the device
> without unmounting + syncing
> first
> (this commands are regularly handled by S0Reboot on
> rc6.d dir)
>
> Gad
>
>
>
>
>
______________________________________________________
> Linux MTD discussion mailing list
>
http://lists.infradead.org/mailman/listinfo/linux-mtd/
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
next prev parent reply other threads:[~2002-02-21 7:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 14:24 jffs2 & new linux zlib Clive Davies
2002-02-20 6:33 ` Slow jffs2 startup on DOM Michael Michael
2002-02-20 16:32 ` Gad Hayisraeli
2002-02-21 7:35 ` Michael Michael [this message]
2002-02-21 8:33 ` David Woodhouse
2002-02-21 9:51 ` Michael Michael
2002-02-21 9:53 ` David Woodhouse
2002-02-21 11:34 ` Michael Michael
2002-02-21 12:32 ` Michael Michael
2002-02-22 12:05 ` Simon Evans
2002-02-22 14:59 ` Michael Michael
2002-02-24 9:18 ` Gad Hayisraeli
2002-02-24 10:47 ` Joakim Tjernlund
2002-02-24 12:04 ` David Woodhouse
[not found] <14164.1014588644@redhat.com>
2002-02-25 7:47 ` Joakim Tjernlund
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=20020221073559.89225.qmail@web14703.mail.yahoo.com \
--to=memmel2@yahoo.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