linux-ext4 - grub / ext4 compatibility problem?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <200906171648.59573.bzolnier@gmail.com>
Date:	Wed, 17 Jun 2009 16:48:59 +0200
From:	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>
To:	"Theodore Ts'o" <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: grub / ext4 compatibility problem?

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
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html