Found my initial problem, my network interface that was being used for lustre communication (myrinet) didn't come up after the kernel upgrade this time. I resolved that, rebuilt everything from scratch, and have have an upgraded lustre 1.6.4.3 running on my MGS and OSS nodes. However, I'm getting this message on the MGS when I converted my last oss node:
Sep 24 19:44:34 mymds kernel: Lustre: upgrading server lustre-OST0001 from pre-1.6 Sep 24 19:44:34 mymds kernel: LustreError: 14c-9: lustre-client is supposedly an old log, but no old LOV or MDT was found. Consider updating the configuration with --writeconf. Sep 24 19:44:34 mymds kernel: LustreError: 149-c: Failed to find lustre-OST0001 in the old client log. Apparently it is not part of this filesystem, or the old log is wrong. Sep 24 19:44:34 mymds kernel: Use 'writeconf' on the MDT to force log regeneration. Sep 24 19:44:39 mymds kernel: Lustre: upgrading server lustre-OST0003 from pre-1.6 Sep 24 19:44:39 mymds kernel: LustreError: 14c-9: lustre-client is supposedly an old log, but no old LOV or MDT was found. Consider updating the configuration with --writeconf. Sep 24 19:44:39 mymds kernel: LustreError: 149-c: Failed to find lustre-OST0003 in the old client log. Apparently it is not part of this filesystem, or the old log is wrong. Sep 24 19:44:39 mymds kernel: Use 'writeconf' on the MDT to force log regeneration. I can't mount a lustre client yet so I assume this is directly related, any suggestions are welcomed. Thanks again, -Nathan On 9/24/08 10:06 AM, "Nathan" <[EMAIL PROTECTED]> wrote: Yes it is a symlink. I just now tried mounting the actual block device and am getting the same error unfortunately. Thanks for the suggestion though. -Nathan On 9/24/08 2:59 AM, "Andreas Dilger" <[EMAIL PROTECTED]> wrote: On Sep 23, 2008 17:55 -0400, Heald, Nathan T. wrote: > When I try to start it I get an error (Same error for an upgrade or fresh > install): > > [EMAIL PROTECTED] lustre]# mount -t lustre /dev/mpath/mpath2 /mnt/test/mdt > mount.lustre: mount /dev/mpath/mpath2 at /mnt/test/mdt failed: No such device > Are the lustre modules loaded? > Check /etc/modprobe.conf and /proc/filesystems > Note 'alias lustre llite' should be removed from modprobe.conf Is /dev/mpath/mpath2 a symlink to some real block device? That can cause problems in some cases. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss _______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
