| Summary: | sys-fs/lvm2: Shutdown of volumes has trouble with snapshots | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Christian Ruppert (idl0r) <idl0r> |
| Component: | Current packages | Assignee: | Robin Johnson <robbat2> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | agk, cardoe, proxy-maint, tove |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
That was the BL1 stop.sh script. Please retest with BL2. Hmm, I didn't realize that the script is still used Ok, this is problematic.
We're passing the name of the VG, not the name of the LV
this is so that lvchange can shut down volumes nicely in parallel.
Does the next command, "Shutting Down volume groups" work properly?
And after that, how many LVs are left?
Add this to the end of that script:
/sbin/lvs --config "${config}"
That script is no longer in use at all. |
Create a volume and make a snapshot of it. # /etc/init.d/lvm stop * Shutting Down logical volumes ... Can't change snapshot logical volume "snap_test" [ !! ] That's happens in /lib/rcscripts/addons/lvm-stop.sh:20 So e.g. /sbin/lvchange --config global { locking_dir = "/dev/.lvm" } --sysinit -a ln vg Looks like we should excludes snapshots, at least in some cases.