LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.20 kernel hang with USB drive and vfat doing ftruncate
Date: Fri, 16 Feb 2007 23:05:43 -0600 [thread overview]
Message-ID: <92CB3192-9176-4D30-B818-16A9C979F5E9@kernel.crashing.org> (raw)
In-Reply-To: <45D639F3.8030609@shaw.ca>
On Feb 16, 2007, at 5:10 PM, Robert Hancock wrote:
> Kumar Gala wrote:
>> I'm seeing an issue with a stock 2.6.20 kernel running on an
>> embedded PPC. I've got a usb flash drive plugged in and the
>> filesystem on the drive is vfat. Running with 64M and no swap.
>> If I execute a series of large (100M+) ftruncate() on the disk the
>> kernel will hang and never return. It seems to be stuck in the
>> idle loop().
>
> On FAT filesystems this forces the entire file contents of that
> size to be written out with zeros. Are you sure the kernel just
> isn't busy writing out all that data to the disk?
I'm pretty sure, seeing as if I run the test it takes maybe 20-30
seconds to create the file if it succeeds. However, I've weighted 10
minutes and still no prompt.
I'm also able to break in with a HW debugger and am always in the
idle loop.
- k
next prev parent reply other threads:[~2007-02-17 5:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.bxsB54F+7+006rE+o/VWUj5keQk@ifi.uio.no>
2007-02-16 23:10 ` 2.6.20 kernel hang with USB drive and vfat doing ftruncate Robert Hancock
2007-02-17 5:05 ` Kumar Gala [this message]
[not found] ` <fa.zK5W70l1vhk1YNxuwxFwZ8t1uIs@ifi.uio.no>
[not found] ` <fa.qFxa41A3LU3cQ19L+5DTEFMtCEY@ifi.uio.no>
2007-02-20 5:28 ` Robert Hancock
2007-02-16 19:54 Kumar Gala
2007-02-18 16:10 ` OGAWA Hirofumi
2007-02-19 21:58 ` Kumar Gala
2007-02-19 22:19 ` OGAWA Hirofumi
2007-02-19 22:27 ` Kumar Gala
2007-02-20 17:20 ` OGAWA Hirofumi
2007-02-19 22:06 ` Kumar Gala
2007-02-21 20:18 ` OGAWA Hirofumi
2007-02-21 20:57 ` Andrew Morton
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=92CB3192-9176-4D30-B818-16A9C979F5E9@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).