From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12603] New: firefox downloads hang on ext4; fine on ext3
Date: Sun, 1 Feb 2009 14:32:20 -0800 (PST) [thread overview]
Message-ID: <bug-12603-13602@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=12603
Summary: firefox downloads hang on ext4; fine on ext3
Product: File System
Version: 2.5
KernelVersion: 2.6.27.10
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: ext4
AssignedTo: fs_ext4@kernel-bugs.osdl.org
ReportedBy: avery@shadypixel.com
Distribution:
Debian testing/unstable
Software Environment:
Kernel is actually from http://wiki.debian.org/DebianKernel. Version is
2.6.27-1~experimental.1~snapshot.12516, which appears to be based on 2.6.27.10.
Problem Description:
I mentioned this in my last bug report
(http://bugzilla.kernel.org/show_bug.cgi?id=12424), but it seems that was
something unrelated (I think). My firefox downloads have been hanging off and
on since reformatting ext3->ext4. I've finally found a way to reproduce this
100% of the time.
Steps:
1.) download large file to folder on ext4 fs
2.) close all firefox windows except the download manager before download
completes
3.) download will hang at nearly 100%
This happens every single time. If I keep another firefox window open (beside
the downloads mini-window), the download always completes successfully. If I do
the same steps except save the file to an ext3 fs, it always works.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-02-01 22:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 22:32 bugme-daemon [this message]
2009-02-01 23:35 ` [Bug 12603] firefox downloads hang on ext4; fine on ext3 bugme-daemon
2009-02-02 0:05 ` bugme-daemon
2009-02-02 0:11 ` bugme-daemon
2009-02-02 2:37 ` bugme-daemon
2009-02-02 2:52 ` bugme-daemon
2009-02-02 2:52 ` bugme-daemon
2009-02-02 2:57 ` bugme-daemon
2009-02-02 3:29 ` bugme-daemon
2009-02-02 3:32 ` bugme-daemon
2009-02-02 3:39 ` bugme-daemon
2009-02-02 3:46 ` bugme-daemon
2009-02-02 4:42 ` bugme-daemon
2009-02-02 4:42 ` bugme-daemon
2009-02-02 4:43 ` bugme-daemon
2009-02-02 4:44 ` bugme-daemon
2009-02-02 12:33 ` bugme-daemon
2009-05-19 18:40 ` bugzilla-daemon
2009-05-20 20:20 ` bugzilla-daemon
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=bug-12603-13602@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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).