[Voyage-linux] voyage mubox memory allocation failed during fsck

[chris hermansen]

Good people;

Today I ran fsck on my external 1TB music drive (formatted as ext2) and
this is what happened:

root at voyage-mubox:~# fsck /dev/sda1
fsck from util-linux 2.20.1
e2fsck 1.42.5 (29-Jul-2012)
/dev/sda1 was not cleanly unmounted, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Error allocating icount structure: Memory allocation failed
e2fsck: aborted
root at voyage-mubox:~#

Probably in my 30 years of working with Unix and Linux I have run fsck
nearly 1000 times and I have to say "it's never done that before".

I am guessing that this may be due to limited real memory in the CuBox-i4
and no swap.  Anyone think that is reasonable?

I am also thinking that this is not a Really Good Thing ie I want to be
able to run fsck on this device from time to time.  Now if I can't get it
through the way things are, I can connect it to my Ubuntu laptop, run fsck,
then reconnect it to the CuBox-i4.  But I don't feel like this is a good
long-term plan.

So, I am begging you all in your collected wisdom for some advice.
-- 
Chris Hermansen · clhermansen "at" gmail "dot" com

C'est ma façon de parler.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20140512/0510fc8e/attachment.html>