Date: Mon, 24 Feb 2014 09:23:21 -0700 From: Ian Lepore <ian@FreeBSD.org> To: Dmitry Sivachenko <trtrmitya@gmail.com> Cc: stable@FreeBSD.org, Slawa Olhovchenkov <slw@zxy.spb.ru> Subject: Re: fsck dumps core Message-ID: <1393259001.1149.36.camel@revolution.hippie.lan> In-Reply-To: <831076C1-0DF7-41BF-B8C5-57583DC92586@gmail.com> References: <417919B7-C4D7-4003-9A71-64C4C9E73678@gmail.com> <A5C0A5F8-09BD-4D54-B80C-F1C54EF88C2B@gmail.com> <20140224155018.GA21738@zxy.spb.ru> <831076C1-0DF7-41BF-B8C5-57583DC92586@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2014-02-24 at 19:52 +0400, Dmitry Sivachenko wrote: > On 24 =C6=C5=D7=D2. 2014 =C7., at 19:50, Slawa Olhovchenkov <slw@zxy.sp= b.ru> wrote: >=20 > > On Mon, Feb 24, 2014 at 06:27:15PM +0400, Dmitry Sivachenko wrote: > >=20 > >> Forgot to mention that it is ~90TB partition and this server has 24G= B of RAM. > >>> Is there any way to complete fsck to get this drive working? > >=20 > > Try to add some swap space. >=20 >=20 > I have 48GB of swap. >=20 > It dumps core almost immediately on start, not that it is running out o= f swap. It looks to me like it's trying to allocate an insanely large amount of memory, perhaps in response to some insane value it found while trying to walk the filesystem data. I had something like that happen back in the 90s, and I was eventually able to track it down to garbage written into one inode block. I manually zero'd that block with dd and lost a few files in the process, but was able to recover most of the filesystem. I'm not recommending that you start zeroing out blocks on your disk at this point, just mentioning one possibility of how much difficulty you may face. fsck does an amazing job, but it can't cope with every possible type of insanity it may encounter. -- Ian
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1393259001.1149.36.camel>