hi!
I copied the entire /var/lib/BackupPC directory to an other machine
using the tool BackupPC_tarPCCopy . I made test restores, everything
looks fine.
Unfortunately there is something I don't understand.
source machine (ext3):z
/dev/md0 7.2T 5.2T 2.1T 72% /var/lib/BackupPC
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: bed31140-a212-43d6-8c88-23f4f5130d97
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal resize_inode dir_index filetype
sparse_super large_file
Default mount options: (none)
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 976764928
Block count: 1953524992
Reserved block count: 0
Free blocks: 551570805
Free inodes: 790904302
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 558
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Filesystem created: Tue Feb 23 14:20:53 2010
Last mount time: Tue Sep 14 20:57:18 2010
Last write time: Sun Dec 12 12:39:20 2010
Mount count: 10
Maximum mount count: 26
Last checked: Tue Feb 23 14:20:53 2010
Check interval: 15552000 (6 months)
Next check after: Sun Aug 22 15:20:53 2010
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal inode: 8
Default directory hash: tea
Directory Hash Seed: 7094c4e9-177f-4269-8a65-0b5fe2ee67b5
Journal backup: inode blocks
target machine (ext4):
/dev/cciss/c0d1p1 5.4T 4.3T 1.1T 81% /var/lib/BackupPC
Filesystem volume name: <none>
Last mounted on: <not available>
Filesystem UUID: e02dd8d0-d4a0-4c47-9cf9-2c08c4964e19
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index
filetype needs_recovery extent flex_bg sparse_super large_file huge_file
uninit_bg dir_nlink extra_isize
Filesystem flags: signed_directory_hash
Default mount options: journal_data_writeback
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 365289472
Block count: 1461150805
Reserved block count: 0
Free blocks: 284021099
Free inodes: 179721980
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 675
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
RAID stride: 32
RAID stripe width: 256
Flex block group size: 16
Filesystem created: Sun Dec 12 13:15:17 2010
Last mount time: Thu Dec 16 09:41:14 2010
Last write time: Thu Dec 16 09:41:14 2010
Mount count: 3
Maximum mount count: 38
Last checked: Sun Dec 12 13:15:17 2010
Check interval: 15552000 (6 months)
Next check after: Fri Jun 10 14:15:17 2011
Lifetime writes: 87 GB
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 256
Required extra isize: 28
Desired extra isize: 28
Journal inode: 8
Default directory hash: half_md4
Directory Hash Seed: f63330a5-efbd-4b5b-a881-63efae2d197f
Journal backup: inode blocks
Could somebody tell me, why there is a so huge difference between used
spaces?
I cannot find out for sure:/
Thank you,
tamas
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
