Per Jessen wrote: > Yep, the same thing happened. I'll try it again though - it's been a while, > so just to > make sure I've the story straight. I'll let you know.
OK, this is what happens: 1. I start out with a clean system, 3 partitions formatted with JFS. 2. I install SuSE 9.3 using boot CDROM and NFS install. 3. As SuSE 9.3 won't boot with JFS, I boot up the Rescue system and rebuild the kernel and initrd with support for JFS. 4. The initial reboot (to finish off the install) works fine. 5. The first system start-up doesn't - produces lots of XT_GETPAGE: xtree page corrupt which makes the root filesystem read-only. Doesn't affect /boot nor /home. I attempt to rescue the situation by fscking the foot file-system and remounting r/w, which works fine, until the next startup when the problem re-manifests itself. After one of these start-ups, including fscking and remount, I was checking out a few things - and discovered that /lost+found held about 7500 entries. All called <something>.RCN and most appear to be block or char devices. I cleared out /lost+found - which may turn out to have been a mistake - and at the next reboot, /dev/console couldn't be found ... When I rebuild the kernel, I setup the initrd to include jfs as a module - but I've also tried with JFS built-in. /Per Jessen, Zürich -- http://www.spamchek.com/freetrial - managed anti-spam and anti-virus solution. Sign up for your free 30-day trial now! ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
