What does "locked for Shared Use" mean, exactly?

Zheng, It would be more helpful if you could at least suggest other resources where this question might be answered.  It is rather frustrating to receive no assistance at all, when the question is quite clear and is obviously affecting a significant number of people. 

At a minimum, perhaps you could include a links to forums that *might* have an answer?  Or perhaps even do a quick search yourself and post a link to an answer or a quick statement like "I could not find anything in our forums, so I've created a new question for you.  Here is the link..."

Please allow me to paraphrase for Microsoft...since they can't say it. 

Dear O365 User, 

If you cannot already tell by our responses, we don't care about your feedback, or about your work files. If you cannot access your OneDrive files through the Office 365 account that you or your organization pay for, that's your own fault. Before you ask anything, are you on a Mac? If so, just expect us to blame everything on that.

Please re-read the generic responses we posted back in 2007, and you will find that there are no helpful links or relatable information regarding your "widespread" issue. If you haven't quit after you were reprimanded for not completing work by your deadline because your files were locked by yourself, then we will ask you if this "answered your question" just to drive the point home. Besides, when you complain about OneDrive, you inadvertently become a perpetual marketing vehicle employed at zero cost, so what's wrong with that? Hm, seems not testing our products is a two-fold return on investment. Good luck! 

This thread has been resolved.

But please do repro this issue on your end and respond.  This is a very common issue with my users too.  There is not predictability.

It can happen to any file, not a specific file.

it can happen even with your own name on it. And you havent checked out the file.

I have tried to explitily check out, and it allows you to check out - which alone is counter-intuitive.

Clearing cache doesnt do anything.

So, as of now, there is no way to fix the error.

Hi, Tisky,

Checkout was not required on that site's library, and the person who was mentioned in the locked for shared use message didn't check anything out.

So that wasn't the cause of the problem.

Hi Tisky--thanks for the follow-up.

I just checked. We were able to move the file today without having done the above steps. 

Can you tell us why a file would spontaneously become "locked for shared use" in a library that doesn't doesn't require check-out, and when a team member didn't check the file out in the first place?

Thanks.