Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (techsharer at outlook.com)
홈페이지
첨부 파일
 
(연관된 글이 1개 있습니다.)

Hyper-V 서비스 시작 오류 - Not enough storage is available to complete this operation.

결론부터 말씀드리면 이 오류는 해결하지 못했습니다. 잘 되던 Hyper-V 서비스가 갑자기 다음과 같은 오류를 발생하며 "시작" 상태로 진입하지 못했습니다.

Windows could not start the Hyper-V Virtual Machine Management service on Local Computer.

Error 14: Not enough storage is available to complete this operation.

이벤트 로그에도 동일한 오류가 남을 뿐 그다지 별 도움이 되지 않았습니다.

Log Name:      System
Source:        Service Control Manager
Date:          2014-01-06 오전 9:20:01
Event ID:      7023
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      testpc.testad.com
Description:
The Hyper-V Virtual Machine Management service terminated with the following error: 
Not enough storage is available to complete this operation.

검색해 보니 다음의 글이 그나마 관련이 있었는데요.

The Hyper-V Virtual Machine Management service terminated with the following error: Not enough storage is available to complete this operation. 
; http://social.technet.microsoft.com/Forums/windows/en-US/c137fe1a-e34d-469a-9e98-2a2c2199ced2/the-hyperv-virtual-machine-management-service-terminated-with-the-following-error-not-enough?forum=w8itprovirt

제 경우에 실제로 다음과 같은 결과를 보였고 하드 디스크의 일부 데이터가 손실된 듯 합니다.

c:\>chkdsk /scan

Chkdsk was executed in scan mode on a volume snapshot.  

Checking file system on C:
The type of the file system is NTFS.

Stage 1: Examining basic file system structure ...
                                                                                       
                                                                                       
  266496 file records processed.                                                         File verification completed.
                                                                                       
                                                                                       
  1925 large file records processed.                                                                                                                           
                                                                                       
  0 bad file records processed.                                      
Stage 2: Examining file name linkage ...
Read failure with status 0xc000000d at offset 0x1364119000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\addons\APPXLOB-Server <0x1,0x2e227>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\addons\APPXLOB-Server <0x1,0x2e227>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136417a000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\legacy <0x1,0x2e229>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\legacy <0x1,0x2e229>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1364185000 for 0x1000 bytes.
    Found a bad index "$I30" in directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1452871000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x90 is invalid.
15 49 03 00 00 00 01 00 90 00 74 00 01 00 00 00  .I........t.....
2b e2 02 00 00 00 01 00 ea 83 56 70 34 9f ce 01  +.........Vp4...
ea 83 56 70 34 9f ce 01 77 b0 75 07 b4 af ce 01  ..Vp4...w.u.....
ea 83 56 70 34 9f ce 01 00 10 00 00 00 00 00 00  ..Vp4...........
70 0b 00 00 00 00 00 00 20 00 00 00 00 00 00 00  p....... .......
19 00 4c 00 53 00 41 00 2d 00 4c 00 69 00 63 00  ..L.S.A.-.L.i.c.
65 00 6e 00 73 00 65 00 2d 00 70 00 70 00 64 00  e.n.s.e.-.p.p.d.
6c 00 69 00 63 00 2e 00 78 00 72 00 6d 00 2d 00  l.i.c...x.r.m.-.
6d 00 73 00 00 00 00 00 ff ff ff ff ff ff ff ff  m.s.............
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\ppdlic <0x1,0x2e22b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136418b000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\skus\csvlk-pack <0x1,0x2e22e>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\skus\csvlk-pack <0x1,0x2e22e>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136419d000 for 0x1000 bytes.
    Found a bad index "$I30" in directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13641a0000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
The down pointer of current index entry with length 0xa8 is invalid.
45 49 03 00 00 00 01 00 a8 00 8c 00 01 00 00 00  EI..............
2f e2 02 00 00 00 01 00 0b 5a 5b e6 51 9f ce 01  /........Z[.Q...
0b 5a 5b e6 51 9f ce 01 f1 94 a1 07 b4 af ce 01  .Z[.Q...........
0b 5a 5b e6 51 9f ce 01 00 30 00 00 00 00 00 00  .Z[.Q....0......
5f 2a 00 00 00 00 00 00 20 00 00 00 00 00 00 00  _*...... .......
25 00 53 00 65 00 72 00 76 00 65 00 72 00 53 00  %.S.e.r.v.e.r.S.
74 00 61 00 6e 00 64 00 61 00 72 00 64 00 2d 00  t.a.n.d.a.r.d.-.
52 00 65 00 74 00 61 00 69 00 6c 00 2d 00 31 00  R.e.t.a.i.l.-.1.
2d 00 70 00 6c 00 2d 00 72 00 74 00 6d 00 2e 00  -.p.l.-.r.t.m...
78 00 72 00 6d 00 2d 00 6d 00 73 00 00 00 00 00  x.r.m.-.m.s.....
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\spp\tokens\skus\ServerStandard <0x1,0x2e22f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1364206000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sr-Latn-CS <0x1,0x2e231>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sr-Latn-CS <0x1,0x2e231>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136427c000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sr-Latn-RS <0x1,0x2e232>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sr-Latn-RS <0x1,0x2e232>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1452d7b000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\sv-SE <0x1,0x2e233>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\sv-SE <0x1,0x2e233>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1b03e000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\Sysprep <0x1,0x2e234>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Sysprep <0x1,0x2e234>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1360683000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Active Directory Rights Management Services Client <0x1,0x2e23b>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Active Directory Rights Management Services Client <0x1,0x2e23b>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x690d0000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\CertificateServicesClient <0x1,0x2e241>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\CertificateServicesClient <0x1,0x2e241>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f982000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Customer Experience Improvement Program <0x1,0x2e243>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Customer Experience Improvement Program <0x1,0x2e243>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0xbb45c7000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Data Integrity Scan <0x1,0x2e245>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Data Integrity Scan <0x1,0x2e245>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f98e000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\Plug and Play <0x1,0x2e252>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\Plug and Play <0x1,0x2e252>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x142f996000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform <0x1,0x2e25c>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform <0x1,0x2e25c>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13a6c52000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\Tasks\Microsoft\Windows\WS <0x1,0x2e26f>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\Tasks\Microsoft\Windows\WS <0x1,0x2e26f>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453603000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\th-TH <0x1,0x2e270>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\th-TH <0x1,0x2e270>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453605000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\tr-TR <0x1,0x2e271>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\tr-TR <0x1,0x2e271>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1453607000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\uk-UA <0x1,0x2e272>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\uk-UA <0x1,0x2e272>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x13643d8000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wbem <0x1,0x2e273>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem <0x1,0x2e273>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x136719d000 for 0x1000 bytes.
                                                                                       
    Found corruption in index "$I30" of directory "\Windows\System32\wbem\en-US <0x1,0x2e275>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem\en-US <0x1,0x2e275>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x14311e2000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wbem\Repository <0x1,0x2e27a>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wbem\Repository <0x1,0x2e27a>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0xbb0b06000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Windows\System32\wdi\LogFiles <0x1,0x2e27e>"
        ... queued for offline repair.
The down pointer of current index entry with length 0x18 is invalid.
00 00 00 00 00 00 00 00 18 00 00 00 03 00 00 00  ................
ff ff ff ff ff ff ff ff ?? ?? ?? ?? ?? ?? ?? ??  ................
    Found a mis-ordered index "$I30" from directory "\Windows\System32\wdi\LogFiles <0x1,0x2e27e>"
        ... queued for offline repair.
Read failure with status 0xc000000d at offset 0x1455a56000 for 0x1000 bytes.
    Found corruption in index "$I30" of directory "\Win

하단에 "wbem" 관련 폴더도 눈에 띄는데요. WMI 관련 서비스에 의존하는 WindowSMART 프로그램을 실행하니 다음과 같은 오류 메시지만 출력할 뿐이었습니다.

WMI Failure Predicted: False
The Microsoft storage driver is reporting False over WMI for the flag "failure predicted." The storage driver is not detecting any problems.

윈도우 백업 서비스를 이용해 시스템 전체 백업이 되어 있었지만 지난 백업 날짜로 C 드라이브를 통째로 돌려도 마찬가지 문제가 발생했습니다. 가정을 해보자면, 지난번 부팅 이후로 파일 시스템이 깨진 곳이 있었고 백업도 그것을 포함해서 된 것 같습니다. (백업 하드 용량이 작은 관계로 백업이 2개 정도만 보관된 것도 문제였고. ^^;) 그러다가 이번에 재부팅이 되면서 wbem 관련 문제가 발생해 Hyper-V 서비스가 시작하지 못하게 된 것입니다.

어쩔 수 없이! Hyper-V 호스트 운영체제만 새로 설치를 하는 것으로 문제를 우회했습니다. (역시 VM으로 서비스들을 뽑아놓으니 복구가 빠르게 되는군요. ^^;) 해결책 찾는 것보다 새로 설치하는 것이 더 빨랐습니다.




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]

[연관 글]






[최초 등록일: ]
[최종 수정일: 6/27/2021]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer at outlook.com

비밀번호

댓글 작성자
 




... 46  47  48  49  50  51  52  53  54  55  56  [57]  58  59  60  ...
NoWriterDateCnt.TitleFile(s)
12546정성태3/3/202118476개발 환경 구성: 545. github workflow/actions에서 빌드시 snk 파일 다루는 방법 - Encrypted secrets
12545정성태3/2/202121235.NET Framework: 1026. 닷넷 5에 추가된 POH (Pinned Object Heap) [10]
12544정성태2/26/202121597.NET Framework: 1025. C# - Control의 Invalidate, Update, Refresh 차이점 [2]
12543정성태2/26/202119266VS.NET IDE: 158. C# - 디자인 타임(design-time)과 런타임(runtime)의 코드 실행 구분
12542정성태2/20/202120913개발 환경 구성: 544. github repo의 Release 활성화 및 Actions를 이용한 자동화 방법 [1]
12541정성태2/18/202118444개발 환경 구성: 543. 애저듣보잡 - Github Workflow/Actions 소개
12540정성태2/17/202119882.NET Framework: 1024. C# - Win32 API에 대한 P/Invoke를 대신하는 Microsoft.Windows.CsWin32 패키지
12539정성태2/16/202119673Windows: 189. WM_TIMER의 동작 방식 개요파일 다운로드1
12538정성태2/15/202120230.NET Framework: 1023. C# - GC 힙이 아닌 Native 힙에 인스턴스 생성 - 0SuperComicLib.LowLevel 라이브러리 소개 [2]
12537정성태2/11/202120278.NET Framework: 1022. UI 요소의 접근은 반드시 그 UI를 만든 스레드에서! - 두 번째 이야기 [2]
12536정성태2/9/202119380개발 환경 구성: 542. BDP(Bandwidth-delay product)와 TCP Receive Window
12535정성태2/9/202118462개발 환경 구성: 541. Wireshark로 확인하는 LSO(Large Send Offload), RSC(Receive Segment Coalescing) 옵션
12534정성태2/8/202119193개발 환경 구성: 540. Wireshark + C/C++로 확인하는 TCP 연결에서의 closesocket 동작 [1]파일 다운로드1
12533정성태2/8/202117680개발 환경 구성: 539. Wireshark + C/C++로 확인하는 TCP 연결에서의 shutdown 동작파일 다운로드1
12532정성태2/6/202119476개발 환경 구성: 538. Wireshark + C#으로 확인하는 ReceiveBufferSize(SO_RCVBUF), SendBufferSize(SO_SNDBUF) [3]
12531정성태2/5/202117982개발 환경 구성: 537. Wireshark + C#으로 확인하는 PSH flag와 Nagle 알고리듬파일 다운로드1
12530정성태2/4/202121414개발 환경 구성: 536. Wireshark + C#으로 확인하는 TCP 통신의 Receive Window
12529정성태2/4/202119921개발 환경 구성: 535. Wireshark + C#으로 확인하는 TCP 통신의 MIN RTO [1]
12528정성태2/1/202119706개발 환경 구성: 534. Wireshark + C#으로 확인하는 TCP 통신의 MSS(Maximum Segment Size) - 윈도우 환경
12527정성태2/1/202119698개발 환경 구성: 533. Wireshark + C#으로 확인하는 TCP 통신의 MSS(Maximum Segment Size) - 리눅스 환경파일 다운로드1
12526정성태2/1/202116425개발 환경 구성: 532. Azure Devops의 파이프라인 빌드 시 snk 파일 다루는 방법 - Secure file
12525정성태2/1/202115288개발 환경 구성: 531. Azure Devops - 파이프라인 실행 시 빌드 이벤트를 생략하는 방법
12524정성태1/31/202115819개발 환경 구성: 530. 기존 github 프로젝트를 Azure Devops의 빌드 Pipeline에 연결하는 방법 [1]
12523정성태1/31/202117693개발 환경 구성: 529. 기존 github 프로젝트를 Azure Devops의 Board에 연결하는 방법
12522정성태1/31/202119907개발 환경 구성: 528. 오라클 클라우드의 리눅스 VM - 9000 MTU Jumbo Frame 테스트
12521정성태1/31/202118204개발 환경 구성: 527. 이더넷(Ethernet) 환경의 TCP 통신에서 MSS(Maximum Segment Size) 확인 [1]
... 46  47  48  49  50  51  52  53  54  55  56  [57]  58  59  60  ...