On Sun, Dec 05, 2010 at 05:11:19AM +0300, Andrew Shirayev wrote:
Package: lvm2
Version: 2.02.39-8
Severity: critical
Justification: causes serious data loss
Bug fixed upstream in version 2.02.46.
Other not so serious pvmove issues fixed in 2.02.55, 2.02.61 and 2.02.74.
Please use a newer
Small problem...
$ apt-cache policy lvm2
lvm2:
Installed: 2.02.39-8
Candidate: 2.02.39-8
Version table:
*** 2.02.39-8 0
500 http://ftp.debian.org lenny/main Packages
500 http://security.debian.org lenny/updates/main Packages
100 /var/lib/dpkg/status
2010/12/6
severity 605957 important
thanks
On Sun, Dec 05, 2010 at 05:11:19AM +0300, Andrew Shirayev wrote:
Justification: causes serious data loss
The log does not show any indication that there is actually some data
lost.
== Short description
I miss a description.
omega:~# pvmove -n tmptmp1
At first time i move 300Gb mail storage to new disk, and lost all data. :-(
Transfer complite at 300Gb/sec speed...
Kernel logs:
omega:~# ls -l /dev/mapper/ | grep move
omega:~# dmesg | tail -2
[11762.790363] drbd5: peer( Secondary - Primary )
[11764.552933] drbd2: peer( Secondary - Primary )
Look for compare #605957 and #529876...
:start
At first time pvmove create /dev/mapper/mir1a-pvmove0, change metadata.
move data, and not remove /dev/mapper/mir1a-pvmove0.
At second time pvmove -- fail, change metadata. but not move realdata
and remove /dev/mapper/mir1a-pvmove0...
GOTO start
Package: lvm2
Version: 2.02.39-8
Severity: critical
Justification: causes serious data loss
-- System Information:
Debian Release: 5.0.7
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8,
6 matches
Mail list logo