Dump/snapshot problems
Kris Kennaway
kris at obsecurity.org
Sat Mar 11 09:45:45 UTC 2006
On Sat, Mar 11, 2006 at 12:37:03PM +0300, Eugene wrote:
> Hi!
>
> ----- Original Message -----
> From: "Kris Kennaway" <kris at obsecurity.org>
> To: "Eugene" <genie at geniechka.ru>
> Cc: <freebsd-fs at freebsd.org>
> Sent: Saturday, March 11, 2006 12:05
> Subject: Re: Dump/snapshot problems
>
> >> 1) System hangs or at least not accessible over the network and has to
> >> be
> >> physically reset. Last message on console
> >> Collecting pv entries -- suggest increasing PMAP_SHPGPERPRO?
> >> maxproc limit exceeded by id(0), please see tuning(7) and login.conf(5)
> >> Question: what exactly should I tune?
> >
> >The value of PMAP_SHPGPERPROC in your kernel config, and the maxproc
> >limit as described in those two manpages.
>
> Well, I can read -) I would like to know why it fails in virtually unloaded
> system (except for dump) and what parameters/values _in particular_ should
> be tweaked.
See the NOTES file for discussion of the former, and please read the
manpages.
> >You can ignore the fsync message, it's a side-effect of the snapshot
> >operation not succeeding. Just retry the dump.
>
> That's very comforting but why is it not succeding? And I would really like
> the dump to work automatically (as it did for more than a year before these
> problems started to appear recently).
I don't know.
Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-fs/attachments/20060311/d3bccd9b/attachment.bin
More information about the freebsd-fs
mailing list