[SOLVED] Would mounting a file system 'tree' to /mnt create a bottleneck?
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Would mounting a file system 'tree' to /mnt create a bottleneck?
A little embarassed to even ask this, but...
In the last few evenings, a typical Linux session has been creating a root file system on an SD card, mounted on /mnt/sd2 (partition2 of card). At the same time watching a movie from the HD, mounted at /mnt/HD.
I was wondering if everything going through /mnt might be slowing things down at all. The answer should be 'no' since everything is mounted to 'root' and that doesn't seem to be a problem, but maybe /mnt is handled differently than root.
Just ran an experiment with 'top' and seeing what is happening with mplayer and debian bootrap:
5562 walter 20 0 62980 23m 9.8m R 38.0 2.7 4:01.75 mplayer
1852 root 20 0 32048 12m 3728 S 3.0 1.4 2:08.92 Xorg
2020 walter 20 0 276m 14m 9m S 2.0 1.7 1:32.03 gnome-mplayer
2070 root 20 0 0 0 0 D 1.0 0.0 0:25.22 mmcqd/0
Can't really tell much from this, except that 'mmcqd/0' must be the bootstrap program unpacking things in the sd card. It kind of begs dumb question number 2: the unpacking process is crawling down the terminal screen, why is it not using more cpu to speed itself up? Must be the sd card can only accept writing to it at that speed, average about 1 second per package? Can't pull the card out at the moment, but pretty shure it's class 10, although suspiciously cheap from Eb.
Last edited by linux_walt; 02-04-2015 at 08:57 PM.
AFAIK, /mnt is a mount point, just like /, /var, /home, whatever else. It should not affect speed drastically.
What do you mean by crawling down the terminal screen? Text is slow to print? What terminal? I found that certain terminals are just slower than others. An example: hen I was working on a PSP game project a while back if I used GNOME Terminal, printing debugging messages would slow the terminal and PSP to a crawl; using xterm would be smooth as silk on both.
Hi goumba, apologies, by terminal I meant a remote ssh connection, I didn't make that clear.
Ah. Well, that's limited by other factors as well. Bandwidth, maybe a limitation on the sending end. I don't know your setup.
As veerain stated, printing output slows down the process as well. It has to send the text to the console, and in this case over ssh as well. Don't know what you're using, but if you don't need the output then disable it. Tools like gnu tar are actually silent except for an error, or unless you tell it to be verbose.
If you need the output, maybe piping to a file then check after the process is done will speed it up (not sure to the extent, or if that will even make a difference, never tried).
Hi goumba, I'm just going to accept the following:
Making several sub-mounts on /mnt is not really a problem.
Until someone figures out how to unpack things in parallel, a 1 Ghz processor is going to be slow, even if it has 2 ARMs (my first Linux joke!). Even slower if you are watching it remotely.
Another interesting thing has cropped up today, but will leave that for another question. Rhetorically speaking though, why in the heck are there 3 places to set environment variables for booting: default settings in kernel, boot.scr, and uEnv.txt. If it were windows I'd have given up by now, but since it's Linux, I'm sure there's an elegant complexity behind it all, just to make a simple task more interesting: 'this' is my monitor, my root partition is 'there', post your progress 'over here'. At the moment it feels like trying to coordinate three drunks. But that's a question for another post. Just a rant here.
Last edited by linux_walt; 02-05-2015 at 10:00 PM.