It was set to /dev/md0. We got it fixed. For some reason the original fsck used the wrong journal. When we replayed against the previous journal all of the data came back.
I'd rather like to know why the wrong journal was used. On 3/31/06, Jure Pečar <[EMAIL PROTECTED]> wrote: > On Wed, 29 Mar 2006 07:36:50 -0700 > "Mike Garfias" <[EMAIL PROTECTED]> wrote: > > > We have two drives in a soft RAID-1 mirror w/hot spare. > > > > / is mounted on /md0 > > All other file systems are on md1 and attached via LVM. > > Was your kernel boot line in grub.conf properly setting root=/dev/md0? If > not, try to look to the other part of the mirror if your data are still there. > > -- > > Jure Pečar > http://jure.pecar.org/ > > > ------------------------------------------------------- > 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?cmdlnk&kid0944&bid$1720&dat1642 > _______________________________________________ > Jfs-discussion mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/jfs-discussion >
