dm-snapshot should be in the installer environment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Medium
|
Stefan Bader | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When using snapshots there is one special situation when using "lvconvert --merge" on a snapshot when its origin is still in use (the merge subcommand is in lvconvert since Precise/12.04 at least). In that case the merge request is noted in the meta-data and it will get done the next time the volume group gets activated.
One case where this should be supported as well would be the rescue environment we offer on server images. For this the dm-snapshot module needs to get listed in the d-i lists (Actually there could the the theoretical situation where someone had initiated a merge and the next thing done is an install into the same volume group).
SRU Justification:
Impact: Without this, the installer and rescue environment will produce an error and hide the origin to be merged (as well as the snapshot) making it impossible to access the origin.
Fix: Just an additional module for the d-i.
Testcase: Initiate a merge on a mounted origin. Then boot into the rescue system and try to activate the VG.
This bug was fixed in the package linux - 3.9.0-6.14
---------------
linux (3.9.0-6.14) saucy; urgency=low
[ Stefan Bader ]
* (d-i) Add dm-snapshot to md-modules
- LP: #1191726
[ Tim Gardner ]
* SAUCE: Updated lttng to 5ca7b8a36c04e07 33b6661d519343e b586d75a51
* [Config] d-i: Add calxedaxgmac to nic-modules
- LP: #1192358
* Release Tracking Bug
- LP: #1192633
[ Upstream Kernel Changes ]
* alx: add a simple AR816x/AR817x device driver
cherry-picked from linux-next, replaces ubuntu/alx. upstream
merge expected in 3.11
-- Tim Gardner <email address hidden> Wed, 19 Jun 2013 08:59:51 -0600