WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki
« previous next »
Pages: [1] 2   Go Down

Author Topic: mounting failed can not allocate memory  (Read 11647 times)

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
mounting failed can not allocate memory
« on: March 20, 2011, 03:46:56 AM »
For just about any extension I try to download from app-browser, I end up receiving a message at the end of the download like this  "mount: mounting /dev/loop148 on /tmp/tcloop.icu failed: can not allocate memory"

I'm not out of memory or swap. I have microcore 3.5.1

Xfce4 desktop and 25 extensions onboot.

246780 kb ram
8 mb video
784600 kb swap partition

I have no idea what this could be caused by but any help would be GREATLY appreciated.
Logged

Offline u54749

  • Jr. Member
  • **
  • Posts: 70
Re: mounting failed can not allocate memory
« Reply #1 on: March 20, 2011, 05:10:51 AM »
I have the same problem sporadically
Seems to be a zlib problem (used by squashfs)

Issue the dmesg command in a console and look at the last lines.  Is there a zlib error message?

Retrying the mount sometimes works
Logged

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
Re: mounting failed can not allocate memory
« Reply #2 on: March 20, 2011, 05:51:06 AM »
Yeah your right.

It says SQUASHFS error: Failed to allocate Zlib workspace

and retrying the mount "on a very good day" works but that still sucks.......

Hopefully somebody can be a hero and help us out

I'll keep my eyes  open :o
Logged

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: mounting failed can not allocate memory
« Reply #3 on: March 21, 2011, 03:42:03 PM »
Quote from: cURIOUSgEORGE on March 20, 2011, 03:46:56 AM
For just about any extension I try to download from app-browser, I end up receiving a message at the end of the download like this  "mount: mounting /dev/loop148 on /tmp/tcloop.icu failed: can not allocate memory"


is '/tmp/tcloop.icu' a typo or literally so?

Quote
I'm not out of memory or swap. I have microcore 3.5.1

Xfce4 desktop and 25 extensions onboot.

246780 kb ram
8 mb video
784600 kb swap partition

I have no idea what this could be caused by but any help would be GREATLY appreciated.

Not sure what you are exactly doing but 149 extensions plus Xfce4 does sound a bit out of proportion with 256MB RAM.
Note that icu is a rather big extension (7.8MB squashed).

Please also check for free space in your filesystems (squashfs excluded) with 'df', particularly tmpfs.
Logged
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11022
Re: mounting failed can not allocate memory
« Reply #4 on: March 21, 2011, 03:43:14 PM »
Note that kernel memory can't be swapped. One may see this error while still having plenty swap.
Logged
The only barriers that can stop you are the ones you create yourself.

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
Re: mounting failed can not allocate memory
« Reply #5 on: March 22, 2011, 09:05:38 PM »
Hey Tiny, you asked - "is '/tmp/tcloop.icu' a typo or literally so?" No it's NOT a typo but what the heck is icu ? I think I was trying to download and install Clementine at that time - what's icu mean?

Also what do you mean "149" extensions - I only have 25 onboot and 0 ondemand. Am I missing something?

tmpfs use is at 9 % mounted on /

tmpfs 0% mounted on /dev/shm

/dev/hda3 2% /mnt/hda3

/dev/hda3 2% /home

/dev/loop0 100% /tmp/tcloop/netfilter-2.

and everything below that is at 100% - I don't know if that's good or normal or what?

« Last Edit: March 22, 2011, 09:08:20 PM by cURIOUSgEORGE »
Logged

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: mounting failed can not allocate memory
« Reply #6 on: March 23, 2011, 01:28:48 AM »
Then there seems to be something wrong with your dirname(s).
For icu.tcz extension see repo.
Looking at clementine.tcz, with 246780 kb ram I would not attempt to install a music player of 64MB...

The fact that you report /dev/loop148 failing to mount means either:
1:You use 149 extensions
2:You use loop devices partially for other purposes than extensions
3:You are leaking loop devices

Each onboot item could have a dependency chain of multiple extensions.

Your filesystem usage seems to be most moderate, so we can exclude issues there.

EDIT: Check your loop devices with
Code: [Select]
losetup
« Last Edit: March 23, 2011, 01:52:52 AM by tinypoodle »
Logged
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11022
Re: mounting failed can not allocate memory
« Reply #7 on: March 23, 2011, 07:06:49 AM »
It would help to post `free` output and /proc/meminfo, to see how close we are.
Logged
The only barriers that can stop you are the ones you create yourself.

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
Re: mounting failed can not allocate memory
« Reply #8 on: March 23, 2011, 10:32:57 PM »
 Okay thanks for all the help and here's free output and /proc/meminfo

                       total            used            free            shared            buffers
Mem:         246780        224532        22248                     0              17428
-/+ buffers:                    207104        39676                          
swap:        784600          70856       713744
 



MemTotal:         246780 kB
MemFree:            5824 kB
Buffers:           18596 kB
Cached:            92676 kB
SwapCached:        13036 kB
Active:            65696 kB
Inactive:         111876 kB
Active(anon):      35652 kB
Inactive(anon):    35572 kB
Active(file):      30044 kB
Inactive(file):    76304 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:             0 kB
HighFree:              0 kB
LowTotal:         246780 kB
LowFree:            5824 kB
SwapTotal:        784600 kB
SwapFree:         715040 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:         61228 kB
Mapped:            27732 kB
Shmem:              4924 kB
Slab:              46428 kB
SReclaimable:      13064 kB
SUnreclaim:        33364 kB
KernelStack:        1432 kB
PageTables:          740 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      907988 kB
Committed_AS:     330468 kB
VmallocTotal:     778296 kB
VmallocUsed:       11404 kB
VmallocChunk:     764688 kB
DirectMap4k:        8128 kB
DirectMap4M:      245760 kB


 
 Here's what I got from losetup command ( I uninstalled audacity.tcz which was onboot and I also uninstalled about 50 extension that weren't being used and were just sitting in appsaudit under dependencies NOT being used.)

 I uninstalled them because I thought it might help and I wasn't using them anyways but NO LUCK - Same issue.

/dev/loop0: 0 /mnt/hda3/tce/optional/netfilter-2.6.33.3-tinycore.tcz
/dev/loop1: 0 /mnt/hda3/tce/optional/iptables.tcz
/dev/loop2: 0 /mnt/hda3/tce/optional/Xlibs.tcz
/dev/loop3: 0 /mnt/hda3/tce/optional/Xprogs.tcz
/dev/loop4: 0 /mnt/hda3/tce/optional/Xvesa.tcz
/dev/loop5: 0 /mnt/hda3/tce/optional/hicolor-icon-theme.tcz
/dev/loop6: 0 /mnt/hda3/tce/optional/gnome-icon-theme.tcz
/dev/loop7: 0 /mnt/hda3/tce/optional/glib2.tcz
/dev/loop8: 0 /mnt/hda3/tce/optional/libxml2.tcz
/dev/loop9: 0 /mnt/hda3/tce/optional/libcroco.tcz
/dev/loop10: 0 /mnt/hda3/tce/optional/bzip2-lib.tcz
/dev/loop11: 0 /mnt/hda3/tce/optional/libgsf.tcz
/dev/loop12: 0 /mnt/hda3/tce/optional/Xorg-7.5-lib.tcz
/dev/loop13: 0 /mnt/hda3/tce/optional/graphics-libs-1.tcz
/dev/loop14: 0 /mnt/hda3/tce/optional/gdk-pixbuf2.tcz
/dev/loop15: 0 /mnt/hda3/tce/optional/expat2.tcz
/dev/loop16: 0 /mnt/hda3/tce/optional/fontconfig.tcz
/dev/loop17: 0 /mnt/hda3/tce/optional/libxft.tcz
/dev/loop18: 0 /mnt/hda3/tce/optional/pango.tcz
/dev/loop19: 0 /mnt/hda3/tce/optional/pixman.tcz
/dev/loop20: 0 /mnt/hda3/tce/optional/cairo.tcz
/dev/loop21: 0 /mnt/hda3/tce/optional/atk.tcz
/dev/loop22: 0 /mnt/hda3/tce/optional/gtk2.tcz
/dev/loop23: 0 /mnt/hda3/tce/optional/librsvg.tcz
/dev/loop24: 0 /mnt/hda3/tce/optional/shared-mime-info.tcz
/dev/loop25: 0 /mnt/hda3/tce/optional/dbus.tcz
/dev/loop26: 0 /mnt/hda3/tce/optional/dbus-glib.tcz
/dev/loop27: 0 /mnt/hda3/tce/optional/libxcb.tcz
/dev/loop28: 0 /mnt/hda3/tce/optional/libxcb-util.tcz
/dev/loop29: 0 /mnt/hda3/tce/optional/libstartup-notification.tcz
/dev/loop30: 0 /mnt/hda3/tce/optional/libxfce4util.tcz
/dev/loop31: 0 /mnt/hda3/tce/optional/xfconf.tcz
/dev/loop32: 0 /mnt/hda3/tce/optional/libxfce4ui.tcz
/dev/loop33: 0 /mnt/hda3/tce/optional/xfce-utils.tcz
/dev/loop34: 0 /mnt/hda3/tce/optional/garcon.tcz
/dev/loop35: 0 /mnt/hda3/tce/optional/xfce4-appfinder.tcz
/dev/loop36: 0 /mnt/hda3/tce/optional/libnotify.tcz
/dev/loop37: 0 /mnt/hda3/tce/optional/exo.tcz
/dev/loop38: 0 /mnt/hda3/tce/optional/openssl-0.9.8.tcz
/dev/loop39: 0 /mnt/hda3/tce/optional/libwnck.tcz
/dev/loop40: 0 /mnt/hda3/tce/optional/xfdesktop.tcz
/dev/loop41: 0 /mnt/hda3/tce/optional/xfwm4.tcz
/dev/loop42: 0 /mnt/hda3/tce/optional/xfce4-session.tcz
/dev/loop43: 0 /mnt/hda3/tce/optional/Xorg-7.5-bin.tcz
/dev/loop44: 0 /mnt/hda3/tce/optional/libxklavier.tcz
/dev/loop45: 0 /mnt/hda3/tce/optional/xfce4-settings.tcz
/dev/loop46: 0 /mnt/hda3/tce/optional/udev-lib.tcz
/dev/loop47: 0 /mnt/hda3/tce/optional/gudev-lib.tcz
/dev/loop48: 0 /mnt/hda3/tce/optional/xfce4-panel.tcz
/dev/loop49: 0 /mnt/hda3/tce/optional/libexif.tcz
/dev/loop50: 0 /mnt/hda3/tce/optional/Thunar.tcz
/dev/loop51: 0 /mnt/hda3/tce/optional/Xfce4.tcz
/dev/loop52: 0 /mnt/hda3/tce/optional/xfwm4-themes.tcz
/dev/loop53: 0 /mnt/hda3/tce/optional/mirrors.tcz
/dev/loop54: 0 /mnt/hda3/tce/optional/curl.tcz
/dev/loop55: 0 /mnt/hda3/tce/optional/libasound.tcz
/dev/loop56: 0 /mnt/hda3/tce/optional/firefox.tcz
/dev/loop57: 0 /mnt/hda3/tce/optional/libstdc++-5.0.7.tcz
/dev/loop58: 0 /mnt/hda3/tce/optional/thunderbird.tcz
/dev/loop59: 0 /mnt/hda3/tce/optional/squashfs-tools-4.x.tcz
/dev/loop60: 0 /mnt/hda3/tce/optional/sqlite3.tcz
/dev/loop61: 0 /mnt/hda3/tce/optional/nspr.tcz
/dev/loop62: 0 /mnt/hda3/tce/optional/nss.tcz
/dev/loop63: 0 /mnt/hda3/tce/optional/flash10.tcz
/dev/loop64: 0 /mnt/hda3/tce/optional/OSS-modules-2.6.33.3-tinycore.tcz
/dev/loop65: 0 /mnt/hda3/tce/optional/OSS.tcz
/dev/loop66: 0 /mnt/hda3/tce/optional/ossxmix.tcz
/dev/loop67: 0 /mnt/hda3/tce/optional/tcl.tcz
/dev/loop68: 0 /mnt/hda3/tce/optional/tk.tcz
/dev/loop69: 0 /mnt/hda3/tce/optional/python.tcz
/dev/loop70: 0 /mnt/hda3/tce/optional/pycairo-2.7.tcz
/dev/loop71: 0 /mnt/hda3/tce/optional/libffi.tcz
/dev/loop72: 0 /mnt/hda3/tce/optional/gobject-introspection.tcz
/dev/loop73: 0 /mnt/hda3/tce/optional/pygobject-2.7.tcz
/dev/loop74: 0 /mnt/hda3/tce/optional/pygtk-2.7.tcz
/dev/loop75: 0 /mnt/hda3/tce/optional/bleachbit.tcz
/dev/loop76: 0 /mnt/hda3/tce/optional/babl.tcz
/dev/loop77: 0 /mnt/hda3/tce/optional/gegl.tcz
/dev/loop78: 0 /mnt/hda3/tce/optional/gimp2.tcz
/dev/loop79: 0 /mnt/hda3/tce/optional/ttf-bitstream-vera.tcz
/dev/loop80: 0 /mnt/hda3/tce/optional/gqview2.tcz
/dev/loop81: 0 /mnt/hda3/tce/optional/mtpaint-3.21.tcz
/dev/loop82: 0 /mnt/hda3/tce/optional/libmowgli.tcz
/dev/loop83: 0 /mnt/hda3/tce/optional/libmcs.tcz
/dev/loop84: 0 /mnt/hda3/tce/optional/gamin.tcz
/dev/loop85: 0 /mnt/hda3/tce/optional/libmad.tcz
/dev/loop86: 0 /mnt/hda3/tce/optional/SDL.tcz
/dev/loop87: 0 /mnt/hda3/tce/optional/faad.tcz
/dev/loop88: 0 /mnt/hda3/tce/optional/ncurses-common.tcz
/dev/loop89: 0 /mnt/hda3/tce/optional/ncurses.tcz
/dev/loop90: 0 /mnt/hda3/tce/optional/lame.tcz
/dev/loop91: 0 /mnt/hda3/tce/optional/flac.tcz
/dev/loop92: 0 /mnt/hda3/tce/optional/libogg.tcz
/dev/loop93: 0 /mnt/hda3/tce/optional/libvorbis.tcz
/dev/loop94: 0 /mnt/hda3/tce/optional/libao.tcz
/dev/loop95: 0 /mnt/hda3/tce/optional/vorbis-tools.tcz
/dev/loop96: 0 /mnt/hda3/tce/optional/audacious-plugins.tcz
/dev/loop97: 0 /mnt/hda3/tce/optional/audacious.tcz
/dev/loop98: 0 /mnt/hda3/tce/optional/SDL_pango.tcz
/dev/loop99: 0 /mnt/hda3/tce/optional/tuxtype.tcz
/dev/loop100: 0 /mnt/hda3/tce/optional/libmikmod.tcz
/dev/loop101: 0 /mnt/hda3/tce/optional/supertux.tcz
/dev/loop102: 0 /mnt/hda3/tce/optional/starfighter.tcz
/dev/loop103: 0 /mnt/hda3/tce/optional/perl5.tcz
/dev/loop104: 0 /mnt/hda3/tce/optional/libgd.tcz
/dev/loop105: 0 /mnt/hda3/tce/optional/openlierox.tcz
/dev/loop106: 0 /mnt/hda3/tce/optional/madbomber.tcz
/dev/loop107: 0 /mnt/hda3/tce/optional/lbreakout2.tcz
/dev/loop108: 0 /mnt/hda3/tce/optional/itetris.tcz
/dev/loop109: 0 /mnt/hda3/tce/optional/blobwars.tcz


 Watcha thinking ?  ;D
« Last Edit: March 23, 2011, 11:50:02 PM by cURIOUSgEORGE »
Logged

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11022
Re: mounting failed can not allocate memory
« Reply #9 on: March 24, 2011, 05:20:17 AM »
Forgot to say, also /proc/meminfo after executing "sudo cache-clear", for comparison. After you have seen the error, of course.
Logged
The only barriers that can stop you are the ones you create yourself.

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
Re: mounting failed can not allocate memory
« Reply #10 on: March 24, 2011, 02:26:31 PM »




Okay I tried downloading Clementine.tcz again for this example and here's how it went.
mount: can't setup loop device: No space left on device

Then I did /proc/meminfo



MemTotal:         246780 kB
MemFree:           36220 kB
Buffers:            3448 kB
Cached:            52280 kB
SwapCached:         1220 kB
Active:            80296 kB
Inactive:          76528 kB
Active(anon):      53604 kB
Inactive(anon):    62248 kB
Active(file):      26692 kB
Inactive(file):    14280 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:             0 kB
HighFree:              0 kB
LowTotal:         246780 kB
LowFree:           36220 kB
SwapTotal:        784600 kB
SwapFree:         776164 kB
Dirty:                32 kB
Writeback:             0 kB
AnonPages:        100224 kB
Mapped:            27264 kB
Shmem:             14756 kB
Slab:              46756 kB
SReclaimable:      10748 kB
SUnreclaim:        36008 kB
KernelStack:        1584 kB
PageTables:          804 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      907988 kB
Committed_AS:     340528 kB
VmallocTotal:     778296 kB
VmallocUsed:       11052 kB
VmallocChunk:     764688 kB
DirectMap4k:        8128 kB
DirectMap4M:      245760 kB


and then sudo cache-clear (hope this is the order you was asking for it to be in.)


MemTotal:         246780 kB
MemFree:           46996 kB
Buffers:            2320 kB
Cached:            45176 kB
SwapCached:         1220 kB
Active:            72316 kB
Inactive:          74152 kB
Active(anon):      51528 kB
Inactive(anon):    62236 kB
Active(file):      20788 kB
Inactive(file):    11916 kB
Unevictable:           0 kB
Mlocked:               0 kB
HighTotal:             0 kB
HighFree:              0 kB
LowTotal:         246780 kB
LowFree:           46996 kB
SwapTotal:        784600 kB
SwapFree:         776164 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:         98100 kB
Mapped:            27148 kB
Shmem:             14792 kB
Slab:              46428 kB
SReclaimable:      10408 kB
SUnreclaim:        36020 kB
KernelStack:        1560 kB
PageTables:          748 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:      907988 kB
Committed_AS:     337880 kB
VmallocTotal:     778296 kB
VmallocUsed:       11052 kB
VmallocChunk:     764688 kB
DirectMap4k:        8128 kB
DirectMap4M:      245760 kB











Logged

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11022
Re: mounting failed can not allocate memory
« Reply #11 on: March 24, 2011, 02:32:07 PM »
OK, thanks. Weird, you have still plenty of ram free.
Logged
The only barriers that can stop you are the ones you create yourself.

Offline cURIOUSgEORGE

  • Full Member
  • ***
  • Posts: 140
Re: mounting failed can not allocate memory
« Reply #12 on: March 24, 2011, 02:43:34 PM »
Well I just turned the computer on 10 minutes ago "as soon as I turned it on I came straight to the forums."

Where as last time I had it running all day. IDK if that matters. But either way the problem still is there. Do ya think I should just do a reinstall ?




EDIT :  Also if I choose to do a complete reinstall of MC is there a better way to wipe the entire computer completely clean "100%" or does cfdisk do that "100%" just by deleting the partitions?

Thanks, George
« Last Edit: March 24, 2011, 03:16:15 PM by cURIOUSgEORGE »
Logged

Offline maro

  • Hero Member
  • *****
  • Posts: 1228
Re: mounting failed can not allocate memory
« Reply #13 on: March 24, 2011, 06:30:50 PM »
AFAIK the 'fdisk' and 'cfdisk' tools are only working on the partition table (e.g. in the MBR) but do not format or wipe the device.

I personally have done something like sudo dd if=/dev/zero of=/dev/hda bs=2M as a "poor man's wipe". Of course one could use the 'wipe.tcz' extension instead, but I'm happy to use what is available in Core as in my case speed of execution is more important than security. Just be sure with the device name (e.g. '/dev/hda') you specify. Any typo on such a command can be very "painful" as you could destroy the content of a unintended device.

BTW, I believe that the typical 'mkfs.*' command also formats to content of the partition. But if you want to be 100% certain I don't see any harm in using a "wipe; fdisk; mkfs.*" sequence.
Logged

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: mounting failed can not allocate memory
« Reply #14 on: March 26, 2011, 04:36:14 AM »
Quote from: maro on March 24, 2011, 06:30:50 PM
sudo dd if=/dev/zero of=/dev/hda bs=2M

Curious, is there a particular reason to use 'bs=2M'? I would probably have chosen 'bs=512' - though I have mostly used 'cat /dev/zero > /dev/sda'.
Logged
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)
Pages: [1] 2   Go Up
« previous next »