From: bugme-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 12697] MAINLINE
Date: Thu, 12 Feb 2009 11:49:40 -0800 (PST) [thread overview]
Message-ID: <20090212194940.A4926108040@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-12697-13602@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=12697
sandeen@redhat.com changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|fs_ext4@kernel-bugs.osdl.org|sandeen@redhat.com
Status|NEW |ASSIGNED
------- Comment #1 from sandeen@redhat.com 2009-02-12 11:49 -------
-30 is EROFS
I assume you've had some error that shut down the filesystem previously, can
you look?
This seems to ring a bell for me but can't remember for sure if it's fixed,
yet.
/* start a new transaction*/
handle = ext4_journal_start(inode, needed_blocks);
if (IS_ERR(handle)) {
ret = PTR_ERR(handle);
printk(KERN_CRIT "%s: jbd2_start: "
"%ld pages, ino %lu; err %d\n", __func__,
wbc->nr_to_write, inode->i_ino, ret);
dump_stack();
goto out_writepages;
}
we should maybe check for a shutdown fs here before we generate all these
messages.
--
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.
next prev parent reply other threads:[~2009-02-12 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 19:12 [Bug 12697] New: MAINLINE bugme-daemon
2009-02-12 19:49 ` bugme-daemon [this message]
2009-02-12 19:50 ` [Bug 12697] ext4_journal_start() spews errors on readonly filesystem bugme-daemon
2009-02-12 20:53 ` bugme-daemon
2009-02-12 20:57 ` bugme-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=20090212194940.A4926108040@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).