Date: Wed, 25 Mar 2009 13:34:31 +1030 From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: "Mikhail T." <mi+thun@aldan.algebra.com> Cc: freebsd-stable@freebsd.org, fs@freebsd.org, Andrew Snow <andrew@modulus.org> Subject: Re: dump | restore fails: unknown tape header type 1853384566 Message-ID: <200903251334.38350.doconnor@gsoft.com.au> In-Reply-To: <49C99204.2050601@aldan.algebra.com> References: <49C83673.3000604@aldan.algebra.com> <200903251232.11418.doconnor@gsoft.com.au> <49C99204.2050601@aldan.algebra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart12025682.40UkcpncZI Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 25 March 2009 12:38:04 Mikhail T. wrote: > Daniel O'Connor =CE=C1=D0=C9=D3=C1=D7(=CC=C1): > >> morning is still hanging (in sbwait) -- I've never seen this before. I= 'm > >> also very troubled, that such an important functionality (dump/restore= !) > >> is sooo problem-prone, and yet so few people seem to care... > > > > Well, "works for me". > > Well, would like a login on this system to take a look for yourself? I > can reproduce the problem easily. I don't know the internals of dump/restore :( > >> Is the official view, that dump is obsolete (and already bit-rotten), > >> perhaps, and use of tar is encouraged instead? > > > > I've never had dump fail but it IS rather crusty and slow.. That said t= ar > > doesn't cover all the information I believe. > > So, if dump/restore ain't it, does FreeBSD have a supported way of > making filesystem-level backups, that's both modern and covers all > aspects (like flags)? I would try a pax archive, eg.. tar --format pax --one-file-system -pcf - -C / . | tar -pxf - -C /mnt/newdi= sk According to the libarchive-formats page this handles ACLs & flags, my test= ing=20 shows it handles flags (at least). eg.. [midget 13:30] /tmp/test2 >touch foo [midget 13:30] /tmp/test2 >chflags uchg foo =20 [midget 13:30] /tmp/test2 >tar --format pax -zpcf /tmp/test.pax.gz foo [midget 13:30] /tmp/test2 >rm -f foo rm: foo: Operation not permitted [midget 13:30] /tmp/test2 >chflags nouchg foo [midget 13:30] /tmp/test2 >rm foo [midget 13:30] /tmp/test2 >tar -pxf /tmp/test.pax.gz =20 [midget 13:30] /tmp/test2 >ls -lao total 30 =20 drwxr-xr-x 2 darius wheel - 512 Mar 25 13:30 . drwxrwxrwt 53 root wheel - 28672 Mar 25 13:29 .. =2Drw-r--r-- 1 darius wheel uchg 0 Mar 25 13:30 foo [midget 13:30] /tmp/test2 >rm -f foo rm: foo: Operation not permitted > That said, I point out, that for me, dump is not failing (although it > did hang this morning). It is the restore, which fails to read dump's > output: You can't tell the difference between dump producing mangled output or rest= ore=20 bombing out on valid input.. =2D-=20 Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C --nextPart12025682.40UkcpncZI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBJyZ9A5ZPcIHs/zowRAjtjAJ9Re4V+zBWBrdjjltDwdYGwJSIaTwCdGlke F95N4/KuXGNR+A1p4WxbUCE= =KvTW -----END PGP SIGNATURE----- --nextPart12025682.40UkcpncZI--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200903251334.38350.doconnor>