From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Matt Dunnington <m@dunnington.eu>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: jfs_fsck fails at boot, after upgrade to recent kernel
Date: Wed, 04 May 2011 10:09:46 -0500 [thread overview]
Message-ID: <4DC16C3A.9000502@oracle.com> (raw)
In-Reply-To: <4DBD5A15.4080700@dunnington.eu>
On 05/01/2011 08:03 AM, Matt Dunnington wrote:
> Hi
>
> I'd appreciate some help with an issue that I'm experiencing with my
> root jfs partition being mounted read only at boot, due to jfs_fsck
> returning code 11. Below is a log of what is shown on screen after
> jfs_fsck has been run on the rootfs:
>
> Could not locate device by label or uuid
Seems to be failing to open the journal. Do you use an external
journal? If so, what device is it on?
> warning... fsck.jfs for device /dev/md1 exiteds with signal 11
Found a bug. not checking the return code of findLog() properly.
Fixing this will result in jfs_fsck failing cleanly rather than a
segfault, but probably won't get you any further.
> operational error
> remounting root filesystem read/write
> mount: / not mounted already, or bad option
I'm guessing that the filesystem is still clean, and the rw mount is
failing for the same reason as jfs_fsck. It doesn't find the journal.
> root filesystem could not be mounted read/write
>
> The issue arose when I upgraded my kernel from 2.6.28-gentoo-r2 to
> 2.6.38-gentoo-r3. If I boot my original kernel the system still boots
> fine, but booting the new kernel results in the errors above. Is this a
> bug, or perhaps I have missed something in my kernel configuration?
If you're using an external journal, then it may be a configuration
error and the kernel isn't configuring the journal device. If not, then
I'll have to dig deeper.
> Many thanks in advance for your kind assistance. Please let me know if
> you need any further information.
>
> Best Regards
> Matt Dunnington
Thanks,
Shaggy
prev parent reply other threads:[~2011-05-04 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 13:03 jfs_fsck fails at boot, after upgrade to recent kernel Matt Dunnington
2011-05-04 15:09 ` Dave Kleikamp [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=4DC16C3A.9000502@oracle.com \
--to=dave.kleikamp@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=m@dunnington.eu \
/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).