当前位置: 首页 > news >正文

CentOS Stream 9扩展根分区

没有废话,直接上操作!

[root@server ~]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs 3.1G 9.1M 3.1G 1% /run /dev/mapper/cs-root 17G 4.5G 13G 27% / /dev/nvme0n1p1 960M 308M 653M 33% /boot tmpfs 1.6G 0 1.6G 0% /run/user/0 [root@server ~]# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sr0 11:0 1 10.8G 0 rom nvme0n1 259:0 0 20G 0 disk ├─nvme0n1p1 259:1 0 1G 0 part /boot └─nvme0n1p2 259:2 0 19G 0 part ├─cs-root 253:0 0 17G 0 lvm / └─cs-swap 253:1 0 2G 0 lvm [SWAP] nvme0n2 259:3 0 20G 0 disk [root@server ~]# fdisk -l Disk /dev/nvme0n1: 20 GiB, 21474836480 bytes, 41943040 sectors Disk model: VMware Virtual NVMe Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x3acf68eb Device Boot Start End Sectors Size Id Type /dev/nvme0n1p1 * 2048 2099199 2097152 1G 83 Linux /dev/nvme0n1p2 2099200 41943039 39843840 19G 8e Linux LVM Disk /dev/nvme0n2: 20 GiB, 21474836480 bytes, 41943040 sectors Disk model: VMware Virtual NVMe Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/cs-root: 17 GiB, 18249416704 bytes, 35643392 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/cs-swap: 2 GiB, 2147483648 bytes, 4194304 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes [root@server ~]# pvcreate /dev/nvme0n2 Physical volume "/dev/nvme0n2" successfully created. [root@server ~]# pvdisplay --- Physical volume --- PV Name /dev/nvme0n1p2 VG Name cs PV Size <19.00 GiB / not usable 3.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 4863 Free PE 0 Allocated PE 4863 PV UUID 5lM9n2-i1BV-icKL-sa2n-mqOt-JNdu-GiNz5N "/dev/nvme0n2" is a new physical volume of "20.00 GiB" --- NEW Physical volume --- PV Name /dev/nvme0n2 VG Name PV Size 20.00 GiB Allocatable NO PE Size 0 Total PE 0 Free PE 0 Allocated PE 0 PV UUID Eq2SH3-uck2-tJJ7-BEiU-rlR1-LT4L-6IKl3Z [root@server ~]# vgextend cs /dev/nvme0n2 Volume group "cs" successfully extended [root@server ~]# pvdisplay --- Physical volume --- PV Name /dev/nvme0n1p2 VG Name cs PV Size <19.00 GiB / not usable 3.00 MiB Allocatable yes (but full) PE Size 4.00 MiB Total PE 4863 Free PE 0 Allocated PE 4863 PV UUID 5lM9n2-i1BV-icKL-sa2n-mqOt-JNdu-GiNz5N --- Physical volume --- PV Name /dev/nvme0n2 VG Name cs PV Size 20.00 GiB / not usable 4.00 MiB Allocatable yes PE Size 4.00 MiB Total PE 5119 Free PE 5119 Allocated PE 0 PV UUID Eq2SH3-uck2-tJJ7-BEiU-rlR1-LT4L-6IKl3Z [root@server ~]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs 3.1G 9.1M 3.1G 1% /run /dev/mapper/cs-root 17G 4.5G 13G 27% / /dev/nvme0n1p1 960M 308M 653M 33% /boot tmpfs 1.6G 0 1.6G 0% /run/user/0 [root@server ~]# lvextend -l +100%free /dev/mapper/cs-root Size of logical volume cs/root changed from <17.00 GiB (4351 extents) to 36.99 GiB (9470 extents). Logical volume cs/root successfully resized. [root@server ~]# blkid /dev/mapper/cs-root /dev/mapper/cs-root: UUID="7891d05a-39a3-4cd4-adf5-12035d8ec669" TYPE="xfs" [root@server ~]# xfs_growfs /dev/mapper/cs-root meta-data=/dev/mapper/cs-root isize=512 agcount=4, agsize=1113856 blks = sectsz=512 attr=2, projid32bit=1 = crc=1 finobt=1, sparse=1, rmapbt=0 = reflink=1 bigtime=1 inobtcount=1 nrext64=0 data = bsize=4096 blocks=4455424, imaxpct=25 = sunit=0 swidth=0 blks naming =version 2 bsize=4096 ascii-ci=0, ftype=1 log =internal log bsize=4096 blocks=16384, version=2 = sectsz=512 sunit=0 blks, lazy-count=1 realtime =none extsz=4096 blocks=0, rtextents=0 data blocks changed from 4455424 to 9697280 [root@server ~]# df -h Filesystem Size Used Avail Use% Mounted on devtmpfs 4.0M 0 4.0M 0% /dev tmpfs 7.7G 0 7.7G 0% /dev/shm tmpfs 3.1G 9.1M 3.1G 1% /run /dev/mapper/cs-root 37G 4.6G 33G 13% / /dev/nvme0n1p1 960M 308M 653M 33% /boot tmpfs 1.6G 0 1.6G 0% /run/user/0 [root@server ~]#
http://www.jsqmd.com/news/635772/

相关文章:

  • MobaXterm远程开发伴侣:千问3.5-2B辅助服务器运维与命令调试
  • PvZ Toolkit:如何为植物大战僵尸PC版打造个性化游戏体验
  • 实战教程:用YOLOv12打造高精度交通标志识别桌面应用(附PySide6界面源码)
  • 2026蓝桥杯 Python A 购电优化(模拟+贪心 好题)
  • 鸿蒙HarmonyOS模块化开发实战:手把手教你使用HSP和HAR共享代码
  • 高中化学里面诱导力,色散力,取向力以及范德华力的区别联系
  • 2026.4.11 蓝桥杯软件类C/C++ G组山东省赛 小记
  • ESP32-S3单片机入门:点灯
  • AlienFX-Tools终极指南:释放Alienware设备的全部潜能
  • 轻量化文件批量重命名工具——太极重命名的设计理念与实践
  • BEAST 2 贝叶斯进化分析:从新手到专家的完整指南
  • 全网最细!OpenClaw 工具系统深度解析:从原子能力到企业级安全,AI 智能体的“万能手脚“完全指南
  • Autoware.universe实车部署实战:从传感器配置到调试全流程
  • 96.1亿元!数字体验编排(DXO)平台软件市场规模揭晓,数字化转型赛道迎新风口
  • VMPDump深度解析:动态VMP脱壳与导入表修复实战指南
  • 2026年宁夏舒心游国际旅行社有限公司官方联系方式公示,宁夏一手地接服务合作便捷入口 - 第三方测评
  • 太极重命名软件的功能架构与技术实现分析
  • 从Verilog到HLS:FPGA实现CNN的并行计算架构与设计权衡
  • Get笔记API + Python脚本:如何自动化处理2W+公众号文章,实现批量摘要与导出
  • 别再让机械臂乱动了!详解ROS2中Gazebo与MoveIt2的控制器配置与通信原理
  • Golang怎么写博客系统后端_Golang博客系统教程【进阶】
  • OpenClaw模型配置规则及说明
  • 2026年主轴维修厂家推荐榜单:高端主轴维修、CNC电主轴维修、加工中心电主轴维修、数控机床主轴维修、高速电主轴维修厂家选择指南 - 海棠依旧大
  • 01_TIM定时器用于周期任务(100us)
  • 告别Keil单调调试:用Ozone + J-Link可视化你的FreeRTOS任务状态(附工程配置避坑点)
  • 【软件架构四大范式】
  • C# NetTopologySuite+ProjNet 实现复杂几何图形坐标转换实战
  • 结构化表达:让你的周报、方案和总结脱颖而出
  • Claude Code 工作流工具怎么选?OpenSpec、GSD、Superpowers、Task Master、Backlog.md、Spec Kit 一次讲清
  • 扩散模型如何革新遥感?从HSIGene看高光谱图像生成的三大应用场景