I have a weird feeling this is going to be a total newbie question... =(
Situation:
=======
I've acquired a new 120 GB Harddisk. Onto that I intend to throw all my "non-system" data, whilst one of my older 40 GB HDDs should hold the system (root, home, usr and swap on primary partitions). To that end I want to first copy the current system contents (using the 120 GB as buffer), repartition the 40 GB to my changed needs and then copy the system contents back. This was reported to work, so I don't think there's a problem in principle.
Alas, the problem:
=============
On the 120 GB HDD, I have created (among others) a 10 GB ext2 partition to serve as a buffer for my root contents, and a 20 GB ext2 partition for my home contents. I did so using the following command:
Code:
mkfs.ext2 -c -T largefile -v /dev/hda2
(respectively hda3)
That space should suffice easily: my root (still including usr at this point) is currently about 4 GB, and my /home is about 5 GB.
Now I try to copy the data like this (example for root partition):
Code:
cp -axv / /mnt/hda3
It starts fine, but after a while I recognise among all the cp-output a message indicating that there is no more free space on the destination drive (don't know the correct syntax of the message in English, my system runs in German). However, there definately IS plenty of space left.
Question:
=======
What's happening there?
Is this an inode problem?
Any remedies?
Thanks in advance!
- furrySpider -
---
Just an addition:
I'm running Slackware 10, the new Harddrive is a Samsung Spinpoint, and there are no journals in the concerned file systems. And, it copied a FAT32 partition nicely.