Date: Sun, 03 May 1998 22:59:26 -0400 From: Benjamin Greenwald <beng@lcs.mit.edu> To: Tom <tom@sdf.com> Cc: "David E. Cross" <dec@phoenix.its.rpi.edu>, freebsd-hackers@FreeBSD.ORG Subject: Re: Network problem with 2.2.6-STABLE Message-ID: <199805040259.WAA10604@miris.lcs.mit.edu> In-Reply-To: Your message of "Sun, 03 May 1998 18:12:27 PDT." <Pine.BSF.3.95q.980503180902.16180A-100000@misery.sdf.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > On Sun, 3 May 1998, David E. Cross wrote: > > > similar to (sorry I I did not write it down): "ping: no network buffers > > available", any telnet requet, etc would just hang indefinititely, the > > Not enough mbufs. Increase MAXUSERS or NMBCLUSTERS > > Beware, dump/restore is also broken for large filesystems. I personally > think that dump/restore should be dropped from FreeBSD. > > Tom It's been fairly well proven that dump/restore is by far the most accurate way of backing up one's filesystems. Dropping dump/restore would not only put a huge number of users in the lurch, but it would be eliminating the best tool for the job. I'm not familiar with the problems in dump/restore, but it seems to make a lot more sense to me to fix them rather than force everyone to change over to an inferior solution. Do you have a suggestion as to what we'd replace dump/restore with? (And PLEASE don't say "tar -g" ... *shiver*) Ben To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805040259.WAA10604>