@novolunt @gengchun 我主要是搭建开发和测试环境，打算所有的数据库和中间件都用 k8s 来管理，不用于生产实践。bash 脚本是《深入理解 Kubernetes 》书中的，上面贴出来的 pvc 和 pv 的 description 中的 AccessModes 请忽略，改成 RWO 还是不行。

@lingly02 应该创建成功了的吧

```shell
[root@arch121 mysql]# kubectl get pvc -n lzipant
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
mysql-data-mysql-0 Bound pvc-ba6d4db6-4de3-4801-b700-f033c25c89af 5Gi RWX managed-nfs-storage 95s
[root@arch121 mysql]# kubectl get pv -n lzipant
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
pvc-ba6d4db6-4de3-4801-b700-f033c25c89af 5Gi RWX Delete Bound lzipant/mysql-data-mysql-0 managed-nfs-storage 100s
[root@arch121 mysql]# kubectl describe pvc mysql-data-mysql-0 -n lzipant
Name: mysql-data-mysql-0
Namespace: lzipant
StorageClass: managed-nfs-storage
Status: Bound
Volume: pvc-ba6d4db6-4de3-4801-b700-f033c25c89af
Labels: app=mysql
Annotations: pv.kubernetes.io/bind-completed: yes
pv.kubernetes.io/bound-by-controller: yes
volume.beta.kubernetes.io/storage-class: managed-nfs-storage
volume.beta.kubernetes.io/storage-provisioner: fuseim.pri/ifs
volume.kubernetes.io/storage-provisioner: fuseim.pri/ifs
Finalizers: [kubernetes.io/pvc-protection]
Capacity: 5Gi
Access Modes: RWX
VolumeMode: Filesystem
Used By: mysql-0
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal ExternalProvisioning 2m2s persistentvolume-controller waiting for a volume to be created, either by external provisioner "fuseim.pri/ifs" or manually created by system administrator
Normal Provisioning 2m fuseim.pri/ifs_nfs-client-provisioner-5868c55665-mbmdq_f2a0aea4-8bfc-4b4a-8eac-78ca5cfcf134 External provisioner is provisioning volume for claim "lzipant/mysql-data-mysql-0"
Normal ProvisioningSucceeded 2m fuseim.pri/ifs_nfs-client-provisioner-5868c55665-mbmdq_f2a0aea4-8bfc-4b4a-8eac-78ca5cfcf134 Successfully provisioned volume pvc-ba6d4db6-4de3-4801-b700-f033c25c89af
[root@arch121 mysql]# kubectl describe pv pvc-ba6d4db6-4de3-4801-b700-f033c25c89af -n lzipant
Name: pvc-ba6d4db6-4de3-4801-b700-f033c25c89af
Labels: <none>
Annotations: pv.kubernetes.io/provisioned-by: fuseim.pri/ifs
Finalizers: [kubernetes.io/pv-protection]
StorageClass: managed-nfs-storage
Status: Bound
Claim: lzipant/mysql-data-mysql-0
Reclaim Policy: Delete
Access Modes: RWX
VolumeMode: Filesystem
Capacity: 5Gi
Node Affinity: <none>
Message:
Source:
Type: NFS (an NFS mount that lasts the lifetime of a pod)
Server: arch121.com
Path: /mnt/nfs/lzipant-mysql-data-mysql-0-pvc-ba6d4db6-4de3-4801-b700-f033c25c89af
ReadOnly: false
Events: <none>

```

https://github.com/donnemartin/system-design-primer 重点关注系统设计吧

@tyzrj766 可能因为那玩意能够赚钱吧

@pengtdyd 厉害了大佬

@sinohsxzw 主要是考虑到接口不兼容，买 D4 的话，感觉过不了多久就过时了 :sob:

@chenmobuys 正在学啊，去年学完 32 位保护模式，今年学 64 位的

@lessMonologue tlpi 怎么样

@LeegoYih 确实也是

@1194129822 至少可以花更多的时间在这些上面

李忠的《 x86 从实模式到保护模式》，只学王爽的《汇编语言》是不够的