From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12579] ext4 filesystem hang
Date: Thu, 12 Feb 2009 16:42:52 -0800 (PST) [thread overview]
Message-ID: <20090213004252.8FE62108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12579-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12579
------- Comment #6 from sandeen@redhat.com 2009-02-12 16:42 -------
dJust for the record; here are the paths we're stuck on:
livecd:
sys_fdatasync
do_fsync
vfs_fsync
filemap_fdatawrite
__filemap_fdatawrite_range
do_writepage
ext4_da_writepages
write_cache_pages
lock page
(currently locked by pdflush)
pdflush:
pdflush
background_writeout
writeback_inodes
generic_sync_sb_inodes
__writeback_single_inode
do_writepages
ext4_da_writepages
write_cache_pages
lock page
(currently loscked by livecd)
the pdflush wbc looks like:
[1]kdb> wbc 0xffff88007d4abe10
struct writeback_control at 0xffff88007d4abe10
bdi = (null) sync_mode 0 (NONE)
nr_to_write = 992 pages_skipped = 0
range_start 0, range_end 0
nonblocking 1 congestion 0 kupdate 0 reclaim 0
writepages 1 range_cyclic 1 more_io 0 no_update 1
and the livecd-creator fsync wbc looks like:
[1]kdb> wbc 0xffff880012821ea8
struct writeback_control at 0xffff880012821ea8
bdi = (null) sync_mode 1 (ALL)
nr_to_write = 9223372036854775689 pages_skipped = 0
range_start 0, range_end 9223372036854775807
nonblocking 0 congestion 0 kupdate 0 reclaim 0
writepages 1 range_cyclic 0 more_io 0 no_update 1
--
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 prev parent reply other threads:[~2009-02-13 0:43 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 5:03 [Bug 12579] New: ext4 filesystem hang bugme-daemon
2009-02-12 15:24 ` [Bug 12579] " bugme-daemon
2009-02-12 16:36 ` Aneesh Kumar K.V
2009-02-12 17:49 ` Theodore Tso
2009-02-12 16:37 ` bugme-daemon
2009-02-12 16:44 ` bugme-daemon
2009-02-12 18:48 ` bugme-daemon
2009-02-12 18:55 ` bugme-daemon
2009-02-13 0:42 ` bugme-daemon [this message]
2009-02-13 11:49 ` Aneesh Kumar K.V
2009-02-13 11:50 ` bugme-daemon
2009-02-13 22:06 ` bugme-daemon
2009-02-14 1:50 ` Theodore Tso
2009-02-14 8:40 ` Aneesh Kumar K.V
2009-02-14 9:41 ` Aneesh Kumar K.V
2009-02-14 8:06 ` Aneesh Kumar K.V
2009-02-13 22:22 ` bugme-daemon
2009-02-14 2:07 ` bugme-daemon
2009-02-14 3:52 ` bugme-daemon
2009-02-14 8:07 ` bugme-daemon
2009-02-14 8:40 ` bugme-daemon
2009-02-14 9:42 ` bugme-daemon
2009-02-20 2:31 ` bugme-daemon
2009-02-21 17:35 ` bugme-daemon
2010-02-27 18:29 ` 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=20090213004252.8FE62108040@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).