fsck -v buggy

While running fsck -v, I got the following SEG fault:

lr=0x4005f7d8 (bad address=0x00000004, code 3)
99)
pc : [<020013b4>] lr : [<4005f7d8>]
sp : bffffd44 ip : bffff67c fp : bffffdb8
r10: 400fe134 r9 : 0200a6e0 r8 : 0200a3d4
r7 : 0200a778 r6 : 00000000 r5 : 00000000 r4 : bffffd4c
r3 : 00000000 r2 : bffffd56 r1 : 02002203 r0 : 00000009
Flags: Nzcv IRQs on FIQs on Mode USER_32 Segment user
Control: C80C517D Table: C80C517D DAC: 00000015
Function entered at [<02001328>] from [<02001dec>]
r7 = 0200a3f0
r6 = 00000000
r5 = 0200a6dc
r4 = 00000000
Function entered at [<02001cc0>] from [<4003995c>]
r9 = 02001eb8
r8 = 400fd0a0
r7 = 02001cc0
r6 = 400217c0
r5 = 00000003
r4 = bffffe24
Function entered at [<4003982c>] from [<020008c8>]
Segmentation fault
empeg:/etc#

Paul Gillingwater
Red Hat Certified Engineer

And for your further amusement, I got this message next, but I know where it comes from:

empeg:/etc# reboot
WARNING: could not determine runlevel - doing soft reboot
(it's better to use shutdown instead of reboot from the command line)
shutdown: warning: cannot open /var/run/shutdown.pid
You don't exist. Go away.
empeg:/etc#

Paul Gillingwater
Red Hat Certified Engineer

The /sbin/fsck from e2fsprog-1.18 seems to be a bit buggy. However, running /sbin/fsck.ext2 directly works (this is what the player does anyway).


- John.

(The above may not represent the views of empeg :)