0

I used dd to capture the two local vm partitions like this...

# dd if=/dev/sda1 | gzip >mySda1.gz 
# dd if=/dev/sda2 | gzip >mySda2.gz

Then I attached two volumes of sufficient size to an already running instance and mounted them (as /mnt/one and /mnt/two), then copied the .gz files up to the instance and used these commands to restore the partitions

# gunzip –c mySda1.gz | dd of=/dev/xvdk
# gunzip –c mySda2.gz | dd of=/dev/xvdl

The gunzip commands do not show failure, but when I then go /mnt/one and issue command ls -a there is nothing there. Why is this? The .gz files are very large. Why does the mounted partition show as blank even if the gunzip command completed?

dmohr
  • 2,699
  • 1
  • 22
  • 22
  • 1
    Just to confirm: you unmounted `/dev/xvdk` and `/dev/xvdkl`, wrote over them, successfully remounted them and still found nothing there? Or did you forget to unmount the partitions prior to overwriting them? The latter will cause utter havoc and just confuse the Linux kernel. – davidg Mar 14 '13 at 03:34
  • No problem---I'll convert the comment into an answer. – davidg Mar 14 '13 at 06:57

1 Answers1

1

Before you can write directly to a partition, you must first ensure that it is unmounted.

Linux will not notice if you write directly to the disk behind its back (and, more importantly, will assume that this will not happen---it will likely get very confused if you try modifying a mounted file system.)

So, the correct procedure would be as follows: 

umount /dev/xvdk
gunzip –c mySda1.gz | dd of=/dev/xvdk
mount /dev/xvdk

and again for /dev/xvdl.

davidg
  • 5,868
  • 2
  • 33
  • 51