summaryrefslogtreecommitdiffstats
path: root/WHATS_NEW
Commit message (Collapse)AuthorAgeFilesLines
...
* Update and fix monitoring of thin pool devicesZdenek Kabelac2012-03-231-0/+1
| | | | | | | | | | | | | Code adds better support for monitoring of thin pool devices. update_pool_lv uses DMEVENTD_MONITOR_IGNORE to not manipulate with monitoring. vgchange & lvchange are checking real thin pool device for existance as we are using _tpool real device and visible LV pool device might not be even active (_tpool is activated implicitely for any thin volume). monitor_dev_for_events is another _lv_postorder like code it might be worth to think about reusing it here - for now update the code to properly monitory thin volume deps. For unmonitoring add extra code to check the usage of thin pool - in case it's in use unmonitoring of thin volume is skipped.
* Return mem fail if hash insert failsZdenek Kabelac2012-03-231-0/+2
|
* Fix typo in config option checkZdenek Kabelac2012-03-231-0/+1
|
* Update lcov targetZdenek Kabelac2012-03-231-0/+1
|
* Fix regression in thin monitoringZdenek Kabelac2012-03-201-0/+1
| | | | | | | Patch https://www.redhat.com/archives/lvm-devel/2012-February/msg00118.html removed initilization of thin volume monitoring, leaving it only for thin pool - but missed the code move part for monitoring of thin pools. Effectively making thin pools not monitorable.
* Support improperly formated device numbersZdenek Kabelac2012-03-201-0/+1
| | | | | | | | | | | | | There are kernel drivers (smblk) which set '-1' as their device major number. This number is listed in /proc/devices then - but the kernel itself is using just 12 bits - thus device is accessible via 4095 - there is posted patch for 3.4 to fix this behavior (0 for auto allocation was mean to be used). However to still allow using such devices with older kernels add some code to use same behavior - so cut 12 bits from the major number from /proc/devices. For now use log_warn() - maybe the severity of the message could be lowered to just verbose level.
* Fix string parsingZdenek Kabelac2012-03-161-0/+3
| | | | | | | | | Fix propagation of -e option - pass it via internal shell variable. Fix parsing of /proc/mounts files (don't check for substrings). as reported by O.Mangold with suggested patch: https://www.redhat.com/archives/linux-lvm/2012-February/msg00030.html Properly pass arguments with spaces ("$@") Add validation for YES and EXTOFF variable content.
* It's new.Petr Rockai2012-03-161-0/+1
|
* Fix name conflicts that prevent down-converting RAID1 when specifying a deviceJonathan Earl Brassow2012-03-151-0/+1
| | | | | | | | | | | | | When down-converting a RAID1 device, it is the last device that is extracted and removed when the user does not specify a particular device. However, when a device is specified (and it is not the last), the device is removed and the remaining sub-LVs are "shifted down" to fill the hole. This cause problems when resuming the LV because if the shifted devices were resumed (and thus renamed) before the sub-LV being extracted, there would be a name conflict. The solution is to resume the extracted sub-LVs first so that they can be properly renamed preventing a possible conflict. This addresses bug 801967.
* Improve thin_check option passingZdenek Kabelac2012-03-141-0/+1
| | | | | | | Update a way we handle option passing - so we now support path and options with space inside. Fix dm name usage for thin pools with '-' in name. Use new lvm.conf option thin_check_options to pass in options as string array.
* Add --with-thin-check configure optionZdenek Kabelac2012-03-141-0/+1
| | | | | If specified - use given path without test (Path could be empty) If autodetection is in use - check for command in available PATH.
* WHATS_NEWPeter Rajnoha2012-03-141-0/+1
|
* Fix error message when pvmove LV activation fails with name already in use.Alasdair Kergon2012-03-131-0/+1
|
* Better structure layout for device_infoZdenek Kabelac2012-03-121-0/+1
| | | | | | Save some relocation entries and use directly char[]. Since we do not need yes more then 127 partitions per device, use just int8_t. Move lvm_type_filter_destroy into local static function.
* Switch to normal log_verbose messageZdenek Kabelac2012-03-121-0/+1
| | | | Here it's not an error case - so do not push this message to stderr.
* Fix error path for create_toolcontextZdenek Kabelac2012-03-121-0/+1
| | | | | | | Never return unfinished toolcontext - since error path is hit on various stages of initialization we cannot leave it partially uninitialized, since we would need to spread many more test across the code for config_valid. Instead return NULL and properly release udev library resources as well.
* Fix warn message and update man pageZdenek Kabelac2012-03-061-0/+1
| | | | | | | | | | Fix regression in man page. The chunk size is in kilobyte units on command line input though in the source code we work with sector size unit so make it clear in the man page. Update chunksize for thin pool in man page - it's max value is 1024M == 1G. Fix warning range message to show proper max value.
* post-releaseAlasdair Kergon2012-03-061-0/+3
|
* pre-releaseAlasdair Kergon2012-03-061-3/+3
|
* Switch pvscan --cache major:minor to --major --minor.Alasdair Kergon2012-03-061-0/+1
|
* Some more missing supposedly 64bit operations.Zdenek Kabelac2012-03-051-1/+1
| | | | Avoid use 32bit math for extent_size.
* Fit thin pool metadata into 128MBZdenek Kabelac2012-03-051-0/+1
| | | | | | | | | If the lvcreate may decide some automagical values for a user, try to keep the pool metadata size into 128MB range for optimal perfomance (as suggested by Joe). So if the pool metadata size and chunk_size were not specified, try to select such values they would fit into 128MB size.
* Improve warningZdenek Kabelac2012-03-051-0/+1
| | | | | | | | Use thin_dump --repair suggestion in log error message and use just warning on deactivation path without repair info (since node has been deactivated). Also check whether there is not 16 args for thin_check configured.
* Use 64bit mathZdenek Kabelac2012-03-051-0/+1
| | | | | Prevent 32bit overflow and resulting weird error reports when working with TB sizes..
* Validate udev structuresZdenek Kabelac2012-03-041-1/+1
| | | | | | Avoid using NULL pointers from udev. It seems like some older versions of udev were improperly returning NULL in some case, so do not silently break here, and give at least a warning to the user.
* Return success for deactivation of thin poolZdenek Kabelac2012-03-041-0/+1
| | | | | | | if the thin_check fail on thin pool - still return successful deactivation, since lvremove would currently fail. TODO: find some way to not run check with lvremove.
* Scan all devices for lvmetad if 'pvscan --cache' used without device list.Alasdair Kergon2012-03-031-0/+3
|
* post-releaseAlasdair Kergon2012-03-031-0/+3
|
* .Alasdair Kergon2012-03-031-0/+1
|
* pre-releaseAlasdair Kergon2012-03-031-6/+7
|
* List _thread_registry missed mutexZdenek Kabelac2012-03-021-1/+0
| | | | | Operation on _thread_registry needs to be covered by mutex. Cosmetic move a die code after free for valgind short leak list.
* Add support for thin checkZdenek Kabelac2012-03-021-0/+1
| | | | | | | | Use libdm callback to execute thin_check before activation thin pool and after deactivation as well. Supporting thin_check_executable which may pass in extra options for the tool.
* Fix estimation of pool metadata device sizeZdenek Kabelac2012-03-021-0/+1
| | | | | | | If no size was give the later added minimal size check efectively disable this code. Also the argument for size now must be kept in sector_size, so adding division by SECTOR_SIZE (moved into a const expression)
* Test alloc failZdenek Kabelac2012-03-011-0/+1
|
* Check for alloc errorZdenek Kabelac2012-03-011-0/+1
| | | | Simplify segtype_str usage and check for NULL segtype.
* Add _rimage as reserved suffixZdenek Kabelac2012-03-011-0/+1
|
* Improve error loggingZdenek Kabelac2012-03-011-0/+1
| | | | | Log errors instead of plain return 0. Check for f->private strdup result.
* Check for allocation errorZdenek Kabelac2012-03-011-0/+1
| | | | return ENOMEM when malloc fails.
* Wipe initial 4KiB for non-zeroed thin volumesZdenek Kabelac2012-02-291-0/+1
| | | | | | | | | If the thin pool has disabled zeroing (created with -Zn), we at least clear initial 4KiB of such thin volume (provisions 1st block). If lvcreate is executed with '-an' command will abort (same way like we for normal LV - however for normal LV option -Zn may skip clearing completely, for thin volumes this option is not supported (applies only for pools).
* Allow cluster mirrors to handle the absence of the checkpoint lib (libSaCkpt).Jonathan Earl Brassow2012-02-291-0/+1
| | | | | | | | | | | | The OpenAIS checkpoint library is going away; therefore, cmirrord must operate without it. The algorithms the handle the timing of when to send a checkpoint, the determination of what to send, and which ongoing cluster requests are relevent with respect to the checkpoints are unaffected. We need only replace the functions that actually perform the storing/transmitting and retrieving/receiving of the checkpoint data. Rather than store the checkpoint data in an OpenAIS checkpoint file, we simply transmit it along with the message that notifies the incoming node that the checkpoint is ready.
* Revert free of allocated segtypeZdenek Kabelac2012-02-281-0/+1
| | | | | lvm_register_segtype takes ownership of segtype and call destructor for it in error path.
* Test dm_hash_insert() failures mem failuresZdenek Kabelac2012-02-281-0/+1
|
* Ensure clvmd message is always \0 terminatedZdenek Kabelac2012-02-281-0/+1
| | | | | | Drop whole buffer clearing (most messages at <100 bytes). Just make sure we have always \0 terminated string for strlen() operations. (before for PIPE_BUF sized messages this was not set).
* Better detection of missing dmeventd fifo connectionZdenek Kabelac2012-02-281-0/+2
|
* Duplicate standard in/out descriptors for daemonZdenek Kabelac2012-02-281-0/+1
| | | | | | | | | | | | | | | Addressing somewhat tricky bug here. Since stdin,stdout,stderr were closed it's been occasionally possible to see some unexpected messages to be flowing into a clvmd and generating some randomly sized allocation of many megabytes. Since the message was not being generated by standard send_message() construction, after some more testing it apperead to be a debug log message - thus something has flown to local socket opened on strandard out descriptor. To fix the issue - use standard file descriptor duplication code for daemons. For making easier debugging of polling daemon - developer might want to recompile without modifition of standard file descriptors.
* Limit max size of clvmd messageZdenek Kabelac2012-02-281-0/+1
| | | | | | | | | | This could be seen as some sort of simple validation - it's not easy to recognize a valid message for now - but we definitely do not want to allocate a lot of megabytes in clvmd memory locked daemon when broken message gets in. Size of 8000 is just selected for now - possibly there could be much lower value put in.
* Do not send uninitilised bytesZdenek Kabelac2012-02-281-0/+1
| | | | | Use struct initalizers to fill struct members and at the same time have all unspecified members set to 0.
* Use unsigned type for bitmaskZdenek Kabelac2012-02-271-0/+1
| | | | | | Using report_type_t for bitmask is not correct, since we have not defined types for all bit combinations - so switching to unsigned type, since values of report_type_t enum are unsigned.
* Nicer cleanup of excl_uuid hashZdenek Kabelac2012-02-271-0/+1
| | | | | Since it on exit path, it's not a big difference, but makes less noise in analyzer and valgrind.
* Check for vg_name existanceZdenek Kabelac2012-02-271-0/+1
| | | | | Since vg_read() mda ops could be called with NULL vg_name, check it before derefence also for pool and format1.
generated by cgit (git 2.34.1) at 2024-06-22 06:28:17 +0000