WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: Confusion using NFS  (Read 1507 times)

Offline tsaukpaetra

  • Newbie
  • *
  • Posts: 10
Confusion using NFS
« on: July 07, 2012, 03:04:09 AM »
Using latest stable TinyCore from the downloads section, I managed to get it to PXEBoot and use my NFS server for persistence and package storage.
However, I am noticing something strange about the memory usage in this setup: Loading up packages has the same effect as downloading them to the /tmp/tce directory (apparently still located in RAM per the cloud-mode)!
I know that the NFS mount works fine, because all of my packages/profile load correctly on a my dev system (which has enough memory to hold it all), and everything (with exception to the memory issue) works as expected.
I was under the impression that by enabling a persistent storage method would alleviate this "temporary caching" thing, but it does not seem to be the case. As a proof of concept, I omitted the      tce=nfs/tce      boot option (thereby stopping the persistent storage feature) but keeping the NFS mount. My mem free at the end stabilizes at 99636 (I'm assuming kb, top doesn't specify). After using the normal boot options, I am left with only 6344 kb free ram. I know about 15Mb has been take by the firefox profile, as reported by du, but I still have 84 mb to account for, which would approximate (almost) the total size of the packages loaded.

Ideally, what I would like is the packages to be directly mounted from the NFS share so they don't have to be resident in memory, thereby freeing the memory it would take to cache them and actually allowing X to run properly (apparently it just can't take it ;) ). I'm not too worried about loosing connection to the NFS Server (if that happens, the network is down and the terminal I'm running Tiny Core would be useless anyways), so that's a non-issue.

Any hints on where I've gone wrong or assumed incorrectly?
(On a side note, Tiny Core is extremely awesome, claiming the first place on my list of distros that my thin clients boot properly and without much hubaloo. The other is the DSL distro with rootfs embedded in initrd)

Offline tinypoodle

  • Hero Member
  • *****
  • Posts: 3857
Re: Confusion using NFS
« Reply #1 on: July 07, 2012, 06:09:45 AM »
Before measuring memory do 'sudo cache-clear'.
To measure storage space using memory do 'df|grep rootfs'.
"Software gets slower faster than hardware gets faster." Niklaus Wirth - A Plea for Lean Software (1995)

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11041
Re: Confusion using NFS
« Reply #2 on: July 07, 2012, 07:52:28 AM »
Double-check that there's no copy2fs.flg or .lst, they would force the copy to RAM.
The only barriers that can stop you are the ones you create yourself.

Offline tsaukpaetra

  • Newbie
  • *
  • Posts: 10
Re: Confusion using NFS
« Reply #3 on: July 07, 2012, 03:06:49 PM »
Well, the RootFS is size: 102M, Used: 30M, Available: 71.9M
After doing the sudo cach-clear, I have 47988 used and 68016 free.
But with that much free memory now, why would X not start?
Actually, come to think of it, Xvesa does start in 640x480x8 mode (which is probably a configuration error somewhere), but Xorg does not. I do remember someone mentioning that some gfx cards don't work right in Xorg.