From: David Woodhouse <dwmw2@infradead.org>
To: joakim.tjernlund@lumentis.se
Cc: linux-mtd@lists.infradead.org
Subject: Re: Disk blocks for long periods
Date: Mon, 05 Aug 2002 14:44:00 +0100 [thread overview]
Message-ID: <22091.1028555040@redhat.com> (raw)
In-Reply-To: <IGEFJKJNHJDCBKALBJLLMEHIFFAA.joakim.tjernlund@lumentis.se>
joakim.tjernlund@lumentis.se said:
> I have noticed that if i copy a "big" file(580K) it sometimes take up
> to 42 seconds before it's finished. Normally it takes about 3-4
> seconds. When this long copy happen, top reports that kupdate and the
> copy(cp) process is in D state, the rest is sleeping. The FS is a 45%
> usage. FS is about 63MB in size. Using the stable branch.
> Why does it block for so long time?
Dunno. What's it doing? Where are cp and kupdate sleeping? (SysRq-T).
> Also, if I fill the FS up to 100% and later reboots, it kan take
> 10-15 minutes before init starts to run. The root fs mount takes about
> 20 seconds and the system just stops between the last message from the
> kernel and when init prints its version.
> It is just the first reboot after I fill the FS, once I have gotten
> past the first reboot and reboots again, things are back to normal.
More logs and SysRq-T required. Sounds like it's erasing blocks and for
some reason not allowing anything else to happen while it's doing it.
--
dwmw2
next prev parent reply other threads:[~2002-08-05 13:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 21:59 MTD Partition problems Malik, Vipin [FRCO/HOU]
2002-08-03 9:46 ` Jörn Engel
2002-08-03 12:47 ` Vipin Malik
2002-08-03 14:10 ` Jörn Engel
2002-08-03 19:24 ` Vipin Malik
2002-08-03 23:50 ` Jörn Engel
2002-08-05 19:10 ` Vipin Malik
2002-08-06 9:35 ` Jörn Engel
2002-08-06 19:08 ` Vipin Malik
2002-08-05 10:35 ` David Woodhouse
2002-08-05 13:35 ` Disk blocks for long periods Joakim Tjernlund
2002-08-05 13:44 ` David Woodhouse [this message]
2002-08-05 13:59 ` Joakim Tjernlund
2002-08-05 14:12 ` David Woodhouse
2002-08-05 14:32 ` Joakim Tjernlund
2002-08-05 14:42 ` David Woodhouse
2002-08-05 21:45 ` Jasmine Strong
-- strict thread matches above, loose matches on Subject: below --
2002-08-05 18:50 Dave Ellis
2002-08-06 10:06 ` Joakim Tjernlund
2002-08-06 12:14 ` David Woodhouse
2002-08-06 13:52 ` Jörn Engel
2002-08-06 13:53 ` David Woodhouse
2002-08-06 16:45 ` Joakim Tjernlund
2002-08-07 9:51 ` David Woodhouse
2002-08-08 7:23 ` Joakim Tjernlund
2002-08-08 8:02 ` David Woodhouse
2002-08-08 8:32 ` Joakim Tjernlund
2002-08-08 8:40 ` David Woodhouse
2002-08-06 14:53 Dave Ellis
2002-08-06 15:09 ` Joakim Tjernlund
2002-08-07 11:11 ` David Woodhouse
2002-08-06 20:16 Dave Ellis
2002-08-06 21:06 ` Joakim Tjernlund
2002-08-07 16:42 Dave Ellis
2002-08-08 7:08 ` Joakim Tjernlund
2002-08-08 8:08 ` David Woodhouse
2002-08-08 9:15 ` Joakim Tjernlund
2002-08-08 9:18 ` 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=22091.1028555040@redhat.com \
--to=dwmw2@infradead.org \
--cc=joakim.tjernlund@lumentis.se \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.