Hide Forgot
Description of problem: - create pv with metadata size of 128m - create vg from that pv check metadata size = 129m - create additional pv without any allocation of metadata size - extend vg from step 2 with that pv check vg metadata size = 1020k note: this doesn't happen when using "--pvmetadatacopies" "0" reproducible - always
(In reply to comment #0) > Description of problem: > > - create pv with metadata size of 128m > - create vg from that pv > > check metadata size = 129m > > - create additional pv without any allocation of metadata size > - extend vg from step 2 with that pv > > check vg metadata size = 1020k > The smallest metadata area size is considered as the "VG metadata size" reported by the vgs command. You should be using pvs command instead to see the metadata size of each PV independently. > note: this doesn't happen when using "--pvmetadatacopies" "0" > Yes, in this case, this is fine - 0 sized metadata area does not count in at all. So I'm closing this bug report...
(Just a note: if using "--metadatasize 0" in pvcreate command, this will fallback to default value then, alignment then makes for the 1020k we see in the output)