| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Recognize when a device is nvme, and apply filter-mpath to
nvme devices in addition to scsi devices.
|
| |
|
|
|
| |
Print a warning if mda1 is not 4k, 8k or 64k.
Don't exit with an error for any unexpected mda1 offset.
|
| |
|
|
|
| |
missing free of devl entries on filtered_devs list in
commit 2c9bb676048fda86867df165aa297f7078dffc4b
|
| | |
|
| |
|
|
|
|
| |
Make dev_cache_get() verify aliases and drop any
that are invalid before returning a dev for a given
name.
|
| |
|
|
|
|
|
|
|
| |
When adding replacement raid+integrity images (lvconvert --repair
after a raid image is lost), various errors can cause the function
to exit with an error. On this exit path, the function attempts
to revert new images that had been created but not yet used. The
cleanup failed to account for the fact that not all images needed
to be reverted.
|
| |
|
|
| |
Check zeroing works on whole thin-pool metadata device.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Since commit 77fdc17d70e62cab75efaaf0dad02493b948610d always include
log_len size into needed extents - however now we may need sometimes
more extents then necessary - mainly when multiple PVs are involved
into allocation.
Add logs_still_needed into calculation of sufficient_pes_free()
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
When a writecache sublv or an integrity metadata sublv
are partial (missing a dev), set the partial flag on
the upper level LV also, as is done for other sublvs.
|
| | |
|
| |
|
|
|
|
|
| |
Fix the two-step writecache detach in commit c32d7fed4f78b.
In the case of uncache, the cachevol is removed after
detaching the writecache. When the detach is finished
in the second step, the remove must wait until then.
|
| |
|
|
|
|
|
|
| |
When using cache with a cachevol, the cache_check tool was
not being run on the cache metadata during activation.
cache_check clears the needs_check flag in the cache
metadata, so if the flag was set due to an unclean
shutdown, the activation would fail.
|
| | |
|
| |
|
|
|
|
|
| |
When 'fsadm resize vg/lv' is used without size, it should just
resize filesystem to match device - but since we now check
for unbound variable in bash - the previous usage no longer
works and needs explicit check.
|
| |
|
|
|
| |
Fix vdo example.
Update some sentences.
|
| | |
|
| |
|
|
|
|
|
| |
This patch improves the clarity, writing style, and language
of the lvmvdo(7) man page.
See https://bugzilla.redhat.com/show_bug.cgi?id=1855804.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
make clearer which is source and which is destination
|
| |
|
|
| |
was using ECMD_FAILED instead of 0.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Verify that corruption is corrected for raid levels other
than raid1. For other raid levels, attempt to corrupt the
given file pattern on each underlying device, since we don't
know which device contains the file being corrupted.
This ensures that corruption is actually be introduced
when testing the other raid levels.
Verify that corruption is being corrected by checking
the integritymismatches count is non-zero for the raid LV,
which includes the total from all images (since we don't
know which image will have the corruption.)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each integrity image in a raid LV reports its own number
of integrity mismatches, e.g.
lvs -o integritymismatches vg/lv_rimage_0
lvs -o integritymismatches vg/lv_rimage_1
In addition to this, allow the total number of integrity
mismatches from all images to be displayed for the raid LV.
lvs -o integritymismatches vg/lv
shows the number of mismatches from both lv_rimage_0 and
lv_rimage_1.
|
| |
|
|
|
|
| |
simplified the method of corrupting data, the old method
was not working reliably. moved syncation tests to a
different file
|
| |
|
|
| |
not version 2
|
| |
|
|
|
|
|
|
|
|
|
| |
Enhance VDO man page with description of memory usage
and space requirements chapter.
Remove some unneeded blank lines in man page.
Use more precise terminology.
Correct examples since cpool and vpool are protected names.
|
| |
|
|
|
| |
line to setup bcache was misplaced in
commit 5a94126e7a28
|
| |
|
|
|
|
| |
This reverts commit 05d23b2dd80919ebd2239cfd7f8e08d5de9ebace.
this required enabling editline in configure
|
| |
|
|
| |
doesn't work on my machine
|
| |
|
|
|
|
|
| |
filters needing io weren't being run because bcache
wasn't set up. Read the first 4k of the device
before doing filtering or reading ondisk structs to
reduce reads.
|
| |
|
|
|
|
|
|
|
| |
It's possible for a machine with a non-4k page size
to create a PV with an mda_header at an offset other
than 4k. Fix pvck --dump to work with these other
mda offsets. pvck --repair will write a new first
mda at 4096 but lvm with other page sizes will work
with this.
|
| |
|
|
| |
when either main or fast lvs are incomplete
|
| |
|
|
| |
syncaction check will detect and correct integrity checksum mismatches.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The args for pvcreate/pvremove (and vgcreate/vgextend
when applicable) were not efficiently opened, scanned,
and filtered. This change reorganizes the opening
and filtering in the following steps:
- label scan and filter all devs
. open ro
. standard label scan at the start of command
- label scan and filter dev args
. open ro
. uses full md component check
. typically the first scan and filter of pvcreate devs
- close and reopen dev args
. open rw and excl
- repeat label scan and filter dev args
. using reopened rw excl fd
- wipe and write new headers
. using reopened rw excl fd
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Older blockdev tool return failure error code with --help,
and since now the tool abort on command failure, lets
detect missing --getsize64 support directly by running
command and check if it returns something usable.
It's likely very hard to have the system with
such old blockdev tool and newer lvm2 compiled.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Since 'kilobytes' could be seen in 2 way - SI as '1000',
while all programmers sees it as '1024' - switch to
commonly acceptted KiB, MiB....
Resolves RHBZ 1496255.
|
| |
|
|
| |
Just add space between %s(.
|
| |
|
|
|
|
| |
Test case where filesystem has been corrected via fsck.
In such case fsck returns '1' as success and should be
handled in a same way as '0' since fs is correct.
|
| |
|
|
|
|
|
| |
Set more secure bash failure mode for pipilines.
Avoid using unset variables.
Enhnace error reporting for failing command.
Avoid using error via 'case..esac || error'.
|
| | |
|
