Summary: My original question was about finding a bad inode, which was causing the kernel to list a zillion messages to /var/log/messages. Nothing came of that, so I decided to reboot, and then found myself in the position of the boot process not wanting to mount this partition. It suggested that I run e2fsck on the file system. When I did this, e2fsck claimed that the superblock was bad, and suggested another e2fsck command, which also claimed that the superblock was bad. Things looked bleak. Solution: Do not run e2fsck, as suggested in the text when the boot puts you in maintenance mode (root login). Instead, run fsck. When I did this, fsck did not complain about the superblock. Instead, it ran the check. And, happily, it detected the inode that was the original cause of the problem and repaired it. The file system is now back on line. Does the e2fsck program require additional parameters if run direct? Things like block size and whatnot? If so, it may be bad to suggest using it in the boot help message in this context. Or, at least tell which options will be REQUIRED for e2fsck to function. Better yet, suggest running fsck instead, and let fsck figure out the options. That is, after all, fsck's job. -- Roger Oberholtzer OPQ Systems / Ramböll RST Ramböll Sverige AB Kapellgränd 7 P.O. Box 4205 SE-102 65 Stockholm, Sweden Office: Int +46 8-615 60 20 Mobile: Int +46 70-815 1696 And remember: It is RSofT and there is always something under construction. It is like talking about large city with all constructions finished. Not impossible, but very unlikely. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org