@fitme

root@develop:/mnt/0# lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
nvme0n1
nvme1n1
├─nvme1n1p1 LVM2_member LVM2 001 We699H-iVEw-Hbkc-weAS-rovx-iX3U-xI9I5f
│ ├─vg-f40_root ext4 1.0 36df5d97-0c81-415e-baf0-88bde742f7bb 10.1G 30% /
│ └─vg-home ext4 1.0 e189760f-5df8-4ccc-9bfb-0a6c28628e9b 27.8G 22% /home
├─nvme1n1p2 vfat FAT16 4B64-9175 24.5M 51% /boot/efi
├─nvme1n1p3 ext4 1.0 4b7258eb-9478-4f7e-bf52-d83fdcf31147 653.2M 24% /boot
├─nvme1n1p4 ext4 1.0 86dbca85-a16b-46c4-9099-9c3fcac2e8c2
└─nvme1n1p5 LVM2_member LVM2 001 PCUuVc-rqiA-f7Wd-Qg0f-sfeJ-DC1R-SlspPV
└─fedora-root ext4 1.0 6ac9d777-70da-4ea2-8873-a00644e50934 11.4G 33% /mnt/0
root@develop:/mnt/0#
root@develop:/mnt/0# df .
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/fedora-root ext4 19G 6.2G 12G 35% /mnt/0
root@develop:/mnt/0#
root@develop:/mnt/0# date > test
root@develop:/mnt/0#
root@develop:/mnt/0# cat test
Mon Jun 24 12:21:53 PM CST 2024
root@develop:/mnt/0#

可以写入数据

@fitme

root@develop:~# ls -l /dev/disk/by-uuid/
total 0
lrwxrwxrwx 1 root root 10 Jun 24 2024 36df5d97-0c81-415e-baf0-88bde742f7bb -> ../../dm-1
lrwxrwxrwx 1 root root 15 Jun 24 10:16 4B64-9175 -> ../../nvme1n1p2
lrwxrwxrwx 1 root root 15 Jun 24 10:16 4b7258eb-9478-4f7e-bf52-d83fdcf31147 -> ../../nvme1n1p3
lrwxrwxrwx 1 root root 10 Jun 24 2024 6ac9d777-70da-4ea2-8873-a00644e50934 -> ../../dm-0
lrwxrwxrwx 1 root root 15 Jun 24 10:16 86dbca85-a16b-46c4-9099-9c3fcac2e8c2 -> ../../nvme1n1p4
lrwxrwxrwx 1 root root 10 Jun 24 2024 e189760f-5df8-4ccc-9bfb-0a6c28628e9b -> ../../dm-2
root@develop:~#


lvm 的 pv 本来就不能用 /dev/disk/by-uuid/ 这种方式看到 uuid 吧？

正常的卷组所在的 pv 用 /dev/disk/by-uuid/ 这种方式也看不到

@fitme fedora 卷组只有一个物理卷，是在 /dev/nvme1n1p5 这个分区上，如下：

root@develop:/home/d#
root@develop:/home/d# gdisk -l /dev/nvme1n1
GPT fdisk (gdisk) version 1.0.10

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/nvme1n1: 976773168 sectors, 465.8 GiB
Model: WD_BLACK SN770 500GB
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): C429264E-34FC-4E49-8B10-9120D21303DC
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 932732927 444.8 GiB 8E00
2 974675968 974778367 50.0 MiB EF00 EFI System Partition
3 974778368 976773119 974.0 MiB 8300
4 932732928 934830079 1024.0 MiB EA00
5 934830080 974675967 19.0 GiB 8E00
root@develop:/home/d#
root@develop:/home/d# mount /dev/nvme1n1p5 /mnt/0/
mount: /mnt/0: unknown filesystem type 'LVM2_member'.
dmesg(1) may have more information after failed mount system call.
root@develop:/home/d#

@fitme

root@develop:/home/d# pvs
PV VG Fmt Attr PSize PFree
/dev/nvme1n1p1 vg lvm2 a-- <444.76g <388.76g
root@develop:/home/d#

@blackeeper

root@develop:/home/d# vgscan
Found volume group "vg" using metadata type lvm2
root@develop:/home/d#

不管用

@julyclyde 我在输入的时候确实应该多注意一下，今天本来想删除 /home 下的一个目录，结果不小心把整个 /home 给删掉了，花了一下午时间来恢复。。。

@wniming #14 你们如果有在用这个的话下次我也尝试用用。

@iBugOne 听你推荐 sd-nd ，刚才我照着 arch 的教程把网桥配置起来了，感觉 sd-nd 配置不算很复杂，想问一下 systemd-resolved 这个你们有在用吗？我很早之前被这个坑过（具体什么问题忘了）所以一直都觉得这个是个很垃圾的玩意，每次新装系统都要先干掉这个， 你们如果有在有这个的话下次我也尝试用用。

@julyclyde 我确实需要用 gmail ，原因不方便说，我标题没有把 smtp 打错，描述里打了 2 次 smtp ，打了 1 次 smpt ，显然那一次是笔误，最后我想问一下你今年几岁？看你说话好像小孩子 ，还 “幸亏 V2EX 不允许修改原始内容”，真是笑到我了

@julyclyde #11

1 ，我描述是不是很清楚，但 2 楼的老哥能看懂并且解决了我的问题
2 ，我没有对我猜测的原因丝毫不怀疑，1 楼老哥指出了其他可能性后，我立刻就觉得他说的可能性更大，随后我才在 jms 的服务器条款里找到了确实是 1 楼老哥说的原因。
3 ，请问 smtp 四个字哪里写错了？

最后，请问你回复的目的是什么？

@ho121 在 fedora 39 上用 journalctl -f -u NetworkManager 查看 nmcli up 后的日志输出是下面这样子的，而 fedora 40 的日志输出会少很多，没有任何包含 enp1s0 的输出，如果你那里正常的话，能把这个输出贴出来看一下吗？


Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5629] agent-manager: agent[31c1f356d9e3a4c0,:1.90/nmtui/0]: agent registered
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5640] device (eth-br): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5644] device (eth-br): state change: unavailable -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5645] device (eth-br): Activation: starting connection 'eth-br' (1bf47946-d465-465e-87b6-70b5f1e568ff)
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5646] audit: op="connection-activate" uuid="1bf47946-d465-465e-87b6-70b5f1e568ff" name="eth-br" pid=2170 uid=0 result="success"
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5646] device (eth-br): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5646] manager: NetworkManager state is now CONNECTING
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5650] device (eth-br): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5651] policy: auto-activating connection 'eth' (7bb978ea-9354-4f02-be7a-d27b7bcedae7)
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5652] device (enp1s0): Activation: starting connection 'eth' (7bb978ea-9354-4f02-be7a-d27b7bcedae7)
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5652] device (enp1s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5652] device (enp1s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5752] device (eth-br): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5837] device (enp1s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5866] device (eth-br): attached bridge port enp1s0
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5866] device (enp1s0): Activation: connection 'eth' enslaved, continuing activation
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5868] device (eth-br): carrier: link connected
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5870] dhcp4 (eth-br): activation: beginning transaction (timeout in 45 seconds)
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5873] device (enp1s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5879] device (enp1s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5880] device (enp1s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.5884] device (enp1s0): Activation: successful, device activated.
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6335] dhcp4 (eth-br): state changed new lease, address=192.168.1.104
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6337] policy: set 'eth-br' (eth-br) as default for IPv4 routing and DNS
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6501] device (eth-br): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6515] device (eth-br): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6515] device (eth-br): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6518] manager: NetworkManager state is now CONNECTED_SITE
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6521] device (eth-br): Activation: successful, device activated.
Jun 22 19:34:36 fedora NetworkManager[586]: <info> [1719056076.6522] manager: NetworkManager state is now CONNECTED_GLOBAL

@ho121 插拔网卡后等待网络恢复要 1 分钟吗？这个感觉也不正常，如果 fedora 40 之前用 nmcli down 掉再 up ，一瞬间网络就会恢复的

@ho121 如果你那里正常的话，把 ip a 的输出贴出来看一下

@ho121 #7

nmcli con down eth-br
nmcli con up eth-br

这样试试

我之前都是用 nmtui 操作的，但 nmcli 和 nmtui 结果应该一样

@ho121 我 3 台 x86 机器和 3 台 arm64 机器都有这个问题，虚拟机里也一样，用 NetworkManager 配置好后，每次系统启动后 eth0 能正常 master 一次，但如果用 nmcli down 掉 eth-br 再 up ，eth0 就没有 master

@passive 没了解过 systemd-networkd ，但是不是很想用，上次看这个帖子： https://global.v2ex.com/t/1047924

中科大镜像管理员说他们镜像服务挂掉就是 systemd-networkd 的问题导致的

@passive 你也是遇到同样的问题了吗？

@bestsanmao JMS 的服务条款确实写了：

https://justmysocks3.net/members/index.php?rp=/knowledgebase/1/Terms-of-Service.html

Please note that outgoing mail port (SMTP) is blocked on our network, with the exception of Google Mail servers.

@jinqzzz 我试了

d@home:/r/d/source/kvmtool$ curl -v --head https://smtp.gmail.com:465
* Host smtp.gmail.com:465 was resolved.
* IPv6: (none)
* IPv4: 108.177.125.109
* Trying 108.177.125.109:465...
^C
d@home:/r/d/source/kvmtool$


和

d@home:/r/d/source/kvmtool$ telnet smtp.gmail.com 587
Trying 74.125.204.108...
^C
d@home:/r/d/source/kvmtool$


都是不通的，端口都不通，为啥 git send-email 可以呢？