| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
| |
- some client-side memory leak fixes
- announce and check protocols and protocol versions
|
| |
|
|
|
|
|
| |
cleanup gcc warning,
use PRIu64
header cleanups
const pointer fixes.
|
| |
|
|
| |
lvm.conf *and* lvmetad is running.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
used to be a few mis-ordered memory accesses (release and access in the next
block). Fix that set_flag could have sometimes corrupted the flags being
modified.
A few issues with metadata tracking are sorted out as well now, and there are
only a few problems remaining before we can integrate lvmetad, mostly on the
client side:
- metadata areas need to be tracked in lvmetad (most likely to be addressed
through an extension of metadata, meaning no special support in lvmetad would
be needed)
- non-udev scanning code needs to be taught about telling lvmetad about device
disappearance (pvscan most importantly)
- this last item also needs to mesh with metadata inconsistencies and
suddenly-incomplete volume groups (aux disable_dev in tests); udev-based
scanning should address this separately and more elegantly
|
| | |
|
| |
|
|
|
| |
them. These are currently mostly for testing the daemon-common code. LVMetaD
functionality is expected to trickle in soon though.
|
| | |
|
| |
|
