<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>If you changed the NID of the servers, you need to do writeconf to let MGS erase and regenerate the system configuration.<div>First you need to shutdown the system, do writeconf on all the targets(MDT/OST), then you can restart the system in the order of MGS, MDT, OST, client.</div><div>Make proper change in the lnet options in /etc/modprobe.conf to reflect your NID info.</div><div>If you change the NID of the MGS, additional work needs to be done to let your server targets correctly communicate with the MGS. But since you only changed the NID of the OSTs, you don't have to worry about this.</div><div><br><div><div>ÔÚ 2010-12-16£¬ÏÂÎç1:50£¬ Andrus, Brian Contractor дµÀ£º</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>
<div><font color="#000000" size="2" face="Arial">Hello,</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">In a pickle now..</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">I upgraded our lustre from 1.8.4 to 1.8.5.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">We have an LVM that contains the MDTs and OSTs and is accessible via SRP. That seems to work without issues.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">I did change IPs of the NID for 2 or our lustre filesystems.</font></div>
<div><font size="2" face="Arial">Made appropriate changes to each ost. One thing I did that I probably shouldn't have was doing a --writeconf on the OSTs. Now I see:</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">Flags: 0x142<br> (OST update writeconf )<br></font></div>
<div><font size="2" face="Arial">and I cannot mount them. I get:</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">mount.lustre: mount /dev/VG_lustre/scratch_ost1 at /mnt/lustre/scratch/ost1 failed: Function not implemented<br></font></div>
<div><font size="2" face="Arial">however I do seem to be able to mount the OSTs that I didn't do --writeconf on.</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">I see in syslog:<br>LustreError: 6182:0:(obd_mount.c:1097:server_start_targets()) Required registration failed for nscratch-OST0001: -38<br>LustreError: 6182:0:(obd_mount.c:1655:server_fill_super()) Unable to start targets: -38<br>LustreError: 6182:0:(obd_mount.c:1438:server_put_super()) no obd nscratch-OST0001<br>LustreError: 6182:0:(obd_mount.c:147:server_deregister_mount()) nscratch-OST0001 not registered<br>LustreError: 6182:0:(obd_mount.c:2050:lustre_fill_super()) Unable to mount (-38)<br></font></div>
<div><font size="2" face="Arial">Is there a way to clear the flags on an OST and get it to mount?</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial">Brian Andrus</font></div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial"></font> </div>
<div><font size="2" face="Arial"></font> </div></div>
_______________________________________________<br>Lustre-discuss mailing list<br><a href="mailto:Lustre-discuss@lists.lustre.org">Lustre-discuss@lists.lustre.org</a><br>http://lists.lustre.org/mailman/listinfo/lustre-discuss<br></blockquote></div><br></div></div></body></html>