Red Hat Bugzilla – Bug 502219
ext2 traceback when mounting with sync
Last modified: 2015-01-04 17:30:59 EST
I see this every time I boot..
[ 26.417949] ------------[ cut here ]------------
[ 26.417960] WARNING: at fs/fs-writeback.c:277 __writeback_single_inode+0x124/0x27a() (Not tainted)
[ 26.417967] Hardware name:
[ 26.417971] Modules linked in: serio_raw pcspkr usb_storage 3c59x i2c_viapro mii i2c_core firewire_ohci via_velocity firewire_core crc_ccitt crc_itu_t ata_generic pata_acpi pata_via ext2 [last unloaded: scsi_wait_scan]
[ 26.418036] Pid: 866, comm: rc.sysinit Not tainted 220.127.116.11-140.fc11.i686.PAE #1
[ 26.418042] Call Trace:
[ 26.418062] [<c0435982>] warn_slowpath+0x7c/0xa4
[ 26.418079] [<c0429798>] ? __dequeue_entity+0x28/0x2c
[ 26.418088] [<c042982c>] ? set_next_entity+0x90/0xfc
[ 26.418100] [<c040808e>] ? __switch_to+0x7b/0xfd
[ 26.418117] [<c044d0e8>] ? clocksource_read+0xc/0xf
[ 26.418126] [<c044d44a>] ? getnstimeofday+0x59/0xec
[ 26.418144] [<c0421bc7>] ? default_spin_lock_flags+0x8/0xd
[ 26.418158] [<c047337d>] ? delayacct_end+0x8d/0x95
[ 26.418168] [<c04733e7>] ? __delayacct_blkio_end+0x35/0x3b
[ 26.418176] [<c04be8a9>] __writeback_single_inode+0x124/0x27a
[ 26.418189] [<c0715614>] ? __wait_on_bit+0x57/0x60
[ 26.418202] [<c04c38a8>] ? sync_buffer+0x0/0x3c
[ 26.418211] [<c07156bd>] ? out_of_line_wait_on_bit+0xa0/0xa8
[ 26.418219] [<c04bea24>] sync_inode+0x25/0x38
[ 26.418256] [<dc82ff98>] ext2_sync_inode+0x2c/0x33 [ext2]
[ 26.418282] [<dc83412c>] ext2_xattr_set2+0x3ac/0x4cc [ext2]
[ 26.418304] [<dc8347f9>] ext2_xattr_set+0x5ad/0x5f0 [ext2]
[ 26.418330] [<dc8355ec>] ext2_init_security+0x4d/0x6d [ext2]
[ 26.418351] [<dc82fa9a>] ext2_new_inode+0x7e2/0x90e [ext2]
[ 26.418375] [<dc831b90>] ext2_create+0x13/0x8f [ext2]
[ 26.418389] [<c04b085c>] vfs_create+0x6e/0x88
[ 26.418399] [<c04b1359>] do_filp_open+0x1e7/0x5e9
[ 26.418413] [<c0568711>] ? strncpy_from_user+0x38/0x54
[ 26.418427] [<c04b938f>] ? alloc_fd+0xd0/0xdc
[ 26.418439] [<c04a7162>] do_sys_open+0x47/0xbc
[ 26.418449] [<c04a7223>] sys_open+0x23/0x2b
[ 26.418460] [<c040945f>] sysenter_do_call+0x12/0x34
[ 26.418466] ---[ end trace 75ddb472065f94ae ]---
The mount it complains about is mounted with the 'sync' option.
why would you want to mount that way? ;)
WARN_ON(inode->i_state & I_NEW);
which was introduced in
Author: Nick Piggin <firstname.lastname@example.org>
Date: Thu Mar 12 14:31:38 2009 -0700
fs: new inode i_state corruption fix
I'll look into it, thanks. This is ringing a bell but I'm not sure why....
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
Ugh sorry this sat for so long. Dave, do you still see it on newer kernels? I'm not able to hit it but then I don't have ext2 root mounted sync ...