|
From: SourceForge.net <no...@so...> - 2004-08-28 11:29:46
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2733795 By: szaka If you use a Unix filesystem on the NFS server then it should be 2.5 GB. What't the filesystem on the NFS server? One workaround from 'man ntfsclone' but the image will be bigger (maybe 3 GB?): backup: ntfsclone --output - /dev/hda1 | gzip -c > ntfs.img.gz restore: gunzip -c ntfs.img.gz | dd of=/dev/hda1 bs=8192 Make sure the backup doesn't report any error. Bzip2 can compress better but usually it's much slower. Restoring the image will be also slower but this is solved in the current ntfsclone development version by using a much more efficient image format. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44085 |
|
From: SourceForge.net <no...@so...> - 2004-08-28 22:59:16
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2734270 By: nobody the nfs filesystem is ufs. i did get one error/message when the client mounted the nfs "mount version older than kernel" but everything seemed to work ok, i did a test write and access, but things did seem a bit slow to me. and when i check the nfs disk on the server it says the backup.img file is around that 20gb size but doesnt take up that space on the drive or anything. thats why i thought it was crapping out for the reason of not enough space. the nfs is on my laptop and going through wireless network btw - not that it should matter. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44085 |
|
From: SourceForge.net <no...@so...> - 2004-08-29 09:31:43
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2734528 By: szaka > the nfs filesystem is ufs. Oh, so it's not Linux? What OS? > i did get one error/message when the client mounted the nfs "mount > version older than kernel" Your mount package is older then the kernel. > but everything seemed to work ok, i did a test write and access, but > things did seem a bit slow to me. and when i check the nfs disk on the > server it says the backup.img file is around that 20gb size but doesnt > take up that space on the drive or anything. You you did a plain 'ntfsclone -o /mnt/backup.img /dev/hda1' then that's the expected. 'ls' shows the file size, and 'du' shows the allocated space on the disk. > thats why i thought it was crapping out for the reason of not enough > space. the nfs is on my laptop and going through wireless network btw > - not that it should matter. Well, wireless network might do matter. Usually they are slower and can have reliability issues. Transfer depends on many factors. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44085 |
|
From: SourceForge.net <no...@so...> - 2004-08-29 20:46:07
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2734953 By: nobody the os is freebsd. i set up a nfs on another bsd computer and it seem to do ok. du sees it as the 2gb file, but ls and x see it as 21gb. whats up with that? will this cause problems when i try to put it on a dvdr? i guess i could try compessing it first that might make it relize its only 2gb. let me know what you think. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44085 |
|
From: SourceForge.net <no...@so...> - 2004-08-31 07:55:09
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=2736944 By: szaka > du sees it as the 2gb file, but ls and x see it as 21gb. whats up with > that? It's a sparse file. A file is sparse if it has unallocated blocks (holes). The reported size of such files are always higher than the disk space consumed by them. The du command can tell the real disk space used by a sparse file. The holes are always read as zeros. All major Linux and Unix filesystem like, ext2, ext3, reiserfs, Reiser4, JFS and XFS, supports sparse files but for example the ISO 9600 CD-ROM filesystem doesn't. > will this cause problems when i try to put it on a dvdr? It depends how you write it. E.g. Iso9660 doesn't support sparse files so it would cause problem. > i guess i could try compessing it first that might make it relize its > only 2gb. let me know what you think. Yes, quite probably you must compress it. But use the method what's written in the manual: Space and speed-wise the most efficient way to compress a clone image tar -cjSf ntfs.img.tar.bz2 ntfs.img Uncompressing a tar archived clone image tar -xjSf ntfs.img.tar.bz2 You can use gzip too of course ('z' option for tar), that's usually much faster but the outputs are a bit bigger. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44085 |
