From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12821] filesystem corrupts on heavy I/O
Date: Tue, 17 Mar 2009 08:28:35 -0700 (PDT) [thread overview]
Message-ID: <20090317152835.8F38C10800E@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12821-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12821
sandeen@redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|fs_ext4@kernel-bugs.osdl.org|sandeen@redhat.com
Status|NEW |ASSIGNED
------- Comment #21 from sandeen@redhat.com 2009-03-17 08:28 -------
(In reply to comment #20)
> As noted in attachments, I have applied the patch and completed my BitTorrent
> download (which was problematic without the patch).
>
> linux-image-2.6.28-8-generic (Ubuntu): Download unable to complete due to EXT4
> error and non-responsive sync.
>
> linux-image-2.6.28-9-generic (Ubuntu+potential fix patch), first try: Computer
> is found unresponsive and screen dark, power and capslock blinking.
That indicates a panic, but we'd need a lot more info, which you probably can't
gather at this time. Getting panics visible when you're in X is tricky,
netconsole or serial console or similar may be needed. So you paniced, but we
have no idea why, unfortunately.
> linux-image-2.6.28-9-generic (Ubuntu+potential fix patch), second try: Computer
> is normal, no errors in dmesg about EXT4, download is successful.
well, that sounds good ;)
> The failure on first try is a new behavior I have not seen before with this
> machine. I therefore am reporting inconclusively that the patch works for me.
Ok, thanks for the testing.. It's headed upstream in any case, I think, as it
seems pretty well correct from inspection and review.
Oh, re: the stat of that inode, for a 10G file that's a metric ton of
extents... you should encourage whichever torrent client this is to use the
preallocation routines now available (fallocate(2)) - a syscall now, exposed by
glibc soon.
the file has 600+ extent tree *nodes* each of which holds an extent... you have
nearly 105000 extents. That's ... impressive ... :)
--
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.
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2009-03-17 15:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 16:42 [Bug 12821] New: filesystem corrupts on heavy I/O bugme-daemon
2009-03-05 17:26 ` [Bug 12821] " bugme-daemon
2009-03-05 17:46 ` bugme-daemon
2009-03-05 18:06 ` bugme-daemon
2009-03-05 18:13 ` bugme-daemon
2009-03-05 18:59 ` bugme-daemon
2009-03-05 19:06 ` bugme-daemon
2009-03-05 19:25 ` bugme-daemon
2009-03-06 6:11 ` bugme-daemon
2009-03-06 7:16 ` bugme-daemon
2009-03-06 14:18 ` bugme-daemon
2009-03-06 20:21 ` bugme-daemon
2009-03-06 20:30 ` bugme-daemon
2009-03-10 10:03 ` bugme-daemon
2009-03-13 7:11 ` bugme-daemon
2009-03-13 15:03 ` bugme-daemon
2009-03-15 4:56 ` bugme-daemon
2009-03-15 5:23 ` bugme-daemon
2009-03-17 6:07 ` bugme-daemon
2009-03-17 6:07 ` bugme-daemon
2009-03-17 6:30 ` bugme-daemon
2009-03-17 15:28 ` bugme-daemon [this message]
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=20090317152835.8F38C10800E@picon.linux-foundation.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).