Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 18244 - fsck.jfs being passed incorrect parameters. Unable to boot.
Summary: fsck.jfs being passed incorrect parameters. Unable to boot.
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High blocker (vote)
Assignee: x86-kernel@gentoo.org (DEPRECATED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-03-26 14:18 UTC by Paul Slinski
Modified: 2003-04-04 12:05 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Slinski 2003-03-26 14:18:08 UTC
Rebooting one of my systems which is using jfs on it's root partition results in
an unknown but incorrect param sent to fsck.jfs. As a result, I'm dropped to a
shell where I can run fsck on the partition. Repairing the partition brings the
same error next boot even though there is nothing wrong with the partition.

Reproducible: Always
Steps to Reproduce:
1. Install base Gentoo system using jfs on root partition
2. update system
3. reboot

Actual Results:  
I cannot give an actual result as the system wont boot. But the error pertains
to incorrect parameters being passed to fsck.jfs (help is shown like when you
pass an option it does not know).

Expected Results:  
Working system.

Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r0)
=================================================================
System uname: 2.4.20-gentoo-r1 i686 Pentium III (Katmai)
GENTOO_MIRRORS="http://gentoo.oregonstate.edu/
http://distro.ibiblio.org/pub/Linux/distributions/gentoo"
CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config
/usr/kde/2/share/config /usr/kde/3/share/config"
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d"
PORTDIR="/usr/portage"
DISTDIR="/usr/portage/distfiles"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR_OVERLAY=""
USE="x86 crypt libg++ libwww mmx ncurses xml2 zlib gdbm berkdb readline tcpd pam
ssl python -3dnow -apm -arts -avi -cups -encode -gif -gnome -gpm -gtk -imlib
ipv6 -java -jpeg -kde mbox -mikmod -motif -mpeg -nls -oggvorbis -opengl -oss
-pdflib perl pic -png -qt -qtmt -quicktime -sdl -slang snmp -spell sse -svga
-truetype -X xml -xmms -xv"
COMPILER="gcc3"
CHOST="i686-pc-linux-gnu"
CFLAGS="-march=pentium3 -O3 -pipe"
CXXFLAGS="-march=pentium3 -O3 -pipe"
ACCEPT_KEYWORDS="x86 ~x86"
MAKEOPTS="-j5"
AUTOCLEAN="yes"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
FEATURES="distcc ccache sandbox"

Gentoo Base System version 1.4.3.4
Comment 1 Paul Slinski 2003-03-31 09:45:24 UTC
Where are the options initially passed to the fsck.* programs?
Comment 2 Paul Slinski 2003-03-31 09:56:47 UTC
Ok, so, checkroot is passing the following options to fsck.jfs: -C -a or, if a file /forcefsck is present: -C -a -f

There is no -C option for fsck.jfs (or cramfs or minix for that matter).

I'm hoping that removing the -C from these scripts will allow me to boot the system (ironicly, it's part of a H.A. cluster).

-P
Comment 3 Paul Slinski 2003-04-04 11:00:31 UTC
What a mess that was.

It was because devfsd would not start with the version of gawk which was installed. (Ref Bug 18192)

Please mark as resolved.
Comment 4 Nicholas Wourms 2003-04-04 12:05:04 UTC
Marked as resolved per reporter