From: "Christopher S. Aker" <caker@theshore.net>
To: xen devel <xen-devel@lists.xensource.com>
Subject: Linux 3.1 domU + ext3 = WARNING: at fs/ext3/inode.c
Date: Tue, 25 Oct 2011 15:48:00 -0400 [thread overview]
Message-ID: <4EA71270.2050303@theshore.net> (raw)
Either right on boot, or shortly thereafter, the following occurs with
either writeback or ordered filesystems. Multiple reports, all
different machines, different users... Some people had success after I
changed CONFIG_EXT3_DEFAULTS_TO_ORDERED off, however some still had
problems... That was my only config change from 3.0.4. Them rebooting
back into 3.0.4 fixed it.
------------[ cut here ]------------
WARNING: at fs/ext3/inode.c:1620 ext3_ordered_writepage+0x20a/0x230()
Modules linked in:
Pid: 2149, comm: flush-202:0 Not tainted 3.1.0-linode39 #1
Call Trace:
[<c01346f8>] ? warn_slowpath_common+0x78/0xb0
[<c025666a>] ? ext3_ordered_writepage+0x20a/0x230
[<c025666a>] ? ext3_ordered_writepage+0x20a/0x230
[<c013474b>] ? warn_slowpath_null+0x1b/0x20
[<c025666a>] ? ext3_ordered_writepage+0x20a/0x230
[<c01067e4>] ? check_events+0x8/0xc
[<c018c3c8>] ? __writepage+0x8/0x30
[<c018cbc6>] ? write_cache_pages+0x196/0x390
[<c018c3c0>] ? set_page_dirty+0x60/0x60
[<c018cdfe>] ? generic_writepages+0x3e/0x60
[<c01d4ae5>] ? writeback_single_inode+0x115/0x2b0
[<c0102b18>] ? xen_end_context_switch+0x8/0x10
[<c01d52c1>] ? writeback_sb_inodes+0x171/0x210
[<c01d58d5>] ? __writeback_inodes_wb+0x75/0xb0
[<c01d5b31>] ? wb_writeback+0x1a1/0x1b0
[<c0106007>] ? xen_force_evtchn_callback+0x17/0x30
[<c01067e4>] ? check_events+0x8/0xc
[<c01d5cef>] ? wb_do_writeback+0x1af/0x1c0
[<c01d5d71>] ? bdi_writeback_thread+0x71/0x130
[<c01d5d00>] ? wb_do_writeback+0x1c0/0x1c0
[<c014e1a4>] ? kthread+0x74/0x80
[<c014e130>] ? kthread_worker_fn+0x170/0x170
[<c06c63b6>] ? kernel_thread_helper+0x6/0x10
---[ end trace 702f842be742d945 ]---
And a different user:
------------[ cut here ]------------
WARNING: at fs/ext3/inode.c:1695 ext3_writeback_writepage+0x12a/0x150()
Modules linked in:
Pid: 2146, comm: flush-202:0 Not tainted 3.1.0-linode39 #1
Call Trace:
[<c01346f8>] ? warn_slowpath_common+0x78/0xb0
[<c025643a>] ? ext3_writeback_writepage+0x12a/0x150
[<c025643a>] ? ext3_writeback_writepage+0x12a/0x150
[<c013474b>] ? warn_slowpath_null+0x1b/0x20
[<c025643a>] ? ext3_writeback_writepage+0x12a/0x150
[<c01067e4>] ? check_events+0x8/0xc
[<c018c3c8>] ? __writepage+0x8/0x30
[<c018cbc6>] ? write_cache_pages+0x196/0x390
[<c018c3c0>] ? set_page_dirty+0x60/0x60
[<c010dfd8>] ? sched_clock+0x8/0x10
[<c0154452>] ? sched_clock_local+0xb2/0x190
[<c018cdfe>] ? generic_writepages+0x3e/0x60
[<c01d4ae5>] ? writeback_single_inode+0x115/0x2b0
[<c0102b18>] ? xen_end_context_switch+0x8/0x10
[<c01d52c1>] ? writeback_sb_inodes+0x171/0x210
[<c01d58d5>] ? __writeback_inodes_wb+0x75/0xb0
[<c01d5b31>] ? wb_writeback+0x1a1/0x1b0
[<c0106007>] ? xen_force_evtchn_callback+0x17/0x30
[<c01067e4>] ? check_events+0x8/0xc
[<c01d5cef>] ? wb_do_writeback+0x1af/0x1c0
[<c01d5d71>] ? bdi_writeback_thread+0x71/0x130
[<c01d5d00>] ? wb_do_writeback+0x1c0/0x1c0
[<c014e1a4>] ? kthread+0x74/0x80
[<c014e130>] ? kthread_worker_fn+0x170/0x170
[<c06c63b6>] ? kernel_thread_helper+0x6/0x10
---[ end trace 0a37bc36a180e73c ]---
Am I barking up the wrong list?
Thanks,
-Chris
next reply other threads:[~2011-10-25 19:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 19:48 Christopher S. Aker [this message]
2011-10-25 20:12 ` Linux 3.1 domU + ext3 = WARNING: at fs/ext3/inode.c Konrad Rzeszutek Wilk
2011-10-25 20:40 ` Christopher S. Aker
2011-10-25 21:01 ` Konrad Rzeszutek Wilk
2011-10-25 21:15 ` Konrad Rzeszutek Wilk
2011-10-26 20:26 ` Christopher S. Aker
2011-10-26 20:36 ` Konrad Rzeszutek Wilk
2011-10-26 21:23 ` Christopher S. Aker
2011-10-27 15:41 ` Konrad Rzeszutek Wilk
2011-10-27 16:23 ` Pasi Kärkkäinen
2011-10-27 16:41 ` Konrad Rzeszutek Wilk
2011-12-01 19:10 ` Konrad Rzeszutek Wilk
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=4EA71270.2050303@theshore.net \
--to=caker@theshore.net \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.