Date: Sat, 21 Nov 2009 16:44:42 +0000 From: Chris Rees <utisoft@googlemail.com> To: Bernt Hansson <bernt@bah.homeip.net> Cc: freebsd-questions@freebsd.org Subject: Re: Dump Message-ID: <b79ecaef0911210844q33c97a7dh4582f670cfaa7a28@mail.gmail.com> In-Reply-To: <4B075AAA.80205@bah.homeip.net> References: <4B0562A4.5050405@bah.homeip.net> <4B056636.6050309@infracaninophile.co.uk> <4B075AAA.80205@bah.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
2009/11/21 Bernt Hansson <bernt@bah.homeip.net>: > Matthew Seaman skrev: >> >> Bernt Hansson wrote: >>> >>> Hello list. >>> >>> I've been testing backups with dump, works well BUT >>> -L does not work. For example >>> >>> dump -0 -a -u -L -f /mnt/dump.home.full /dev/ad0s2d >> >> I believe that you need to tell dump the mount point of the file system = in >> order for it to create a snapshot, rather than the device file for the >> partition. (ie. snapshotting only makes sense on a mounted read-write >> filesystem). >> >> Also, if you're dumping a snapshotted FS to a local file, then bump up t= he >> cachesize to improve performance a lot. =A0Add '-C 32' to your command-l= ine. > > Ok. I've tested this > dump -1 -a -u -L -C 64 -h 0 -f /usr/home/bernt/disk2/dump.backup.home.2 > /usr/home > > The error is > mksnap_ffs: Cannot create /usr/home/.snap/dump_snapshot: Invalid argument > dump: Cannot create /usr/home/.snap/dump_snapshot: No such file or direct= ory > Just for sanity... Are you root? Chris --=20 A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b79ecaef0911210844q33c97a7dh4582f670cfaa7a28>