主页 / user-237298

yael's questions

Martin Hope
yael
Asked: 2025-01-09 14:33:49 +0800 CST
  • 5

我有以下简单的脚本可以更改文件夹的所有权

more hola_config.sh

#!/bin/bash

chown -R hola:pola /home/darna
chmod -R 775  /home/darna

在 /etc/sudoers 中我添加了以下内容（super_hola 用户就像超级用户）

super_hola ALL=(ALL)       NOPASSWD:ALL

但是当我运行脚本时

su super_hola
whoami
super_hola

sudo -u super_hola ./hola_config.sh

我从脚本中得到“chmod 不允许操作”

例子：

chmod: changing permissions of ‘/home/darna/linux.cvg: Operation not permitted

问题是

为什么超级用户super_hola无法像 root 用户那样更改权限，以及我需要修复配置中的哪些部分才能让用户 super_hola 这样做

这里是用户和组 ID

id super_hola
uid=1001(super_hola) gid=1001(pola) groups=1001(pola),982(docker)

grep super_hola /etc/group
docker:x:982:super_hola

id -G super_hola
1001 982
linux
Martin Hope
yael
Asked: 2024-08-04 21:34:11 +0800 CST
  • 5

LVM2_member 可能因设备分区号不同而不同

例子

 lsblk -f | grep     LVM2_member   | awk '{print $1}'
└─sda3

或者在其他 redhat 机器上

 lsblk -f | grep  LVM2_member  | awk '{print $1}'
└─sda2

如何在没有“└─”行的情况下捕获 sdaX 设备，或者也许其他方法来捕获与 LVM2_member 相关的 OS 设备

查看lsblk -f

    lsblk -f
    NAME             FSTYPE      LABEL                  UUID                                   MOUNTPOINT
    sda
    ├─sda1           vfat                               E7D6-EC08                              /boot/efi
    ├─sda2           xfs                                1d74a8b2-9226-45cf-aa90-f9c9783a9a57   /boot
    └─sda3           LVM2_member                        eRpqzd-o7UM-ruPb-2xU3-QUAW-EswH-PzsSZE
      ├─VG00-lvv_root xfs                                e0cfac88-be2e-41e4-8163-da3ef0fcb98c   /
      ├─VG00-lvv_swap swap                               91341494-85f3-4300-9f66-68922c39418b   [SWAP]
      └─VG00-lvv_var  xfs                                92cc4e1a-23a4-40ac-ae5d-b0d884bfdeeb   /var
linux
Martin Hope
yael
Asked: 2024-04-19 00:24:53 +0800 CST
  • 3

我们有不同的 Linux 机器，每台 Linux 机器需要不同的分区大小

为了通过脚本扩展根文件系统或var文件系统，我们可以使用以下lvextend语法，变量为-PARTITION_VAL_SIZE

 PARTITION_VAL_SIZE=100
 lvextend -L"$PARTITION_VAL_SIZE"G /dev/vg-data/lv-var
 PARTITION_VAL_SIZE=30
 lvextend -L"$PARTITION_VAL_SIZE"G /dev/vg-data/lv-root
 .
 .
 PARTITION_VAL_SIZE=50
 lvextend -L"$PARTITION_VAL_SIZE"G /dev/vg-data/lv-var
 PARTITION_VAL_SIZE=20
 lvextend -L"$PARTITION_VAL_SIZE"G /dev/vg-data/lv-root

 .
 .

lvextend因为我们使用的是 GIGA 中的值，所以我们在命令上添加“G”

我们可以做得更好吗？或者我们的方法是否足以增加带有变量的 Linux 分区？

linux
Martin Hope
yael
Asked: 2024-01-05 16:37:23 +0800 CST
  • 5

几个月前，我们通过添加 VMDK sdi 磁盘来扩展根 XFS 文件系统分区大小（仅为 20G），并将根文件系统增加 +100G

[root@DB_OP_SERVER ~]# pvcreate /dev/sdi
  Physical volume "/dev/sdi" successfully created.


[root@DB_OP_SERVER ~]# vgextend VG_DB /dev/sdi
  Volume group "VG_DB" successfully extended


[root@DB_OP_SERVER ~]# lvresize --size +100g /dev/mapper/VG_DB-lv_root
  Size of logical volume VG_DB/lv_var changed from .... 
  Logical volume VG_DB/lv_var successfully resized.


[root@DB_OP_SERVER ~]#  xfs_growfs /root
meta-data=/dev/mapper/VG_DB-lv_var isize=512    agcount=7, agsize=6553600 blks
         =                       sectsz=512   attr=2, projid32bit=1
         =                       crc=1        finobt=0 spinodes=0
data     =                       bsize=4096   blocks=42729472, imaxpct=25
         =                       sunit=0      swidth=0 blks
naming   =version 2              bsize=4096   ascii-ci=0 ftype=1
log      =internal               bsize=4096   blocks=12800, version=2
         =                       sectsz=512   sunit=0 blks, lazy-count=1
realtime =none                   extsz=4096   blocks=0, rtextents=0
data blocks changed from 42729472 to 45350912

df -h /
Filesystem                Size  Used   Avail Use% Mounted on
/dev/mapper/VG_DB-lv_root 120G   110G   10G  93% /

现在我们想要将根文件系统增加+50G，以使根文件系统大小达到170G

所以我们更新VMDK磁盘（通过将vSphere客户端中的设置编辑为150G）

再次增加根文件系统需要哪些步骤？

linux
Martin Hope
yael
Asked: 2023-11-09 21:25:57 +0800 CST
  • 3

我想检查文件夹下/var/kafka所有文件夹都以数字结尾，否则我将错误退出

ls -ltr  /var/kafka
drwxr-xr-x 399 kafka kafka 28672 Nov  9 13:10 data6
drwxr-xr-x 392 kafka kafka 28672 Nov  9 13:10 data5
drwxr-xr-x 391 kafka kafka 28672 Nov  9 13:10 data1
drwxr-xr-x 405 kafka kafka 28672 Nov  9 13:10 data2
drwxr-xr-x 386 kafka kafka 28672 Nov  9 13:10 data4
drwxr-xr-x 389 kafka kafka 28672 Nov  9 13:10 data8
drwxr-xr-x 406 kafka kafka 28672 Nov  9 13:10 data7
drwxr-xr-x 397 kafka kafka 28672 Nov  9 13:10 data3

所以我创建了以下简单的代码（应该在 bash 脚本中）

for i in `  ls -ltr  /var/kafka | awk '{print $NF}' `; do  [[ ! $i  = *?[0-9] ]] && echo "ERROR folder/s not ended with number" && exit 1 ; done

但上面的例子代码太长，我想找到其他优雅的短命令来简单地验证下面的文件夹是否/var/kafka以数字结尾，

我们也可以使用awk/sed/或Perl在内衬上。

linux
Martin Hope
yael
Asked: 2023-11-02 02:47:12 +0800 CST
  • 5

我们的目标是为 Kafka 机器使用 200TB 的巨大存储空间

为了实现这个目标，我们在RAID10中使用LVM在4个物理磁盘上创建卷，每个磁盘大小为50T，

RAID10注意 -当每个 RAID10 拥有 12 个磁盘时，每个磁盘实际上是 sdb/sdc/sdd/sde

在我们的 kafka 服务器中，我们有 4 个磁盘（示例来自lsblk）

sdb                  8:16   0   50T  0 disk 
sdc                  8:32   0   50T  0 disk 
sdd                  8:48   0   50T  0 disk 
sde                  8:64   0   50T  0 disk

所以我们写了下面的程序：

我们将磁盘/dev/sdb和结合起来/dev/sdc。和/dev/sdd，/dev/sde将它们添加到同一卷组中。-DB_vg

vgcreate DB_vg /dev/sdb /dev/sdc /dev/sdd /dev/sde

我们创建逻辑卷（我们这里使用 200T 大小）

lvcreate -L200T -n DB_lv DB_vg

我们创建 XFS 文件系统

mkfs.ext4  -j -m 0  /dev/DB_vg/DB_lv -F

我们创建文件夹，以便将LV挂载到该文件夹

mkdir /var/lib/kafka_broker

mount /dev/DB_vg/DB_lv /var/lib/kafka_broker

从df -h，它应该看起来像这样（示例）

/dev/mapper/DB_vg-DB_lv  200T   61M  200T   1%  /var/lib/kafka_broker

从lsblk

sdb                   
└─DB_vg-DB_lv 253:4    
sdc                   
└─DB_vg-DB_lv 253:4   
sdd                  
└─DB_vg-DB_lv 253:4    
sde                  
└─DB_vg-DB_lv 253:4

从blkid

blkid | grep LVM2_member
/dev/sda2: UUID="Y5MbyB-C5NN-hcPA-wd9R-jmdI-02ML-W9qIiu" TYPE="LVM2_member"    <-- sda2 is the OS
/dev/sdc: UUID="mtg8CY-b3j9-K1qZ-CRTV-SZum-gDx3-lbm4ZX" TYPE="LVM2_member"
/dev/sdb: UUID="MvfzqO-PV8N-dror-psl4-PfUf-7coa-6cb8lQ" TYPE="LVM2_member"
/dev/sdd: UUID="C4n63l-Uk3E-D65G-WcgI-xic2-cJLi-eSTUAa" TYPE="LVM2_member"
/dev/sde: UUID="d743Xp-eDxr-Dygk-HGgy-Dh9c-K3cx-kHtyqo" TYPE="LVM2_member"

现在我们可以使用/dev/mapper/DB_vg-DB_lv挂载到的 LV/var/lib/kafka_broker folder

我们可以使用该文件夹 /var/lib/kafka_broker作为kafka代理机200T的存储

我的问题是：

  1. 安全吗？使用 LVM 使用 4 个巨大磁盘创建的巨大存储空间？

  2. 当存储大小在200T左右时，我们可以创建XFS文件系统吗？

  3. 我对我的程序是否正确，或者我可能遗漏了什么？

linux
Martin Hope
yael
Asked: 2023-10-27 19:37:36 +0800 CST
  • 7

/etc/fstab我们的目标是创建 bash 脚本，从文件中删除未使用/不必要的 UUID 编号，

简要背景- 在我们的实验室中，我们有超过 500 台 RHEL 服务器，我们希望修复配置fstab不正确的文件，fstab如未使用的 UUID 编号或注释行中未使用的 UUID 编号等

我们创建以下 bash 脚本作为示例。

#!/bin/bash


blkid_list_of_uuid=` blkid | awk -F'UUID=' '{print $2}' | awk '{print $1}' | sed s'/"/ /g' `
grep UUID /etc/fstab >/tmp/fstab

while read line_from_fstab
do
        echo "checking if ${line_from_fstab} is unused UUID"
        if [[ ! ${line_from_fstab} =~ $blkid_list_of_uuid ]]
        then
           #sed -i "/$line_from_fstab/d" /etc/fstab
           echo "delete unused line ${line_from_fstab} from fstab"
        fi
done < /tmp/fstab

我们捕获了变量blkid中的数字blkid_list_of_uuid。并将 fstab 中的 UUID 行过滤到/tmp/fstab文件中

if 语法的目标 -[[ ! ${line_from_fstab} =~ $blkid_list_of_uuid ]] 是通过 sed 删除（现在在注释中）其中/etc/fstab未使用的UUID 行

但正则表达式不起作用，脚本实际上删除了正在使用的 UUID

blkid 的示例

blkid
/dev/mapper/vg-VOL_root: UUID="49232c87-6c49-411d-b744-c6c847cfd8ec" TYPE="xfs"
/dev/sda2: UUID="Y5MbyB-C5NN-hcPA-wd9R-jmdI-02ML-W9qIiu" TYPE="LVM2_member"
/dev/sda1: UUID="0d5c6164-bb9b-43f4-aa9b-092069801a1b" TYPE="xfs"
/dev/mapper/vg-VOL_swap: UUID="81140364-4b8e-412c-b909-ef0432162a45" TYPE="swap"
/dev/mapper/vg-VOL_var: UUID="e1574eeb-5a78-4a52-b7e3-c53e2b8a4220" TYPE="xfs"
/dev/sdb: UUID="547977e2-a899-4a75-a31c-e362195c264c" TYPE="ext4"
/dev/mapper/vg-VOL_docker: UUID="2e1a2cbf-9920-4e54-8b6b-86d0482c5f7b" TYPE="xfs"
/dev/sdc: UUID="1a289232-0cfe-4df7-9ad5-6a6e2362a1c5" TYPE="ext4"
/dev/sdd: UUID="91493d1f-ffe9-4f5f-aa6d-586d2c99f029" TYPE="ext4"
/dev/sde: UUID="f11845e7-1dcb-4b81-a1d4-9a5fe7da6240" TYPE="ext4"
bash
Martin Hope
yael
Asked: 2023-09-11 12:30:24 +0800 CST
  • 5

CPU IDLE 低可能由多种因素引起，包括： RAM 不足或硬盘驱动器速度慢

但在我们的 RHEL 服务器 RAM 内存中有足够的 RAM，但从 dmesg 中我们发现了几个有关磁盘驱动器的错误

我们的怀疑与磁盘有关，例如 sdk 和 sdc，因为我们从 dmesg 错误中看到：[sdk] tag#0 Add. Sense: Unrecovered read error

sar这里是显示 CPU IDLE 值的命令的详细信息

    09:43:56 AM     CPU     %user     %nice   %system   %iowait    %steal     %idle
    09:44:01 AM     all     98.57      0.00      0.62      0.00      0.00      0.80
    09:44:06 AM     all     98.26      0.00      0.92      0.01      0.00      0.81
    09:44:11 AM     all     97.29      0.00      1.66      0.01      0.00      1.03
    09:44:16 AM     all     92.81      0.00      6.06      0.03      0.00      1.10
    09:44:21 AM     all     92.31      0.00      6.43      0.05      0.00      1.21
    Average:        all     95.85      0.00      3.14      0.02      0.00      0.99


09:44:21 AM     CPU     %user     %nice   %system   %iowait    %steal     %idle
09:44:22 AM     all     96.52      0.00      3.10      0.00      0.00      0.38
09:44:22 AM       0     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM       1     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM       2    100.00      0.00      0.00      0.00      0.00      0.00
09:44:22 AM       3     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM       4     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM       5     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM       6     97.98      0.00      2.02      0.00      0.00      0.00
09:44:22 AM       7     97.98      0.00      2.02      0.00      0.00      0.00
09:44:22 AM       8     98.99      0.00      1.01      0.00      0.00      0.00
09:44:22 AM       9     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM      10     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM      11     98.02      0.00      0.99      0.00      0.00      0.99
09:44:22 AM      12     97.00      0.00      1.00      0.00      0.00      2.00
09:44:22 AM      13     96.97      0.00      3.03      0.00      0.00      0.00
09:44:22 AM      14     98.02      0.00      0.99      0.00      0.00      0.99
09:44:22 AM      15     94.00      0.00      6.00      0.00      0.00      0.00
09:44:22 AM      16     83.00      0.00     16.00      0.00      0.00      1.00
09:44:22 AM      17     98.00      0.00      1.00      0.00      0.00      1.00
09:44:22 AM      18     96.97      0.00      2.02      0.00      0.00      1.01
09:44:22 AM      19     96.00      0.00      4.00      0.00      0.00      0.00
09:44:22 AM      20     97.98      0.00      1.01      0.00      0.00      1.01
09:44:22 AM      21     95.05      0.00      4.95      0.00      0.00      0.00
09:44:22 AM      22     94.95      0.00      5.05      0.00      0.00      0.00
09:44:22 AM      23     98.99      0.00      1.01      0.00      0.00      0.00
09:44:22 AM      24     98.99      0.00      1.01      0.00      0.00      0.00
09:44:22 AM      25     99.00      0.00      1.00      0.00      0.00      0.00
09:44:22 AM      26     98.99      0.00      1.01      0.00      0.00      0.00
09:44:22 AM      27     98.99      0.00      1.01      0.00      0.00      0.00
09:44:22 AM      28     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM      29     98.00      0.00      2.00      0.00      0.00      0.00
09:44:22 AM      30     94.95      0.00      5.05      0.00      0.00      0.00
09:44:22 AM      31     97.03      0.00      1.98      0.00      0.00      0.99
09:44:22 AM      32     98.02      0.00      1.98      0.00      0.00      0.00
09:44:22 AM      33     99.00      0.00      1.00      0.00      0.00      0.00
09:44:22 AM      34     98.00      0.00      1.00      0.00      0.00      1.00
09:44:22 AM      35     97.98      0.00      2.02      0.00      0.00      0.00
09:44:22 AM      36     94.00      0.00      5.00      0.00      0.00      1.00
09:44:22 AM      37     98.02      0.00      0.99      0.00      0.00      0.99
09:44:22 AM      38     97.98      0.00      1.01      0.00      0.00      1.01
09:44:22 AM      39     89.00      0.00     11.00      0.00      0.00      0.00
09:44:22 AM      40     83.00      0.00     13.00      0.00      0.00      4.00
09:44:22 AM      41     97.00      0.00      3.00      0.00      0.00      0.00
09:44:22 AM      42     91.92      0.00      8.08      0.00      0.00      0.00
09:44:22 AM      43     94.06      0.00      5.94      0.00      0.00      0.00
09:44:22 AM      44     92.93      0.00      7.07      0.00      0.00      0.00
09:44:22 AM      45     97.00      0.00      3.00      0.00      0.00      0.00
09:44:22 AM      46     99.00      0.00      1.00      0.00      0.00      0.00
09:44:22 AM      47     98.99      0.00      1.01      0.00      0.00      0.00

sar -B 2 5

09:44:24 AM  pgpgin/s pgpgout/s   fault/s  majflt/s  pgfree/s pgscank/s pgscand/s pgsteal/s    %vmeff
09:44:26 AM  14852.00  71776.00 101443.50      0.00 216420.00      0.00      0.00      0.00      0.00
09:44:28 AM  14336.00    184.00   5123.00      0.00  47167.50      0.00      0.00      0.00      0.00
09:44:30 AM  14418.00 203778.00  67194.50      0.00 132952.50      0.00      0.00      0.00      0.00
09:44:32 AM  14352.00 220796.00   2475.00      0.00  59666.00      0.00      0.00      0.00      0.00
09:44:34 AM  13318.00  56996.00  16290.00      0.00   9599.00      0.00      0.00      0.00      0.00
Average:     14255.20 110706.00  38505.20      0.00  93161.00      0.00      0.00      0.00      0.00

来自vmstat命令

procs -----------memory---------- ---swap-- -----io---- -system-- ------cpu-----
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st
65  0 3505188 6265864 4828612 304096576    0    0   137   127    0    0 49  1 50  0  0
63  1 3505188 6068484 4828660 304294848    0    0 12292 41500 95782 88751 98  2  1  0  0
66  0 3505188 5933464 4828672 304429248    0    0 14668 130968 85788 90844 97  2  1  0  0

r：等待运行时的进程数。

从内核消息中我们得到：

[117426425.532990] blk_update_request: critical medium error, dev sdc, sector 116127985
[117426431.038365] sd 0:0:3:0: [sdc] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[117426431.038374] sd 0:0:3:0: [sdc] tag#0 Sense Key : Medium Error [current] [descriptor] 
[117426431.038378] sd 0:0:3:0: [sdc] tag#0 Add. Sense: Unrecovered read error
[117426431.038383] sd 0:0:3:0: [sdc] tag#0 CDB: Read(16) 88 00 00 00 00 00 06 eb f8 f0 00 00 00 08 00 00
[117426431.038386] blk_update_request: critical medium error, dev sdc, sector 116127985
[139602560.596832] traps: polkitd[27641] general protection ip:7f7996318cf2 sp:7ffe7a28e5b0 error:0 in libmozjs-17.0.so[7f79961da000+3b3000]
[144770588.094226] sd 0:0:11:0: [sdk] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[144770588.094238] sd 0:0:11:0: [sdk] tag#0 Sense Key : Medium Error [current] [descriptor] 
[144770588.094242] sd 0:0:11:0: [sdk] tag#0 Add. Sense: Unrecovered read error
[144770588.094248] sd 0:0:11:0: [sdk] tag#0 CDB: Read(16) 88 00 00 00 00 00 01 15 20 00 00 00 02 00 00 00

那么根据上面的输出，CPU IDLE 非常低的根本原因是因为我们从内核消息中得到的磁盘错误，这是否有意义？

rhel
Martin Hope
yael
Asked: 2023-06-12 11:22:56 +0800 CST
  • 5

我想分享以下问题

在 RHEL 7.9 机器上升级安全 rpm 之后包括microcode_ctlrpm更新

rpm -qa | grep microcod
microcode_ctl-2.1-73.15.el7_9.x86_64

我们注意到以下内核消息。

[Sun Jun  4 13:12:19 2023] Microcode update for Intel Broadwell-EP/EX (BDX-ML B/M/R0; family 6, model 79,
stepping 1; CPUID 0x406f1) CPUs is disabled as it may cause system instability.
Please refer to /usr/share/doc/microcode_ctl/caveats/06-4f-01_readme
and /usr/share/doc/microcode_ctl/README.caveats for details.
[Sun Jun  4 13:13:35 2023] After installation of a new version of microcode_ctl package,
[Sun Jun  4 13:13:35 2023] initramfs hasn't been re-generated for all the installed kernel packages.
[Sun Jun  4 13:13:35 2023] The following kernel packages have been skipped: kernel-3.10.0-514.26.2.el7.x86_64.
[Sun Jun  4 13:13:35 2023] Please re-generate initramfs manually for these kernel packages with the
[Sun Jun  4 13:13:35 2023] "dracut -f --kver KERNEL_VERSION" command in order to get the latest
[Sun Jun  4 13:13:35 2023] Intel CPU microcode included into early initramfs image for it, if needed.

当前的 RHEL 内核版本是

uname -r
3.10.0-1160.80.1.el7.x86_64

所以根据 dmesg 我们可以看到。

dracut -f --kver KERNEL_VERSION

那么这是否意味着我们需要在命令中将当前内核版本设置为

dracut -f --kver 3.10.0-1160.80.1.el7.x86_64

或者将内核设置为内核消息中定义的

dracut -f --kver  kernel-3.10.0-514.26.2.el7.x86_64
linux
Martin Hope
yael
Asked: 2023-05-30 01:21:00 +0800 CST
  • 3

我们正在使用服务器 RHEL 7.9 版本从 7.x 行下载 rpm

我们连接到 rhel 7.x 存储库，如下所示（VIA subscription-manager）

yum repolist
Loaded plugins: langpacks, product-id, search-disabled-repos, subscription-manager
repo id                                                                                                     repo name                                                                                                            status
docker-ce-stable/7Server/x86_64                                                                             Docker CE Stable - x86_64                                                                                                     245
rhel-7-server-extras-rpms/x86_64                                                                            Red Hat Enterprise Linux 7 Server - Extras (RPMs)                                                                           1,457
rhel-7-server-optional-rpms/7Server/x86_64                                                                  Red Hat Enterprise Linux 7 Server - Optional (RPMs)                                                                  18,552+5,311
rhel-7-server-rpms/7Server/x86_64                                                                           Red Hat Enterprise Linux 7 Server (RPMs)                                                                             26,611+7,114
repolist: 46,865

到目前为止，我们正在从 rhel 存储库下载 rpm，这很好。

现在的问题是万一我们想从 8.x RHEL 存储库下载 rpm。

我们可以使用相同的 RHEL 7.9 从 8.x 存储库下载 rpm 吗？

这是我们所做的例子。

我们为 rhel 8.x 添加额外的相关 repos，如下例

vi redhat.repo


[rhel-8-for-x86_64-highavailability-rpms]
name = Red Hat Enterprise Linux 8 for x86_64 - High Availability (RPMs)
baseurl = https://cdn.redhat.com/content/dist/rhel8/$releasever/x86_64/highavailability/os
enabled = 0
gpgcheck = 1
gpgkey = file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
sslverify = 1
sslcacert = /etc/rhsm/ca/redhat-uep.pem
sslclientkey = /etc/pki/entitlement/8663009972005896744-key.pem
sslclientcert = /etc/pki/entitlement/8663009972005896744.pem
metadata_expire = 86400
enable_metadata = 0
ui_repoid_vars = releasever

我们做了以下额外的步骤

yum clean all
subscription-manager refresh

和

yum repolist

但我们仍然只得到 7.x 的回购协议

repo id                                                                                                     repo name                                                                                                            status
docker-ce-stable/7Server/x86_64                                                                             Docker CE Stable - x86_64                                                                                                     245
rhel-7-server-extras-rpms/x86_64                                                                            Red Hat Enterprise Linux 7 Server - Extras (RPMs)                                                                           1,457
rhel-7-server-optional-rpms/7Server/x86_64                                                                  Red Hat Enterprise Linux 7 Server - Optional (RPMs)                                                                  18,552+5,311
rhel-7-server-rpms/7Server/x86_64                                                                           Red Hat Enterprise Linux 7 Server (RPMs)                                                                             26,611+7,114
repolist: 46,865

我们的流程出了什么问题？

参考 - https://access.redhat.com/discussions/4547301

rhel
Martin Hope
yael
Asked: 2023-05-18 15:46:31 +0800 CST
  • 3

我们的网络实验室范围从 18.2.1.1 到 18.7.252.253，我们只想捕获版本为 7.x (/etc/redhat-release) 的 Linux RHEL 机器，（我们有大约 2870 台机器，只有 390 台 RHEL 机器）

强制我可以为这个任务创建 bash/python/perl 脚本，但也许我们可以获得一些已经存在的工具来完成这项工作？

linux
Martin Hope
yael
Asked: 2023-03-08 16:56:10 +0800 CST
  • 4

我们在文件中设置以下内核参数99-custom.conf

more /etc/sysctl.d/99-custom.conf

net.ipv4.tcp_low_latency = 1
net.ipv4.tcp_adv_win_scale = 1
net.ipv4.tcp_max_syn_backlog = 30000
net.ipv4.tcp_max_tw_buckets = 2000000
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_fin_timeout = 5
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.all.accept_source_route = 2
net.ipv4.tcp_mtu_probing = 1

为了即时设置，我们可以使用上面的参数sysctl -p /etc/sysctl.d/99-custom.conf

但当然重启后这些值就会消失。

所以，解决这个问题的一种方法是在/etc/rc.local

作为

more /etc/rc.local
#!/bin/bash
# THIS FILE IS ADDED FOR COMPATIBILITY PURPOSES
#
# It is highly advisable to create own systemd services or udev rules
# to run scripts during boot instead of using this file.
#
# In contrast to previous versions due to parallel execution during boot
# this script will NOT be run after all other services.
#
# Please note that you must run chmod +x /etc/rc.d/rc.local to ensure
# that this script will be executed during boot.

touch /var/lock/subsys/local

sysctl -p  /etc/sysctl.d/99-custom.conf

以上是正确的方法吗？

linux
Martin Hope
yael
Asked: 2023-02-28 00:00:40 +0800 CST
  • 9

在下面的示例fstab文件中，我们要删除所有以 开头的行UUID，但除了UUID带有bootword的行

/dev/mapper/VG100-lv_root /                       xfs     defaults        0 0
UUID=735cb76a-51b5-4e06-b6fb-3b9577e38dc5 /boot                   xfs     defaults        0 0
/dev/mapper/VG100-lv_var /var                    xfs     defaults        0 0


UUID=0b14011d-f69d-4c4c-8ce0-6240bb0a574a   /var/kafka/mp1                      xfs defaults,noatime 0 0
UUID=2d7872f2-96d4-4ba9-8a17-a1115542645c   /var/kafka/mp2                      xfs defaults,noatime 0 0
UUID=79bdbf56-9a09-4505-ab8e-41ce9432cf0f   /var/kafka/mp3                      xfs defaults,noatime 0 0
UUID=ca42a388-83d4-4f8b-aff7-3450d836eef7   /var/kafka/mp4                      xfs defaults,noatime 0 0
UUID=62d356bb-c393-4a74-bbf9-984b60d3b5c4   /var/kafka/mp5                      xfs defaults,noatime 0 0
UUID=d4071a83-204f-475f-8917-cdd77ef6b1ed   /var/kafka/mp6                      xfs defaults,noatime 0 0

所以例外的结果应该如下

/dev/mapper/VG100-lv_root /                       xfs     defaults        0 0
UUID=735cb76a-51b5-4e06-b6fb-3b9577e38dc5 /boot                   xfs     defaults        0 0
/dev/mapper/VG100-lv_var /var                    xfs     defaults        0 0

到目前为止，我们有以下 sed

 sed -i '/^UUID/d'  /etc/fstab

但是上面的方法删除了所有UUID行

text-processing
Martin Hope
yael
Asked: 2023-01-19 03:57:54 +0800 CST
  • 5

从 saX 文件上的 sar 命令我们可以得到磁盘利用率如下

sar -d -f /var/log/sa/sa18  | grep Average
Average:       dev8-0      1.24      0.00    150.06    121.40      0.04     30.40      4.72      0.58
Average:     dev253-0      0.32      0.00      3.75     11.83      0.01     17.95      3.48      0.11
Average:     dev253-1      0.00      0.00      0.00      0.00      0.00      0.00      0.00      0.00
Average:     dev253-2      1.12      0.00    146.31    130.68      0.04     31.79      4.46      0.50
Average:      dev8-16      0.00      0.00      0.00      0.00      0.00      0.00      0.00      0.00
Average:      dev8-32      0.00      0.00      0.00      0.00      0.00      0.00      0.00      0.00
Average:      dev8-48      0.00      0.00      0.00      0.00      0.00      0.00      0.00      0.00
Average:     dev253-3      0.00      0.00      0.00      0.00      0.00      0.00      0.00      0.00

我们可以看到定义为 MAJ:MIN 的磁盘为（dev8-16、dev8-48 等）

是否有可能获得真正的磁盘名称如 sdb 、 sdc sdc 等？使用命令行sar( sar -d -f /var/log/sa/sa18 | grep Average)

linux
Martin Hope
yael
Asked: 2022-12-01 02:41:14 +0800 CST
  • 6

我们想通过 parted 命令从每个新磁盘创建 2 个分区

如以下示例：

sdg                  8:96   0    50G  0 disk
├─sdg1               8:97   0    25G  0 part
└─sdg2               8:98   0    25G  0 part

例如上面的磁盘大小是 50G，我们想从每个磁盘创建 2 个分区

我们通过以下方法来做到这一点

parted --script /dev/sdg mklabel msdos
parted --script /dev/sdg mkpart primary 0% 50%
parted --script /dev/sdg mkpart primary  50% 100%

以上是否正确以创建请求的 2 个分区？大小相同

我问这个是因为我将值用作0% 50%and 100%，而不是以 GB 为单位给出值

注意 - 其他相关链接 https://askubuntu.com/questions/507274/how-to-create-two-partitions-with-exactly-the-same-size

rhel
Martin Hope
yael
Asked: 2022-10-28 06:39:40 +0800 CST
  • 4

我们有旧的 RHEL 7.2 服务器，我们注意到非常奇怪的内核消息

不确定下面的行是否定义了问题

[ffffea00a5a00000-ffffea00a5bfffff] PMD -> [ffff880015000000-ffff8800151fffff] on node 0

但我也分享了完整的信息，希望能得到更多关于它们的细节

[Thu Oct 27 10:20:59 2022] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[Thu Oct 27 10:20:59 2022] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[Thu Oct 27 10:20:59 2022] Node 1 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1048576kB
[Thu Oct 27 10:20:59 2022] Node 1 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[Thu Oct 27 10:20:59 2022] 11230501 total pagecache pages
[Thu Oct 27 10:20:59 2022] 55992 pages in swap cache
[Thu Oct 27 10:20:59 2022] Swap cache stats: add 1175357, delete 1119365, find 4949217/4971174
[Thu Oct 27 10:20:59 2022] Free swap  = 13818588kB
[Thu Oct 27 10:20:59 2022] Total swap = 16351228kB
[Thu Oct 27 10:20:59 2022] 33652606 pages RAM
[Thu Oct 27 10:20:59 2022] 0 pages HighMem/MovableOnly
[Thu Oct 27 10:20:59 2022] 587996 pages reserved
[Thu Oct 27 10:21:00 2022] init_memory_mapping: [mem 0x2a40000000-0x2c3fffffff]
[Thu Oct 27 10:21:00 2022]  [mem 0x2a40000000-0x2c3fffffff] page 1G
[Thu Oct 27 10:21:00 2022]  [ffffea00a5a00000-ffffea00a5bfffff] PMD -> [ffff880015000000-ffff8800151fffff] on node 0
[Thu Oct 27 10:21:00 2022]  [ffffea00a9000000-ffffea00a93fffff] PMD -> [ffff881002c00000-ffff881002ffffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00a9400000-ffffea00a99fffff] PMD -> [ffff881003800000-ffff881003dfffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00a9a00000-ffffea00a9bfffff] PMD -> [ffff881000200000-ffff8810003fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00a9c00000-ffffea00a9dfffff] PMD -> [ffff881004200000-ffff8810043fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00a9e00000-ffffea00a9ffffff] PMD -> [ffff881003e00000-ffff881003ffffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aa000000-ffffea00aa9fffff] PMD -> [ffff881004600000-ffff881004ffffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aaa00000-ffffea00aabfffff] PMD -> [ffff881005200000-ffff8810053fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aac00000-ffffea00aadfffff] PMD -> [ffff881005000000-ffff8810051fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aae00000-ffffea00ab9fffff] PMD -> [ffff881005400000-ffff881005ffffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aba00000-ffffea00acbfffff] PMD -> [ffff881006200000-ffff8810073fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00acc00000-ffffea00acffffff] PMD -> [ffff881007600000-ffff8810079fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00ad000000-ffffea00ad1fffff] PMD -> [ffff881007400000-ffff8810075fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00ad200000-ffffea00adffffff] PMD -> [ffff881007a00000-ffff8810087fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00ae000000-ffffea00ae1fffff] PMD -> [ffff881008a00000-ffff881008bfffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00ae200000-ffffea00ae3fffff] PMD -> [ffff881008800000-ffff8810089fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00ae400000-ffffea00ae5fffff] PMD -> [ffff881008c00000-ffff881008dfffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00ae600000-ffffea00ae7fffff] PMD -> [ffff881009200000-ffff8810093fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00ae800000-ffffea00ae9fffff] PMD -> [ffff881009000000-ffff8810091fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aea00000-ffffea00aebfffff] PMD -> [ffff881009400000-ffff8810095fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aec00000-ffffea00aedfffff] PMD -> [ffff881009800000-ffff8810099fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00aee00000-ffffea00aeffffff] PMD -> [ffff881009600000-ffff8810097fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00af000000-ffffea00af1fffff] PMD -> [ffff881009c00000-ffff881009dfffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00af200000-ffffea00af3fffff] PMD -> [ffff881009a00000-ffff881009bfffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00af400000-ffffea00af5fffff] PMD -> [ffff88100a200000-ffff88100a3fffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00af600000-ffffea00af7fffff] PMD -> [ffff881009e00000-ffff881009ffffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00af800000-ffffea00b03fffff] PMD -> [ffff88100a400000-ffff88100adfffff] on node 1
[Thu Oct 27 10:21:00 2022]  [ffffea00b0400000-ffffea00b09fffff] PMD -> [ffff88100b000000-ffff88100b5fffff] on node 1
[Thu Oct 27 10:21:01 2022]  [ffffea00b0a00000-ffffea00b0bfffff] PMD -> [ffff881004400000-ffff8810045fffff] on node 1
[Thu Oct 27 10:21:01 2022]  [ffffea00b0c00000-ffffea00b0dfffff] PMD -> [ffff88100b800000-ffff88100b9fffff] on node 1
[Thu Oct 27 10:21:01 2022] init_memory_mapping: [mem 0x2c40000000-0x2e3fffffff]
[Thu Oct 27 10:21:01 2022]  [mem 0x2c40000000-0x2e3fffffff] page 1G
[Thu Oct 27 10:21:01 2022]  [ffffea00b0e00000-ffffea00b0ffffff] PMD -> [ffff88100b600000-ffff88100b7fffff] on node 1
[Thu Oct 27 10:21:01 2022]  [ffffea00b1000000-ffffea00b1dfffff] PMD -> [ffff88100ba00000-ffff88100c7fffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b1e00000-ffffea00b33fffff] PMD -> [ffff88100cc00000-ffff88100e1fffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b3400000-ffffea00b4ffffff] PMD -> [ffff88100e400000-ffff88100fffffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b5000000-ffffea00b51fffff] PMD -> [ffff88100c800000-ffff88100c9fffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b5200000-ffffea00b59fffff] PMD -> [ffff881010000000-ffff8810107fffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b5a00000-ffffea00b5bfffff] PMD -> [ffff881010c00000-ffff881010dfffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b5c00000-ffffea00b5dfffff] PMD -> [ffff881010a00000-ffff881010bfffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b5e00000-ffffea00b61fffff] PMD -> [ffff881011000000-ffff8810113fffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b6200000-ffffea00b69fffff] PMD -> [ffff881011800000-ffff881011ffffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b6a00000-ffffea00b7ffffff] PMD -> [ffff881012200000-ffff8810137fffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b8000000-ffffea00b81fffff] PMD -> [ffff881013a00000-ffff881013bfffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b8200000-ffffea00b83fffff] PMD -> [ffff881013e00000-ffff881013ffffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b8400000-ffffea00b85fffff] PMD -> [ffff881013c00000-ffff881013dfffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b8600000-ffffea00b87fffff] PMD -> [ffff881014400000-ffff8810145fffff] on node 0
[Thu Oct 27 10:21:01 2022]  [ffffea00b8800000-ffffea00b89fffff] PMD -> [ffff881014000000-ffff8810141fffff] on node 0
rhel
Martin Hope
yael
Asked: 2022-10-27 07:36:04 +0800 CST
  • 4

在 RHEL 7.9 机器中，我们创建了新用户 -moon

注意-用户moon由创建，我们通过命令给moon用户useradd密码passwd

moon用户应具有与root

为了做到这一点，我们添加以下配置/etc/sudoers

moon    ALL=(ALL)       ALL
moon    ALL=(ALL:ALL)ALL
moon    ALL=(ALL) NOPASSWD:ALL

但我们有以下问题

我们访问用户moon

# su moon
$ whoami
moon

但是当我们尝试将hdfs用户从用户更改为用户时，moon我们会收到密码提示

$su hdfs
Password:

绕过密码所需的配置，就像用户发生的那样root

这是来自用户的示例root

# su hdfs

上面的例子来自用户 root，我们不需要回答密码

sudo
Martin Hope
yael
Asked: 2022-06-14 02:05:55 +0800 CST
  • 0

我们擦除磁盘签名如下（这是在我们执行 umount 之后）

 wipefs -a /dev/sde
/dev/sde: 2 bytes were erased at offset 0x00000438 (ext4): 53 ef

然后我们检查磁盘是否没有文件系统，如下所示

lsblk -f

sde                ext4              20eba791-c9c9-4462-aa23-74c40a41b8a0

但是尽管我们擦除了文件系统，lsblk 仍然在 sde 磁盘上显示 ext4 文件系统

linux filesystems