Date: Thu, 8 Mar 2001 18:58:31 +0100 From: "Andy De Petter" <andy@techos.be> To: <freebsd-hackers@freebsd.org> Subject: RE: memory disk problem (mounted memory "hangs") Message-ID: <NMEIJMCFCECINGDHLNMOIEHOFBAA.andy@techos.be> In-Reply-To: <NMEIJMCFCECINGDHLNMOOEHMFBAA.andy@techos.be>
next in thread | previous in thread | raw e-mail | index | archive | help
I've been able to reproduce this problem, with "yes >> /mnt/my_mdisk". After it grows 'till about 100Mb (which might be coincidance) used, it hangs again. Do I have to "reserve" memory, for my mdisk, and if so, with which sysctl parameters, and which values to give them, for 512Mb mdisk? -a > -----Original Message----- > From: owner-freebsd-hackers@FreeBSD.ORG > [mailto:owner-freebsd-hackers@FreeBSD.ORG]On Behalf Of Andy De Petter > Sent: donderdag 8 maart 2001 17:56 > To: freebsd-hackers@freebsd.org > Subject: memory disk problem (mounted memory "hangs") > > > > Hello, > > I have a machine, with 2Gb physical memory, of which I mount 512Mb as a > filesystem (/dev/md0c). This partition is very heavily used, and the > machine hangs after a certain amount of time, for no obvious reason. > > What I've found is this, to be configured during kernel compilation > time: > > -- > # > # Set the number of PV entries per process. Increasing this can > # stop panics related to heavy use of shared memory. However, that can > # (combined with large amounts of physical memory) cause panics at > # boot time due the kernel running out of VM space. > # > # If you're tweaking this, you might also want to increase the sysctls > # "vm.v_free_min", "vm.v_free_reserved", and "vm.v_free_target". > # > # The value below is the one more than the default. > # > options "PMAP_SHPGPERPROC=201" > -- > > Now, I have tried this, and set PMAP_SHPGPERPROC=400, and changed set > "vm.v_free_reserved=1024" and "vm.v_free_min=1500", but still I have the > same problem, that the machine hangs after a certain amount of time. > > I'm running FreeBSD 4.2-RELEASE. > > Is there anything else, I should take into account, or anything I should > configure, to stop this from happening? Because once the mounted mdisk > "hangs", the only way to unlock the machine, is to reboot it :( > > Thanks, > > -Andy > > -- > "For nothing can seem foul to those that win." > - Henry IV, Pt1, Act 5, Sc 1 > > *** DISCLAIMER *** > This e-mail and any attachments thereto may contain information, which > is confidential and/or protected by intellectual property rights and > are intended for the sole use of the recipient(s) named above. Any use > of the information contained herein (including, but not limited to, > total or partial reproduction, communication or distribution in any > form) by persons other than the designated recipient(s) is prohibited. > If you have received this e-mail in error, please notify the sender > either by telephone or by e-mail and delete the material from any > computer. Thank you for your cooperation. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > 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?NMEIJMCFCECINGDHLNMOIEHOFBAA.andy>