On 25/03/2009, at 7:55 PM, Daniel O'Connor wrote:
On Wednesday 25 March 2009 18:37:17 Bartosz Stec wrote:
Yes, dump is broken for you, deal with it. It is quite possible
your FS
is corrupt, and/or your disk is damaged.
..and/or it is some other hardware problem, maybe you also should
test
your memory with memtest or something similiar? I'm using dump/
restore
very frequently and I had never seen such problem. Neither on -
RELAESE,
-STABLE, nor -CURRENT.
So I think you should make sure that your problem is not
hardware/filesystem dependent before you point dump/restore as a
couse
of the problem. Peter Jeremy already gives you good hints to do that.
One other thing would be to make absolutely sure that your version
of dump &
restore are in sync, the are very machine/version dependent.
And the system is compiled without strange CFLAGS in /etc/make.conf
Great way to cause inexplicable problems because an unsafe
optimisation ran rampant, which is really noticeable when it's two
programs that have to be in sync.
--
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
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
