Error Allocating Block Bitmap 4 Memory Allocation Failed E2fsck Aborted
Contents |
system with insufficient RAM, you can encounter the following error. $ e2fsck -p -f /dev/vg_mnt/lv_mnt01 /dev/vg_mnt/lv_mnt01: Error allocating icount structure: Memory allocation failed /dev/vg_mnt/lv_mnt01: Error allocating directory block array: Memory allocation failed e2fsck: aborted This
Fsck Error Storing Directory Block Information
happens because the e2fsck tries to store all inode information in memory, which qnap swap memory may exceed the available memory size on the system. To fix this, either upgrade the system with more memory or try fsck memory allocation failed to set additional options that allow e2fsck to create a temporary directory on a system with sufficient (several GB's) free disk space. Not that this only works for e2fsck version 1.40 or higher (meaning: CentOS and RHEL users are screwed since they only provide 1.39). $ rpm -qa | grep e2fsprogs e2fsprogs-libs-1.39-34.el5_8.1 e2fsprogs-devel-1.39-34.el5_8.1 e2fsprogs-1.39-34.el5_8.1 To run the e2fsck with a recent version, try the following. $ cd /usr/local/src $ wget "http://kernel.org/pub/linux/kernel/people/tytso/e2fsprogs/v1.42.5/e2fsprogs-1.42.5.tar.gz" $ tar xzf e2fsprogs-1.42.5.tar.gz $ rm -f e2fsprogs-1.42.5.tar.gz $ cd e2fsprogs-1.42.5 $ yum install gcc make $ ./configure $ make The above will download e2fsck (the latest version as of this writing), compile and make it but leave it in the directory of the build (/usr/local/src/e2fsck), it won't copy the binaries to your system. That means you can use the newly compiled binary at /usr/local/src/e2fsprogs-1.42.5/e2fsck/e2fsckw. Now, since you have a e2fsck version higher than 1.40, you can set the options to use a scratch-disk and avoice the Out-of-Memory errors. First, create the directory. $ mkdir -p /var/cache/e2fsck And create a custom file called /etc/e2fsck.conf that contains the following content. $ cat /etc/e2fsck.conf [scratch_files] directory = /var/cache/e2fsck This tells e2fsck to use a directory on disk if the total available memory is insufficient to host all inode information of the partition. If you had to make a new e2fsck yourself because the OS didn't have a recent version, start the new e2fsck as such. $ /usr/local/src/e2fsprogs-1.42.5/e2fsck/e2fsck -f /dev/vg_mnt/lv_mnt01 If you had a recent version already, you can simply restart e2fsck with the system binary. $ e2fsck -f /dev/vg_mnt/lv_mnt01 When the new e2fsck is running, you should see additional information appear in the cache-directory. $ ls /var/cache/e2fsck/ total 475M -rw------- 1 root root 106M Aug 5 13:16 2fb8a70e-8ee3-4c9c-b95b-0e42ae1ecebd-dirinfo-jthsIm -rw------- 1 root root 368M Aug 5 13:16 2fb8a70e-8ee3-4c9c-b95b-0e42ae1ecebd-icount-ZxFa0u If the directory is empty, your e2fsck i
to your NAS for large volume fsck activities Posted on 06/03/2015 by dan That's right, another heading from the Department of not terribly catchy blog article titles. I've been having a mighty terrible time with one of my QNAP arrays lately. After updating to 4.1.2, I've been getting some weird symptoms. For example, every time the NAS reboots, the filesystem is marked as unclean. Worse, it mounts as read-only from time to time. And it seems generally flaky. So I've spent the last week trying to evacuate the data with the thought that maybe I can re-initialize it https://ma.ttias.be/e2fsck-error-allocating-directory-block-array-memory-allocation-failed/ and clear out some of the nasty stuff that's built up over the last 5 years. Incidentally, while we all like to moan about how slow SATA disks are, try moving a few TB via a USB2 interface. The eSATA seems positively snappy after that. Of course, QNAP released version 4.1.3 of their platform recently, and a lot of the symptoms I've been experiencing have stopped occurring. http://www.penguinpunk.net/blog/qnap-add-swap-to-your-nas-for-large-volume-fsck-activities/ I'm going to continue down this path though, as I hadn't experienced these problems on my other QNAP, and just don't have a good feeling about the state of the filesystem. And you thought that I would be all analytical about it, didn't you? In any case, I've been running e2fsck on the filesytem fairly frequently, particularly when it goes read-only and I have to stop the services, unmount and remount the volume. [/] # cd /share/MD0_DATA/ [/share/MD0_DATA] # cd Qmultimedia/ [/share/MD0_DATA/Qmultimedia] # mkdir temp mkdir: Cannot create directory `temp': Read-only file system [/share/MD0_DATA/Qmultimedia] # cd / [/] # /etc/init.d/services.sh stop Stop qpkg service: chmod: /share/MD0_DATA/.qpkg: Read-only file system Shutting down Download Station: OK Disable QUSBCam ... Shutting down SlimServer... Error: Cannot stop, SqueezeboxServer is not running. WARNING: rc.ssods ERROR: script /opt/ssods4/etc/init.d/K20slimserver failed. Stopping thttpd-ssods .. OK. rm: cannot remove `/opt/ssods4/var/run/thttpd-ssods.pid': Read-only file system WARNING: rc.ssods ERROR: script /opt/ssods4/etc/init.d/K21thttpd-ssods failed. Shutting down QiTunesAir services: Done Disable Optware/ipkg . Stop service: cloud3p.sh vpn_openvpn.sh vpn_pptp.sh ldap_server.sh antivirus.sh iso_mount.sh qbox.sh qsyncman.sh rsyslog.sh snmp lunportman.sh iscsitrgt.sh twonkymedia.sh init_iTune.sh ImRd.sh crond.sh nvrd.sh StartMediaService.sh bt_scheduler.sh btd.sh mysqld.sh recycled.sh Qthttpd.sh atalk.sh nfs ftp.sh smb.sh versiond.sh . [/] # umount /dev/md0
Developer Network (CDN) ForumsCitrix Insight ServicesCitrix ReadyCitrix Success KitsCloud Provider PackCloudBridgeCloudPlatform (powered by Apache CloudStack)CloudPortalDemo CenterDesktopPlayerEdgeSightEducationForum http://discussions.citrix.com/topic/328361-local-storage-sr-backend-failure-52/ PrototypeHDX MonitorHDX RealTime Optimization PackHotfix Rollup PackJapanese ForumsKnowledge Center http://www.spinics.net/lists/linux-ext4/msg20547.html FeedbackLicensingLTSRNetScalerNetScaler E-Business CommunityNetScaler Gateway (Formerly Access Gateway)Profile ManagementProof of Concept KitsProvisioning ServerQuick Demo ToolkitReceiver, Plug-ins, and Merchandising ServerSecure GatewayShareFileSingle Sign-On (Password Manager)SmartAuditorStoreFrontTechnology PreviewsTrial SoftwareUniversal Print ServerUser Group CommunityVDI-in-a-BoxWeb InterfaceXenAppXenClientXenDesktopXenMobileXenServer Discussions Support Forums Products XenServer XenServer memory allocation Product Family Storage Javascript Disabled Detected You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality. Local Storage SR_BACKEND_FAILURE_52 Started by Shannon Kimber , 02 April 2013 - 12:08 PM Login to Reply 6 replies to this memory allocation failed topic Best Answer Corin Goodier , 02 April 2013 - 12:15 PM Run lvscan and vgscan so you can see the actual bits that would be mounted then run fsck on the actual logical volume as the partition is a PV, not a logical volume... Go to the full post
Shannon Kimber Members #1 Shannon Kimber 7 posts Posted 02 April 2013 - 12:08 PM We have a Tier 2 Xenserver 6.0.2 (15138 - XS602E005 & XS602E003 applied) 4 x 2TB drives (software RAID 0) with 6 VMs (some backed up). One VM is a fileserver in which we were copying 5Gb of data to (largest file: 200mb). During the copy the host froze and had no choice but to reboot.Xenserver applies a "Red X Cross" to Local Storage.TrouDate: Wed, 18 Aug 2010 14:20:13 -0600 Cc: linux-ext4