[LU-8027] Ensure OSC OBD has been set up in onu_upcall() Created: 14/Apr/16 Updated: 01/Oct/16 Resolved: 12/May/16 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.9.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Yang Sheng | Assignee: | Yang Sheng |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Issue Links: |
|
||||
| Severity: | 3 | ||||
| Rank (Obsolete): | 9223372036854775807 | ||||
| Description |
|
The OBD may not setup successful while onu_upcall be invoked. So we have to check it in cl_ocd_update(). Since customer doing writeconf after this issue. So we have not possible to figure out why OBD was not setup. Below is original report from customer: Hello ,
MDT (ldiskfs, LSI 9286 syncro)
OST (openzfs 0.6.4.1-1, JBOD)
We add some HDDs to JBOD enclosure.
1. Update /etc/zfs/vdev_id.conf
2. Create zpool
3. Enable compression
4. mkfs.lustre (ost-24,ost-25)
5. export zpool
6. Add zfs and lustre mount resource to pacemaker
All operates are successful
A few minutes later,
7. MDT node reboot, I don 't know why.
8. Login MDT passive node , pcs show MDT mount fail
9. All lustre clients kernel panic(oh ,shit)
10. e2fsck mdt
11. writeconf mdt and osts
12. mount mgt mdt and osts
14. lustre client mount failed
15. remount mdt and osts, mdt mount failed
16. writeconf
17. mount ost-0, lustre client mount successful
18. umount ost-0
19. mount ost-24, lustre client mount failed
20. mdt could not remount
21. writeconf
22. exclude ost-24 and ost-25 , mount mdt and the other osts
23. mount mdt and osts
24. lustre client mount successful
|
| Comments |
| Comment by Gerrit Updater [ 15/Apr/16 ] |
|
Yang Sheng (yang.sheng@intel.com) uploaded a new patch: http://review.whamcloud.com/19597 |
| Comment by Gerrit Updater [ 11/May/16 ] |
|
Oleg Drokin (oleg.drokin@intel.com) merged in patch http://review.whamcloud.com/19597/ |
| Comment by Yang Sheng [ 12/May/16 ] |
|
Patch landed. Close ticket. |