[LU-4487] LFSCK 5: modify Lustre with backend mounted directly and keep system consistency Created: 15/Jan/14  Updated: 30/Jan/22

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: nasf (Inactive) Assignee: nasf (Inactive)
Resolution: Unresolved Votes: 0
Labels: None

Severity: 3
Rank (Obsolete): 12286

 Description   

There are some remaining issues for the following patch to be further discussed and resolved:

http://review.whamcloud.com/#/c/8002/

In fact, there are some rude usages for Lustre admin to modify Lustre with ldiskfs mounted directly, which may cause some stale OI mapping entries left in the OI files but related inodes have been removed. Sometimes, such modification are meaningful. For example: removing last_rcvd file to resolve some recovery trouble; removing OI files to increase OI files count for larger scale or shrink OI files unused space; and so on. On the other hand, such modification brings trouble to the system consistency. Currently, we use OI scrub to resolve those trouble as much as possible. But is seems not the best solution. Maybe we can introduce more suitable way to resolve the issues in the future. For example, we can offer a offline tools set to admin to modify Lustre files and related OI mappings together, then guarantee that even though the modification is done under ldiskfs mounted, the system is still is consistent.



 Comments   
Comment by nasf (Inactive) [ 29/Jan/15 ]

We will allow the admin to directly modify the ldiskfs backend under some special cases, and make the normal RPC services to remove the unused OI mappings during the OI lookup.

Generated at Sat Feb 10 01:43:09 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.