Your message dated Sun, 12 Sep 2010 16:01:53 +0000
with message-id <e1oup05-0004pv...@merkel.debian.org>
and subject line Package pcopy has been removed from Debian
has caused the Debian Bug report #484067,
regarding Partitions copied with pcopy have two problems
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
484067: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=484067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pcopy
Version: 1.5-1
I used pcopy to copy two partitions from a 60GB hard drive to a 120GB
hard drive. One was the 7GB system partition. The other was a 48GB /home
partition. I pcopied the first to a 10GB partition, and the second to a
100GB partition. Two things happened:
1. The space used and free reported (on the 120GB drive) of both copied
partitions was wrong. They reported the same amount of space used and
free on both drives:
a. The 10GB partition was showing the same amount of disk space used
*and free* as the 7GB original; it should have been showing 3GB more
space free.
b. The 100GB partition was also showing the same figures as the 48GB
original partition. Instead of showing 56GB free, it was showing only
2.5GB free (the amount free on the original partition).
2. After using the system for a few hours, it suddenly started reporting
the pcopied system partition as read-only. After I shutdown and
restarted, the boot process reported errors with the system partition
(mostly about files it couldn't fine). It left me at a command prompt
reading "(initramfs)". I rebooted the system using two different recent
live Linux CDs that fully support ext3 filesystems, and both times fsck
reported that it was incompatible with the ext3 journal version on the
system partition. So I reformatted the partition, used partimage to
restore the original disks system partition to it, restarted, and it
came up fine, reporting the proper amounts of disk space used and free,
and reporting no incompatibilities with the journal version. It has been
working fine for several days now.
I fixed the problem on the second partition by simply copying the data
from the original drive.
I had prepared the 120GB disk by fscking with -c to check for badblocks
and update the badblock list before using pcopy. So there were no
hardware problems with the disk.
pcopy reported no errors during the copying process and didn't crash.
I think pcopy hosed the journal when copying the system partition, and
at least did a number on the directory structure when copying the other
partition.
Thank you for the opportunity to try pcopy. I will stick with partimage
instead for copying partitions.
--
David
gn...@hawaii.rr.com
authenticity, honesty, community
--- End Message ---
--- Begin Message ---
Version: 1.5-2+rm
You filed the bug http://bugs.debian.org/484067 in Debian BTS
against the package pcopy. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/596552. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Luca Falavigna
--- End Message ---
