From: Jan Kara <jack@suse.cz>
To: Helge Hafting <helgehaf@aitel.hist.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Hanging ext3 or USB, linux 2.6.16-rc6-mm2
Date: Thu, 6 Apr 2006 20:47:12 +0200 [thread overview]
Message-ID: <20060406184712.GA5458@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <20060327210514.GA24421@aitel.hist.no>
> I managed to hang ext3 or usb today.
> I have a small machine that boot off a compactflash card.
> I want to use a bigger card, so I used scp to copy everything
> from that machine to a new 4GB card in a usb cardreader.
> This cardreader have never given me trouble before, but is
> usually used for reading.
>
> I decided on a ext3 fs in order to avoid long fsck runs,
> and a minimal 4MB journal in order to not waste space.
> Disk seeks are supposed to be really cheap on a device
> with no moving parts anyway. The root reserved percentage
> is 1% instead of the usual 5% - more space, and fragmentation
> will probably not hurt much with cheap seeks.
>
> When scp had filled the card to 71% of capacity (according to df),
> it stopped in the middle of a file. I first suspected network
> errors, but a "ls /mnt" hung.
>
> I now have the following processes in D-state:
> [khubd] [scsi_eh_4] [usb-storage] [kjournald] scp,
> 3 x [pdflush], 2 x ls, lsusb, and a sync.
>
> Could this be a ext3 problem due to the small journal or something?
>
> Or is a usb problem more likely? "Dmesg" shows an
> usb disconnect sometime after I mounted that filesystem,
> but it seems to be usblp0 which looks like the printer to me.
I'd guess it is some USB/block layer problem. If just ext3 hung, then
you would not see [usb-storage] and similar hung. I would need to see
where each process hung to tell more..
Honza
--
Jan Kara <jack@suse.cz>
SuSE CR Labs
next prev parent reply other threads:[~2006-04-06 18:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 21:05 Helge Hafting
2006-04-06 18:47 ` Jan Kara [this message]
2006-04-07 8:47 ` Helge Hafting
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=20060406184712.GA5458@atrey.karlin.mff.cuni.cz \
--to=jack@suse.cz \
--cc=helgehaf@aitel.hist.no \
--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
all inboxes | Powered by JetHome®