| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
| |
Check lock_type and lock_args in vg_validate.
Make some minor changes to when lock_type and lock_args
are written during vgcreate and vgchange to eliminate
intermediate states of the VG.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
not needed
|
|
|
|
| |
avoid malloc/free entirely
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
These both now work:
make check_lvmlockd_sanlock T=shell/sanlock-hello-world.sh
make check_lvmlockd_dlm T=shell/dlm-hello-world.sh
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
lvextend --use-policies ee/lv1
Policy-based resize is supported only for snapshot and thin pool volumes.
lvextend --usepolicies ee/lv1
Policy-based resize is supported only for snapshot and thin pool volumes.
lvextend --us-ep-oli---cies ee/lv1
Policy-based resize is supported only for snapshot and thin pool volumes.
|
| |
|
| |
|
|
|
|
|
| |
A new thin pool LV gets a new lock in lvmlockd.
The locks from data and meta LVs are unlocked and freed.
|
| |
|
|
|
|
| |
--clustered n was failing when it shouldn't.
|
|
|
|
|
|
|
| |
The parent directory (DIR) should either exist or should be created.
It is not desirable to use `mkdir -p` which could lead to existing
directory reuse.
|
|
|
|
|
|
|
|
|
| |
'vgcreate --shared' is only used with lvmlockd and selects
lock_type sanlock|dlm depending on which lock manager is
running. It will not create clvm VGs.
'vgcreate --clustered' is only used with clvmd, only
creates clvm VGs, and will not create lockd VGs.
|
|
|
|
| |
handle them similarly
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
at the start of lvcreate
|
|
|
|
|
|
|
|
|
|
| |
The lockd_init_lv() function no longer calls lvmlockd
to ask for the sanlock lease to be allocated for the LV,
i.e. lockd_init_lv_args().
Instead, it waits until vg_write() to do that, so the sanlock
lease does not need to be freed in all the cases where lvcreate
may quit before actually finishing.
|
| |
|
| |
|
|
|
|
|
| |
Use standard syslog level names as option args to
specify the level at which to send to syslog.
|
|
|
|
|
|
|
| |
By default, vgcreate and vgchange --lock-start will
wait for the lockspace to start. Adding --lock-opt nowait
will cause them not to wait. The waiting can always
be canceled by Ctrl-C without any harm.
|
|
|
|
|
|
|
|
|
|
|
| |
By default retry lock operations that return EAGAIN
because the lock is held by another host.
These retries occur at the client/command level, and
can be adjusted using global/lock_retries.
lvmlockd already has some automatic retries to handle
most incidental lock conflicts.
|
| |
|
|
|
|
|
| |
In addition to requiring lvm.conf configuration to override
lock modes, also print a warning if it is done.
|
|
|
|
|
| |
Print one simple warning message if the command cannot
properly use lvmlockd.
|
|
|
|
|
| |
Add explanations of when and why to use the basic lvmlockd
locking functions.
|
|
|
|
|
| |
State the reason that the global lock is
needed in each place it is taken.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
make check_lvmlockd_sanlock T=shell/sanlock-hello-world.sh
will run:
shell/sanlock-prepare.sh to prepare sanlock and lvmlockd on the system
shell/sanlock-hello-work.sh to test using lvmlockd and sanlock
shell/sanlock-remove.sh to undo the things from sanlock-prepare.sh
TODO:
- use alias vgcreate="vgcreate --lock-type sanlock" in sanlock-prepare
so that existing shell tests can just call vgcreate can be used to
create and test sanlock vgs.
- when using existing shell tests with sanlock, we need
prepare_devs/prepare_pvs to create adequately large devs.
See the necessity of sanlock-hello-world of specifying
a large device size. This is needed for all the ondisk
leases that are created by vgcreate.
- get check_lvmlockd_dlm working
|
|
|
|
|
|
|
| |
vgcreate with '--lock-opt wait' will cause the command
to wait for the lock start to complete before returning,
the same as when starting explicitly with
'vgchange --lock-start --lock-opt wait'
|
| |
|
|
|
|
|
| |
Get rid of the round about logic that was copied
from lvmetad. Make it simple and clear.
|
|
|
|
|
|
|
| |
The split names function wasn't used correct, it just
accidentally worked before.
Check for the LVM prefix on dm uuids.
|
|
|
|
|
| |
-o locktype,lockargs can be used to display
the lock_type and lock_args of VGs or LVs.
|
|
|
|
| |
was used for early testing, no purpose any more.
|