LVM 정렬 불량: lvcreate로 인해 정렬이 일관되지 않습니다.

LVM 정렬 불량: lvcreate로 인해 정렬이 일관되지 않습니다.

다음 명령을 사용하여 논리 볼륨을 생성할 때 커널 로그에 일부 정렬 오류가 있음이 표시됩니다.

$ sudo vgcreate shinymarengo --dataalignment 1M /dev/sda /dev/sdb /dev/sdc
  Volume group "shinymarengo" successfully created

$ sudo lvcreate --type raid5 -L 4T --nosync --stripesize 1M -n shinymarengo_data shinymarengo
  WARNING: New raid5 won't be synchronised. Don't read what you didn't write!
  Logical volume "shinymarengo_data" created.

처음에는 모든 것이 괜찮다고 생각하겠지만, 보면 dmesg몇 가지 경고가 있습니다.

[  +0.000052] device-mapper: table: 254:6: adding target device dm-3 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=512, start=0
[  +0.000010] device-mapper: table: 254:6: adding target device dm-5 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=0
[  +0.000010] device-mapper: table: 254:6: adding target device dm-3 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=512, start=0
[  +0.000008] device-mapper: table: 254:6: adding target device dm-5 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=0
[  +0.000290] device-mapper: table: 254:6: adding target device dm-3 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=512, start=0
[  +0.000009] device-mapper: table: 254:6: adding target device dm-5 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=0
[  +0.000008] device-mapper: table: 254:6: adding target device dm-3 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=512, start=0
[  +0.000008] device-mapper: table: 254:6: adding target device dm-5 caused an alignment inconsistency: physical_block_size=4096, logical_block_size=512, alignment_offset=0, start=0

lsblk다음과 같은 이야기를 하는 것 같습니다 .

$ lsblk -t
NAME                                      ALIGNMENT  MIN-IO  OPT-IO PHY-SEC LOG-SEC ROTA SCHED       RQ-SIZE   RA WSAME
sda                                               0    4096       0    4096     512    1 mq-deadline      58  128   32M
├─shinymarengo-shinymarengo_data_rmeta_0          0    4096       0    4096     512    1                 128  128   32M
│ └─shinymarengo-shinymarengo_data               -1 1048576 2097152    4096     512    1                 128 6144    0B
└─shinymarengo-shinymarengo_data_rimage_0         0    4096       0    4096     512    1                 128  128   32M
  └─shinymarengo-shinymarengo_data               -1 1048576 2097152    4096     512    1                 128 6144    0B
sdb                                               0    4096       0    4096     512    1 mq-deadline      58  128   32M
├─shinymarengo-shinymarengo_data_rmeta_1        512    4096       0    4096     512    1                 128  128   32M
│ └─shinymarengo-shinymarengo_data               -1 1048576 2097152    4096     512    1                 128 6144    0B
└─shinymarengo-shinymarengo_data_rimage_1       512    4096       0    4096     512    1                 128  128   32M
  └─shinymarengo-shinymarengo_data               -1 1048576 2097152    4096     512    1                 128 6144    0B
sdc                                               0    4096       0    4096     512    1 mq-deadline      58  128   32M
├─shinymarengo-shinymarengo_data_rmeta_2          0    4096       0    4096     512    1                 128  128   32M
│ └─shinymarengo-shinymarengo_data               -1 1048576 2097152    4096     512    1                 128 6144    0B
└─shinymarengo-shinymarengo_data_rimage_2         0    4096       0    4096     512    1                 128  128   32M
  └─shinymarengo-shinymarengo_data               -1 1048576 2097152    4096     512    1                 128 6144    0B

정렬 불량을 제거하기 위해 다르게 수행할 수 있는 작업이 있습니까? 아니면 단순히 버그일 수 있습니까?

편집 - 플랫폼 세부정보:

  • 라즈베리 파이 4B 2GB
  • 라즈베리 파이 네메시스
  • 리눅스 4.19.108
  • LVM 2.03.02(2)

관련 정보