On Fri, 2006-03-31 at 20:25 -0700, Mike Garfias wrote: > Well, a bit of a misnomer. We pulled the "previous fsck.jfs service > log" and reran that.
The service log is not the same as the journal. The service log is a record of the output of fsck, which can be retrieved after the fact. > I used jfs_fscklog to pull the previous journal like so: > jfs_fscklog -p -e /dev/mapper/vg0-var -f /tmp/var-previous-journal > > then > > jfs_fsck -j /tmp/var-previous-journal /dev/mapper/vg0-var jfs_fsck probably ignored the -j flag. If the file system uses an internal journal (the default), jfs_fsck doesn't try to open an external journal, so var-previous-journal will be ignored. I can't explain why this fixed your problem. :-) -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
