Date: Thu, 17 Oct 1996 11:44:54 -0700 (PDT) From: Chris Timmons <skynyrd@tahoma.cwu.edu> To: "Mark S. Velasquez" <msv@arisia.net> Cc: freebsd-isp@freebsd.org Subject: Re: **ccd, disk striping, and fsck problems** Message-ID: <Pine.OSF.3.95.961017113948.19528D-100000@tahoma.cwu.edu> In-Reply-To: <199610151658.LAA26097@brasil.moneng.mei.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I had this problem recently and changed the passno in fstab such that each ccd device would be checked seperately. Problem solved! Did the unlimit-before-exec solution work too? I've been meaning to have a look at the code to see what really is happening but with the passno workaround I've moved on to other fires at the moment... -Chris On Tue, 15 Oct 1996, Joe Greco wrote: > > We're running FreeBSD 2.1.5 and I recently striped 3 disks(Quantum 4.3GB, > > 7400 rpm) into one logical volume, and have beeen using it without incident. > > However, when I brought the system down for maintainance, it was unable to > > boot due to an fsck problem(complains about "out of memory"). The filesystem > > was built with "-i 1024", which I feel was appropriate for a filesystem to > > be used as a news server's spool directory, but I'm wondering if this is > > what's causing the problem. > > > > Any help is appreciated. > > I assume you have a fair amount of physical RAM if you are running a news > server. That is probably not the problem. > > If you are crashing in the "fsck -p" in /etc/rc, I would probably try: > > csh -c "unlimit; exec fsck -p" > > as a way to circumvent the per process memory limit that you may be > running into. You can probably stick that right into /etc/rc in place > of the current fsck -p. > > ... JG >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.3.95.961017113948.19528D-100000>