Date: Fri, 22 Aug 2008 02:19:26 +0200 From: Polytropon <freebsd@edvax.de> To: freebsd-questions@freebsd.org, Polytropon <freebsd@edvax.de> Cc: Oliver Fromme <olli@lurza.secnetix.de>, freebsd-questions@freebsd.org Subject: Re: Again: fsck_ffs memory requirements Message-ID: <20080822021926.d2d9ee0f.freebsd@edvax.de> In-Reply-To: <200808211649.m7LGnH8l009064@lurza.secnetix.de> References: <20080821173738.1e01ca84.freebsd@edvax.de> <200808211649.m7LGnH8l009064@lurza.secnetix.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 21 Aug 2008 18:49:17 +0200 (CEST), Oliver Fromme <olli@lurza.secnetix.de> wrote: > Polytropon <freebsd@edvax.de> wrote: > > On Thu, 21 Aug 2008 17:23:41 +0200, Kris Kennaway <kris@FreeBSD.org> wrote: > > > Increase kern.maxdsiz. > > > > It seems that I don't have kern.maxdsiz: > > > > # sysctl kern.maxdsiz > > sysctl: unknown oid 'kern.maxdsiz' > > > > Am I looking at the wrong place? Allthough I've been using > > FreeBSD since 4.0, it seems that I got a "little" stupid over > > the years... :-/ > > It's a loader tunable, so you must put it in /boot/loader.conf. I put a value of ca. 1.5 GB into the loader's config file and that solved the problem. Thanks! > Best regards, and good luck with your recovery! Allthough fsck_ffs 5 does seem to be able to calloc() the needed memory, it fails with the same message as fsck_ffs 7: fsck_ffs: bad inode number 306176 to nextinode Don't know what to do next. I may gather all information I have, write al little "story" and bring this topic up here next week. Maybe someone has better ideas than me. > PS: Better make good backups next time. More precise: Better make _at least any_ backups. :-) More than 5 years without any (!) problem with FreeBSD and now this stupid problem... :-( -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080822021926.d2d9ee0f.freebsd>