SVN "이미 잠긴 오류"

SVN "이미 잠긴 오류"

---

저장소 (내가 유일한 사용자 인 경우)에 변경 사항을 커밋하려고하면 오류가 발생합니다.

Path
'/trunk/TemplatesLibrary/constraints/templates/TP145210GB01_PersonWithOrganizationUniversal.cs'
is already locked by user 'admin' in filesystem
'/guest/gam/subversion/cdaapi/db'

나는 사용자 'admin'입니다.

나는 다음을 시도했지만 모두 성공하지 못했습니다.

• Tortoise SVN에서 "정리"실행
• 새 사본 체크 아웃

• "repo 브라우저"를 사용하여 잠금을 해제하지만 잠금이 표시 되지 않습니다 (내가 잠근 SVN 파일에 따라 이제 커밋 할 수 없음 )

  업데이트를 커밋 할 수없는 저장소가 있으므로 이제 완전히 멈춰 있습니다.

  이 문제를 해결하는 방법에 대한 아이디어

  요청에 따라 추가 정보 :

  SVN 상태 명령이 산출됩니다 (하나의 파일을 편집했습니다).

          92       77 admin        TP146228GB01_EncompassingEncounter.cs
          92       83 admin        TP145212GB02_WorkgroupUniversal.cs
          92       83 admin        TP146248GB01_ReferenceURL.cs
          92       85 admin        TP145201GB01_PatientUniversal.cs
          92       83 admin        TP145204GB02_RecipientWorkgroupUniversal.cs
          92       83 admin        TP145202GB01_RecipientPersonUniversal.cs
          92       83 admin        TP145203GB02_RecipientOrganizationUniversal.cs
          92       77 admin        TP145205GB01_PersonUniversal.cs
          92       83 admin        TP145202GB02_RecipientPersonUniversal.cs
          92       83 admin        TP145203GB03_RecipientOrganizationUniversal.cs
          92       85 admin        TP145211GB01_HealthCareFacilityUniversal.cs
          92       85 admin        TP145200GB01_AuthorPersonUniversal.cs
          92       83 admin        TP145207GB01_AuthorDeviceUniversal.cs
      M   92       87 admin        TP146226GB02_Consent.cs
          92       85 admin        TP146229GB01_TextSection.cs
          92       83 admin        TP145204GB03_RecipientWorkgroupUniversal.cs
          92       86 admin        TP145018UK03_CustodianOrganizationUniversal.cs
          92       83 admin        TP145208GB01_AuthorNonNamedPersonUniversal.cs
          92       70 admin        TP145214GB01_DocumentParticipantUniversal.cs
          92       85 admin        TP145007UK03_RelatedEntity.cs
          92       80 admin        TP146224GB02_Atachment.cs
          92       83 admin        TP146227GB02_ServiceEvent.cs
          92       77 admin        TP145210GB01_PersonWithOrganizationUniversal.cs
  

svn 커밋은 다음을 산출합니다.

svn commit --message updates
Sending        TP146226GB02_Consent.cs
Transmitting file data .svn: E195022: Commit failed (details follow):
svn: E195022: File    'D:\BENBUN_CODE\WORK\cdaapi\trunk\TemplatesLibrary\constraints\templates\TP146226GB02_Consent.cs' is locked in another working copy
svn: E170007: No lock on path '/subversion/cdaapi/!svn/wrk/3c75d861-8462-b94e-8729-df54843044f9/trunk/TemplatesLibrary/constraints/templates/TP146226GB02_Consent.cs' (Status 423 on PUT Request)
svn: E175002: Server sent unexpected return value (423 Locked) in response to PUT request for '/subversion/cdaapi/!svn/wrk/3c75d861-8462-b94e-8729-df54843044f9/trunk/TemplatesLibrary/constraints/templates/TP146226GB02_Consent.cs'  

요청 된 SVN st -u 출력은 아래와 같습니다.

>svn st -u
M               92   TP146226GB02_Consent.cs
Status against revision:     92              

---

당신의 SVN 저장소가 AnkhSVN에 의해 잠겨있는 경우, 단지에서 "정리"명령을 사용 AnkhSVN 잠금을 해제! ;)

---

나는 같은 문제가 있었다. 이 문제는 AnkhSVN에서 정리 명령을 실행하면 쉽게 해결됩니다.

---

내 SVN 저장소 호스팅에 대해 논의한 후 그들은 다음과 같은 답변을주었습니다.

분명히 내 저장소는 SVNSYNC를 사용하여 원격 저장소에 복제됩니다. SVNSYNC에는 복제 된 리포지토리에 잠금을 적용하는 데 알려진 제한 사항이 있으며 여기에 문제가 있습니다.

잠금은 Visual Studio의 AnkhSVN 플러그인에 의해 도입되었습니다.

잠금이 원격 저장소에있는 것처럼 보이기 때문에 SVN 명령을 사용하여 실제로 볼 수없는 이유를 설명합니다.

잠금 장치는 호스팅 회사를 통해 제거되고 있으며 곧 모든 것이 잘 될 것입니다.

---

I am not using AnkhSVN but got a similar problem after cancelling a Tortoise SVN update. It left two directories "already locked". Similar to Roman C's solution. Use Get lock to to lock one file in each directory that is "already locked" and then release those locks, then do a cleanup on the highest directory. That seemed to fix the problem.

---

Its even good to use tortoise svn cleanup, no need to use Ankh one in my case

---

I got similar error msgs. I run svn clean-up, and then tried "get clock" for a few times. Then this error was gone.

---

I had to do a Clean Up and elect to "Break Locks" for it to work for me.

---

These settings worked for me:

I was unable to update repository after the connection timeout, while I was checking out the repository.

---

I had the same problem: I can't commit a lot of files at once.

---

The commit works by:

1. Running a "clean up" from Tortoise SVN

2. Commit each file separate. Create new root folder and commit each file or folder.

---

** If the error returns you should repeat action no.1-2 **

---

TortoiseSVN users: right click on the root project directory > TortoiseSVN > Clean up... (make sure you check all the boxes). This worked for me.

---

You need to cleanup your tortoise SVN by clicking on cleanup option you get after Right Clicking on windows where you want to UPDATE SVN. And after cleanup try updating SVN similarly by clicking UPDATE SVN option you get after right clicking.

This worked for me.

---

Sometimes cleaning the repository with the "break locks"-option still doesn't work if the lock was created by another process. Possible Solution: 1) Acquire a new lock on the folder/file and choose the option "Steal the locks" 2) Release your new lock.

ReferenceURL : https://stackoverflow.com/questions/9779710/svn-already-locked-error