On Mon, March 14, 2005 16:18, Dave Kleikamp said: > > You should run fsck -f against the file system to make sure it gets > fixed, since this function should have just written the block map to
too late - it got mkfs'ed right after the oops by another process. > This loop has probably outlived it's usefulness, and I should either > remove it entirely, or make a sanity check against db_numag at the top, > which would avoid the oops. i have a lot runs of mkfs.jfs in front of me, i'll if i can trigger the oops again and let you know. thanks, Christian. -- make bzImage, not war ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
