Please don't reply to lustre-devel. Instead, comment in Bugzilla by using the
following link:
https://bugzilla.lustre.org/show_bug.cgi?id=10734
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
(In reply to comment #13)
> > Eric, is there any more work you want to do here before we land this?
>
> I'm not familiar with 1.6 teardown / module unload procedures. Does that need
> to take account of possible delays and if so, does it?
umount waits for the last disk reference to drop before returning, but isn't
particularly concerned that all obds stop. As long as all obd's eventually do
stop (the mgc in this case), I don't have a problem with it. It will prevent
immediate re-startup (probably EALREADY), but since it's trying to talk to a
non-responding node anyhow, I don't think this will cause anyone pain.
> Apart from that issue, I'm happy this can land.
Landed on b1_5
_______________________________________________
Lustre-devel mailing list
[email protected]
https://mail.clusterfs.com/mailman/listinfo/lustre-devel
