it should write up the first Gb and then zeros for the rest.
scratch that, i got the same result, it only writes the first 1Gb. so you
could create another 99Gb file that is blank and then use cat
dd if=/dev/zero of=/blank bs=1M count=99000
then use cat
cat backup_file blank > newbackupfile
you should then get 99Gb+1Gb=100Gb.
remember to use the fsck on it at the end.
On Dec 10, 2007 11:25 PM, Johan Ekh <[EMAIL PROTECTED]> wrote:
> It seems to work! Magic...
> I started to create a 1 Gb file. Then I tried to expand it to 100Gb but it
> became also 1 Gb.
>
> I used "dd if=backup_sparse of=backup_100Gb bs=1M count=100000"
>
> Did do it wrong?
>
> /Johan
>
>
>
> 2007/12/10, dan <[EMAIL PROTECTED]>:
>
> > if all else fails, use a file and mount it with 'loop'
> >
> > you will get around all of the nfs issues except speed.
> >
> > you would mount the nas by nfs, create a sparse file
> >
> > > dd if=/dev/zero of=/nfsmountpoint/filename bs=1M count='how many mb
> > > you want'
> > >
> >
> > now make a filesystem on it
> > mkfs/ext3 /nfsmountpoint/filename
> >
> > agree to the warning that it is not a block device
> >
> > now mount it
> > mount -o loop /nfsmountpoint/filename /target
> >
> > df -h and see your new drive!
> >
> > alternatively, you could create a sparse file to mount but you would
> > risk an overflow..
> >
> > better would be to create a file that is the right size today and expand
> > it later. if you use ext3 you have create a 1Gb file, then when you need
> > more space you can create a new file from the original file like so
> >
> > dd if=/path/to/original/file of=/newfile bs=1M count=newsize
> > then
> > fsck.ext3 /newfile
> >
> > then you have a new file with the old files contents ready to use.
> >
> > you can also use the linux software raid on files to create mirrors.
> > even on two seperate nfs servers, though performance will suck.
> >
> >
> >
> >
> >
> > On Dec 10, 2007 11:07 AM, Les Mikesell < [EMAIL PROTECTED]> wrote:
> >
> > > Johan Ekh wrote:
> > > > Thanks for your answer.
> > > > However, I try to install backuppc as root but it is still not
> > > possible
> > > > to "chown".
> > > > I can access the mounted disk as "root" or as any user. But not
> > > "chown".
> > > > Any ideas?
> > > >
> > > > Can you point me in the right direction regarding the
> > > "no_root_squash"
> > > > option?
> > > > Is it used with the "mount" command?
> > >
> > > No, it is a server side option. Typically root (uid=0) from a client
> > > is
> > > mapped to 'nobody' on the server file system. If the server is linux,
> > > you need an /etc/exports line like:
> > > /path/exported
> > > 192.168.0.0/255.255.255.0(rw,no_root_squash,async)<http://192.168.0.0/255.255.255.0%28rw,no_root_squash,async%29>
> > > ^^^ network range
> > >
> > > Other NFS servers may have a different syntax.
> > >
> > > --
> > > Les Mikesell
> > > [EMAIL PROTECTED]
> > >
> >
> >
>
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
