Error Allocating Icount Link Information Memory Allocation Failed
Contents |
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring fsck error storing directory block information developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question
Fsck Memory Allocation Failed
_ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's
E2fsck
how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Running out of memory running fsck on large filesystems up vote 9 down vote favorite 3 I look after an old Debian linux box (running etch) with only 512 MB of RAM, but a lot of external storage attached. One ext3 filesystem is 2.7 TB in size, and fsck can't check it, because it runs out of memory, with an error such as this one: Error allocating directory block array: Memory allocation failed e2fsck: aborted I've added a 4 GB swap partition and it still doesn't complete, but this is a 32-bit kernel, so I don't expect adding any more will help. Apart from booting into a 64-bit kernel, are there any other ways of getting fsck to complete its check? linux debian memory ext3 fsck share|improve this question asked May 17 '09 at 22:10 TimB 1,17521116 add a comment| 2 Answers 2 active oldest votes up vote 10 down vote accepted A 64 bit kernel and large quantities of RAM will allow the fsck to finish nice and fast. Alternately, there's now an option in e2fsck that'll tell it to store all of it's intermediate results in a directory instead of in RAM, which helps immensely. Create /etc/e2fsck.conf with the following contents: [scratch_files] directory = /var/cache/e2fsck (And, obviously, make sure that directory exists, and is on a partition with a good few GB of free space). e2fsck will run SLLOOOOWWWWWWW, but at least it'll complete. Of course, this won't work with the root FS, but if you've got swap then you're past mounting the root FS anyway. share|improve this answer answered May 17 '09 at 23:05 womble♦ 76.6k11117184 add a comment| up vote 4 down vote I ended up trying what womble suggested; here are some more details that may be useful if, like me, you haven't seen this new functionality in e2fsck before. The "scratch_files" configuration option for e2fsck became available sometime in the version 1.40.x period. (In our case, we had to upgrade to the latest Debian distribution to get this functionality.)
a +6TB device Date: Mon, 09 Jun 2008 19:33:48 +0200 Dear Srs, That's the scenario: +6TB device on a 3ware 9550SX RAID controller, running Debian Etch 32bits, with 2.6.25.4 kernel, and defaults e2fsprogs version, "1.39+1.40-WIP-2006.11.14+dfsg-2etch1". Running "tune2fs" returns that filesystem is in EXT3_ERROR_FS state, "clean with errors": # tune2fs -l /dev/sda4 tune2fs 1.40.10 (21-May-2008) Filesystem volume name:
Filesystems Utilities Brought to you by: tytso Summary Files Reviews Support Wiki Mailing Lists Tickets ▾ Bugs Feature Requests Support Requests https://sourceforge.net/p/e2fsprogs/bugs/254/ Patches News Discussion Donate Code Svn Create Ticket View Stats Group Searches Changes Closed Tickets Open Tickets Help Formatting Help #254 Error allocating icount structure: Memory allocation http://osdir.com/ml/misc.nslu2.general/2005-10/msg00061.html failed Status: open Owner: Theodore Ts'o Labels: e2fsck (61) Priority: 5 Updated: 2012-11-28 Created: 2010-01-14 Creator: Anonymous Private: No While trying to fsck a 7TB RAID, I memory allocation get the following error: ubuntu@ubuntu:~$ date; sudo fsck -nC /dev/sdb1; date Thu Jan 14 09:23:04 UTC 2010 fsck from util-linux-ng 2.16 e2fsck 1.41.9 (22-Aug-2009) /dev/sdb1 has gone 260 days without being checked, check forced. Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Error allocating icount structure: Memory allocation failed memory allocation failed e2fsck: aborted Thu Jan 14 13:37:59 UTC 2010 I have attached some additional information. The filesystem has 855 million inodes. The only memory requirements I was able to find for e2fsck state that it requires about 0.5MB of memory per million inodes, so it should require about 418MB for this drive, which is much less than the 1.8GB available (plus a 1TB swap drive which I added because I was getting the same error with 8GB of swap.) Am I running into a per-process RAM limitation, or a bug in e2fsck, or something else? Thanks, -- Don Discussion Nobody/Anonymous - 2010-01-14 Diagnostic info hydra.txt If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Nobody/Anonymous - 2011-04-07 7Cg3kv xegvhcfidolq, [url=http://bkyaybqmvtts.com/]bkyaybqmvtts[/url], [link=http://lyjunyufvelu.com/]lyjunyufvelu[/link], http://tqykbpxeyqhw.com/ If you would like to refer to this comment somewhere else in this project, copy and paste the following link: Nobody/Anonymous - 2011-05-16 KIWSuF