From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: grub / ext4 compatibility problem?
Date: Wed, 17 Jun 2009 16:48:59 +0200 [thread overview]
Message-ID: <200906171648.59573.bzolnier@gmail.com> (raw)
Hi,
I've run into a really peculiar problem today..
After the last /boot/grub/grub.conf update (just to test today's linux-next)
grub reads the file's content as a garbage and drops into the interactive
mode (cat /boot/grub/grub.conf from within the inteactive mode shows garbage,
other files are read fine).
This makes booting quite challenging (interactive mode is easy to manage,
remembering kernel name derived from the git tree is the difficult part ;)
but once the system is running I can read the content of the file just fine.
On the first manual boot ext4 reported some filesystem problems & fixed them:
EXT4-fs (hda1): barriers enabled
kjournald2 starting: pid 449, dev hda1:20, commit interval 5 seconds
EXT4-fs (hda1): delayed allocation enabled
EXT4-fs: file extents enabled
EXT4-fs: mballoc enabled
EXT4-fs (hda1): orphan cleanup on readonly fs
EXT4-fs (hda1): ext4_orphan_cleanup: deleting unreferenced inode 261260
EXT4-fs (hda1): 1 orphan inode deleted
EXT4-fs (hda1): recovery complete
EXT4-fs (hda1): mounted filesystem with ordered data mode
but the /etc/grub/grub.conf problem is still there (I thought that it may
be a good idea to report it first before trying to run fsck manually).
This is on Fedora 11 system (I upgraded from Fedora 10 few days ago) with
all updates and ext3 migrated (per HOWTO on ext4 wiki) to ext4 yesterday.
Is this something worth people's attention or should I just try to run fsck
manually?
Thanks,
Bart
next reply other threads:[~2009-06-17 14:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 14:48 Bartlomiej Zolnierkiewicz [this message]
2009-06-17 14:46 ` grub / ext4 compatibility problem? Eric Sandeen
2009-06-17 15:07 ` Bartlomiej Zolnierkiewicz
2009-06-17 15:20 ` Eric Sandeen
2009-06-17 15:40 ` Bartlomiej Zolnierkiewicz
2009-06-17 18:03 ` Bartlomiej Zolnierkiewicz
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=200906171648.59573.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).