Details
-
Bug
-
Resolution: Fixed
-
Minor
-
Lustre 1.8.6
-
various
-
3
-
7892
Description
Ever since we moved from Lustre 1.6.6 to 1.8 I've seen issues with using
the automounter and Lustre. I've finally got around to looking at what
the issue is, but I'm not quite sure what the correct way to resolve it
is. I think the issue will remain in 2.0+ but I didn't look closely at
the code. The issue is that lov_connect which calls lov_connect_obd is
an asynchronous connect that does not wait for all OSCs to be connected
before returning. In the end lustre_fill_super can return before all
OSCs have been set active so any file operations that caused the
automount may return an error. Many lov functions check to make sure
the lov_tgt_desc ltd_active flag is 1 or return -EIO.
Original email thread from lustre-devel:
http://groups.google.com/group/lustre-devel-list/browse_thread/thread/4796d88cadf9d0e9/248ebf6e3f9877f3?lnk=gst&q=automount#248ebf6e3f9877f3
Attachments
Issue Links
- Trackbacks
-
Lustre 1.8.x known issues tracker While testing against Lustre b18 branch, we would hit known bugs which were already reported in Lustre Bugzilla https://bugzilla.lustre.org/. In order to move away from relying on Bugzilla, we would create a JIRA