[SATLUG] Dear Journal, GO AWAY
dave at coverstreet.com
Sat Aug 3 22:22:01 CDT 2002
Ok, I'm lost. Someone please tell me what I'm missing here. I've got a
P200MMX running an 80GB IDE drive and 64MB of RAM in my closet for a
file server. I just loaded it a month ago with RedHat 7.3 with a
standard load, nothing fancy at all.
When I loaded it, I formatted it all ext3, since journalling on the file
server seemed like a good idea. Extra precautions and all.
Unfortunately this journalling has been more of a pain in the butt and
it just won't go away. Every few days it will decide it's unhappy and
journal_bmap_R013e9a84: journal block not found at offset 7968 on
Aborting journal on device ide0(3,1).
EXT3-fs abort (device ide0(3,1)): ext3_journal_start: Detected aborted
Remounting filesystem read-only
and will remount my / partition read only. Only the / partition too,
not the partitions with any of the file stores on it which I've been
constantly accessing. Mounting / read only messes up any programs that
like to write things to /etc (like Samba) and of course trying to save
anything to root's home directory.
I've looked all over and the basic fix for ext3 problems seems to be to
e2fsck -fy /dev/hdaX
to replay the journal on the drive and make sure it's ok, and then to
mount it as ext2. I've done this, I've edited my /etc/fstab so that
nothing mounts ext2, and yet I'm still getting this error. Doing a
'mount' shows everything mounted ext2, and yet this error just won't go
away. The machine runs great otherwise, up until the point that it
wants to be read-only again.
So does anyone know how to fix this, or how to remove ext3 completely,
preferably without reloading from scratch?
More information about the Satlug