mount problem

English Applications
#1

Hi,

A friend of mine mounted several ISOs on a server. As I had to free some memory I : rm -f some the ISOs directory (didn’t know that it was a mount)… But the space is still not freed. And now he doesn’t remember from where he mounted these ISO.
How can I do now to umount these ISOs properly.

Thanks.

Pat’

#2

-=WELCOME=- new poster, but something is wrong here:

-why do you feel you must free some memory? please, show us the output
of the command ‘free’…

-that said: unmount with the ‘umount’ command, see man umount (which is
very simple, just


umount {dir|device}

but, as said that won’t do much to empty out the RAM…

read more here
http://forums.opensuse.org/english/get-technical-help-here/applications/459538-please-clarify-memory-usage.html

or google “linux ate my ram”

–
DD http://tinyurl.com/DD-Caveat
openSUSE®, the “German Engineered Automobiles” of operating systems!

#3

On 2011-12-13 17:46, T0ky wrote:
>
> Hi,
>
> A friend of mine mounted several ISOs on a server. As I had to free
> some memory I : rm -f some the ISOs directory (didn’t know that it was a
> mount)… But the space is still not freed.

Well, removing files does not free RAM, ie, memory. If you refer to disk
space, it is not freed because those mounts are read-only, and in any case,
fictitious space, not real. They may dissapear from sight, but must be
there somehow.

> And now he doesn’t remember
> from where he mounted these ISO.

The bash history should show the command he used. Also, you can issue
“mount” to see what is mounted and where.

–
Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

#4

As Carlos said, issue the mount command and it will give you a list of mounts. The ones you are looking for involve /dev/loopN. You can umount either the device or the mount point, either will work.

Since it’s a server I won’t suggest you reboot. But if it’s a machine that you don’t care keeping up all the time, that would be a lazy and brute force way to umount.

#5

Yes sorry that was to free disk space and not memory space.
Ok thanks for your answers, the problem has been solved :).