Re: [Feedback needed] Setting the right size for /tmp

2012-03-04 Thread Osamu Aoki
Hi,

I join too late but ...  (I do not use tmpfs for /tmp)

On Tue, Nov 29, 2011 at 04:13:05PM +, Camaleón wrote:
 On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
 
  I'm running an updated wheezy and today faced with this little
  problematic.
 
 (...)
 
  Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
  more situations like this in the future so some questions arise. As the
  current tmpfs default settings for /tmp seem a bit unrealistic (just %
  20 of the RAM?) for even doing common tasks:

This is just the default value for RAMTMP=yes in the /etc/default/rcS file.
You could have much bigger than RAM size as long as you have big enough
swap to support it.  You can do so via /etc/fstab. I once had 10GB tmpfs
with 4GB RAM so I could have DVD image on /tmp on tmpfs.  So 20% of RAM
is not good enough reason to reject tmpfs :-)

  1/ How many room should be set for a /tmp partition? I never had it
  one so I can't make any good estimation.

This depends on what you run.  DVD data may be as big as 5GB.

  2/ Would be better to simply disable tmpfs for /tmp? This is how I've
  been doing all these years.
  
  Any comments are welcome :-)
 
 Jerome, Bob, Dom... thank you all for your input :-)
 
 After carefully reading your suggestions I have decided to disable tpmfs 
 for /tmp and use the old method of having /tmp inside a partition.

Good.  As long as you have lots of RAM, most data written to disk stays
on RAM anyway as cached data if it is very short lived data.  So this
does not slow system.

But that may cause concern for disk wareout if you are using SSD.

 @Jerome, why not a dedicated partition to hold /tmp? Because I would have 
 to decide a fixed partition size and to be sincere, I don't think there 
 is any gain for this specific case, this is a small netbook I use mainly 
 for testing purposes so I don't need to be excesive careful with security 
 or privacy options nor need for speed :-). I prefer to keep things as 
 easy as possible.
 
 @Bob, thanks for pointing out that development mailing list thread. Very 
 interesting. By reading it, I see this is also issue for other users and 
 I have to agree that the defaults are a bit (to say at least) 
 conservative. I'm usually fine with Debian defaults and try to keep them 
 as long as  there is no compelling reason for editing them, e.g., when 
 they choke with common tasks, like making MC to crash for the simple fact 
 of exploring a 75 MiB compressed file :-) 
 
 @Dom, I agree, having /tmp on the same / directory is also the most 
 suitable deal for me.
 
 So, in the end I have set RAMTMP=no option at /etc/default/rcS.

But if you are on laptop with SSD and lots of memory, you may optimize
diskware by slowing down on disk cache flushing from memory.

 
http://www.debian.org/doc/manuals/debian-reference/ch09.en.html#_optimization_of_solid_state_drive

Anyway, even for mormal usage, use of noatime in mount option seems to
be one of the easiest system optimizer.

I stop using huge tmpfs for tmp since it gains nothing for me.

Regards,

Osamu


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120304091209.GA7714@localhost



Re: [Feedback needed] Setting the right size for /tmp

2012-03-04 Thread Camaleón
On Sun, 04 Mar 2012 18:12:09 +0900, Osamu Aoki wrote:

 Hi,
 
 I join too late but ...  (I do not use tmpfs for /tmp)

Time does not matter when good feedback comes to place :-)

 On Tue, Nov 29, 2011 at 04:13:05PM +, Camaleón wrote:
 On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:
 
  I'm running an updated wheezy and today faced with this little
  problematic.
 
 (...)
 
  Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
  more situations like this in the future so some questions arise. As
  the current tmpfs default settings for /tmp seem a bit unrealistic
  (just % 20 of the RAM?) for even doing common tasks:
 
 This is just the default value for RAMTMP=yes in the /etc/default/rcS
 file. You could have much bigger than RAM size as long as you have big
 enough swap to support it.  You can do so via /etc/fstab. I once had
 10GB tmpfs with 4GB RAM so I could have DVD image on /tmp on tmpfs.  So
 20% of RAM is not good enough reason to reject tmpfs :-)

(...)

True, but is still a bad default setting, IMO. Neither good for a 
system with 132 GiB of ram nor for another with 512 MiB ;-)

Besides, I can give tmpfs a chance (I can see the benefits of using it) 
but how could I mimic my current configuration with it? I mean, I don't 
like to have to worry for this, so now my /tmp -which resides at the 
/ partition- can make use of whatever available space is left on the 
disk.

How could I get this setting (that is, use as much space as there is and 
you need) with tmpfs? And will this be desirable or I'm going to have 
additional gotchas? :-)
 
 Jerome, Bob, Dom... thank you all for your input :-)
 
 After carefully reading your suggestions I have decided to disable
 tpmfs for /tmp and use the old method of having /tmp inside a
 partition.
 
 Good.  As long as you have lots of RAM, most data written to disk stays
 on RAM anyway as cached data if it is very short lived data.  So this
 does not slow system.
 
 But that may cause concern for disk wareout if you are using SSD.

Having as little as 2 GiB of ram in this system I can guess tmpfs will help 
to speed up things. Yup, I see what can be the benefits of using it... when/
if sanely tweaked.

(...)

 So, in the end I have set RAMTMP=no option at /etc/default/rcS.
 
 But if you are on laptop with SSD and lots of memory, you may optimize
 diskware by slowing down on disk cache flushing from memory.
 
  
 http://www.debian.org/doc/manuals/debian-reference/ch09.en.html#_optimization_of_solid_state_drive

Useful and understandable, but not my case. I'm still a bit reluctant in
using SSD disks with the current technology and design.
 
 Anyway, even for mormal usage, use of noatime in mount option seems to
 be one of the easiest system optimizer.
 
 I stop using huge tmpfs for tmp since it gains nothing for me.

Okay, so no more worries about this. I will keep the old-good default for 
/tmp then.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/jiviis$847$2...@dough.gmane.org



Re: [Feedback needed] Setting the right size for /tmp

2012-03-04 Thread Hans-J. Ullrich
 
  I stop using huge tmpfs for tmp since it gains nothing for me.
 
 Okay, so no more worries about this. I will keep the old-good default for
 /tmp then.
 
 Greetings,

I also got in problems, when k3b asked me for a temporary place for a 
temporary ISO. I choose /tmp (good choice for normal users!), but tmpfs 
(mounted to /tmp) just gave me about 600MB, too less for burning a DVD. 

So I removed tmpfs and stayed with good old /tmp on my / device, which gives 
me now the space I need.

So tmpfs still causes problems, no one thought of.

Hans


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201203041222.20621.hans.ullr...@loop.de



Re: [Feedback needed] Setting the right size for /tmp

2012-02-29 Thread Chris Bannister
On Wed, Feb 22, 2012 at 08:59:38AM +, Dom wrote:
 I think it would have been nice to have a warning of this change of
 behaviour. I have apt-listchanges installed and I'm sure it didn't
 notify me of any changes.

True, but there was a discussion on debian-devel titled:

  /tmp as tmpfs and consequence for imaging software

http://lists.debian.org/debian-devel/2011/11/threads.html#00501

-- 
Religion is excellent stuff for keeping common people quiet.
   -- Napoleon Bonaparte


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120229135430.GA13541@tal



Re: [Feedback needed] Setting the right size for /tmp

2012-02-29 Thread Chris Bannister
On Thu, Mar 01, 2012 at 02:54:30AM +1300, Chris Bannister wrote:
 On Wed, Feb 22, 2012 at 08:59:38AM +, Dom wrote:
  I think it would have been nice to have a warning of this change of
  behaviour. I have apt-listchanges installed and I'm sure it didn't
  notify me of any changes.
 
 True, but there was a discussion on debian-devel titled:
 
   /tmp as tmpfs and consequence for imaging software
 
 http://lists.debian.org/debian-devel/2011/11/threads.html#00501

Agh!!! sorry, should read whole thread first before replying.

-- 
Religion is excellent stuff for keeping common people quiet.
   -- Napoleon Bonaparte


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120229140029.GA13818@tal



Re: [Feedback needed] Setting the right size for /tmp

2012-02-22 Thread Dom

On 22/02/12 01:10, Seb wrote:


I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp.  What is the Debianish way to avoid using this
system for /tmp so that it uses whatever is available on /?


This seems to have been caused by a recent change to /etc/default/rcS in 
Wheezy. I was caught out by it too and had to reset it on a number of my 
systems.


Others on this list have already mentioned how to set it back to how it 
was, so I won't bother :)


I think it would have been nice to have a warning of this change of 
behaviour. I have apt-listchanges installed and I'm sure it didn't 
notify me of any changes.


--
Dom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4f44ae7a.5030...@rpdom.net



Re: [Feedback needed] Setting the right size for /tmp

2012-02-22 Thread Bob Proulx
Dom wrote:
 I think it would have been nice to have a warning of this change of
 behaviour. I have apt-listchanges installed and I'm sure it didn't
 notify me of any changes.

These types of changes are discussed in debian-devel.  In a released
system they would be in the release notes.  But since you are using
the development bits you would need to be reading the development
mailing list for that type of information.  Users of Sid/Unstable saw
this change some time ago.

Here is one long discussion thread on it.

  http://lists.debian.org/debian-devel/2011/11/msg00281.html

Bob


signature.asc
Description: Digital signature


Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread Seb
On Mon, 28 Nov 2011 19:44:46 +,
Dom to...@rpdom.net wrote:

 On 28/11/11 18:07, Camaleón wrote:
 Hello,

 I'm running an updated wheezy and today faced with this little
 problematic.

 While running Midnight Commander to open (on-the-fly decompression
 for browsing the archive) the kernel source package (a ~75 MiB
 .tar.bz2 file) I got this error:

 http://picpaste.com/mc-error-YXdyRawO.gif

 My Atom based netbook is not a powerful system but has 2 GiB of ram
 and 250 hard disk so, what was happening?

 df -H told me:

 S.ficheros Tamaño Usado Disp Uso% Montado en /dev/sda2 247G 7,7G 239G
 4% / tmpfs 5,3M 4,1k 5,3M 1% /lib/init/rw tmpfs 212M 664k 211M 1%
 /run tmpfs 5,3M 0 5,3M 0% /run/lock tmpfs 423M 423M 0 100% /tmp ---
 here!  udev 1,1G 0 1,1G 0% /dev tmpfs 423M 238k 423M 1% /run/shm

 Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
 more situations like this in the future so some questions arise. As
 the current tmpfs default settings for /tmp seem a bit unrealistic
 (just % 20 of the RAM?) for even doing common tasks:

 1/ How many room should be set for a /tmp partition? I never had it
 one so I can't make any good estimation.

 2/ Would be better to simply disable tmpfs for /tmp? This is how
 I've been doing all these years.

 Any comments are welcome :-)

 I don't use tmpfs for /tmp for a couple of reasons.

 Firstly, some of my PCs don't have much RAM (as low as 32MB), so it's
 just not practical, and on the others I sometimes store up to 4.7GB of
 files to put on DVDs.

 I know that I could create tmpfs filesystems bigger than that and they
 would use swap when physical RAM is exceeded, but that would slow the
 systems down to an almost unusable level.

 I'd rather either not have /tmp as a separate file system, or allocate
 at least 10GB to it. Disk is still cheaper than RAM, although slower.

I just discovered to my horror /tmp is handled by a tmpfs system that
allocates by default a percentage of RAM that happens to be too small
for my use of /tmp.  What is the Debianish way to avoid using this
system for /tmp so that it uses whatever is available on /?

Thanks,

-- 
Seb


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ehtnk702@kolob.subpolar.dyndns.org



Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread Bob Proulx
Seb wrote:
 I just discovered to my horror /tmp is handled by a tmpfs system that
 allocates by default a percentage of RAM that happens to be too small
 for my use of /tmp.  What is the Debianish way to avoid using this
 system for /tmp so that it uses whatever is available on /?

Set RAMTMP=no in the /etc/default/rcS file.

  # sed --in-place 's/RAMTMP=.*/RAMTMP=no/' /etc/default/rcS

Bob


signature.asc
Description: Digital signature


Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread Seb
On Tue, 21 Feb 2012 18:17:15 -0700,
Bob Proulx b...@proulx.com wrote:

 Seb wrote:
 I just discovered to my horror /tmp is handled by a tmpfs system that
 allocates by default a percentage of RAM that happens to be too small
 for my use of /tmp.  What is the Debianish way to avoid using this
 system for /tmp so that it uses whatever is available on /?

 Set RAMTMP=no in the /etc/default/rcS file.

   # sed --in-place 's/RAMTMP=.*/RAMTMP=no/' /etc/default/rcS

Thank you!  With this modification, does /tmp still get cleared after
each reboot?

Cheers,

-- 
Seb


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87aa4bk64v@kolob.subpolar.dyndns.org



Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread John Hasler
Seb writes:
 I just discovered to my horror /tmp is handled by a tmpfs system that
 allocates by default a percentage of RAM that happens to be too small
 for my use of /tmp.  What is the Debianish way to avoid using this
 system for /tmp so that it uses whatever is available on /?

Set TEMPDIR appropriately for the processes in question.
-- 
John Hasler


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ipiz1wcx@thumper.dhh.gt.org



Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread Bob Proulx
John Hasler wrote:
 Seb writes:
  I just discovered to my horror /tmp is handled by a tmpfs system that
  allocates by default a percentage of RAM that happens to be too small
  for my use of /tmp.  What is the Debianish way to avoid using this
  system for /tmp so that it uses whatever is available on /?
 
 Set TEMPDIR appropriately for the processes in question.

TEMPDIR?  Did you mean TMPDIR?

As in:

  mkdir -p $HOME/tmp
  export TMPDIR=$HOME/tmp

??  That is a useful configuration.  Although not every program is
coded to honor TMPDIR, most do.

Bob


signature.asc
Description: Digital signature


Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread Bob Proulx
Seb wrote:
 Bob Proulx wrote:
  Set RAMTMP=no in the /etc/default/rcS file.
# sed --in-place 's/RAMTMP=.*/RAMTMP=no/' /etc/default/rcS
 
 Thank you!  With this modification, does /tmp still get cleared after
 each reboot?

Yes.  That is controlled by TMPTIME=0 in the same /etc/default/rcS
file.  The /etc/init.d/mountall-bootclean.sh script reads it and acts
upon it.  But I recommend leaving it set to 0 and clearing files from
/tmp on reboot.  It's a good thing.

Bob


signature.asc
Description: Digital signature


Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread John Hasler
Bob writes:
 Did you mean TMPDIR?

Yes.  Note that you may want to provide for cleanup.  Consider tmpreaper.

 Although not every program is coded to honor TMPDIR...

File bug reports.
-- 
John Hasler


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87ehtn1rwb@thumper.dhh.gt.org



Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread Seb
On Tue, 21 Feb 2012 19:55:36 -0700,
Bob Proulx b...@proulx.com wrote:

 John Hasler wrote:
 Seb writes:  I just discovered to my horror /tmp is handled by a
 tmpfs system that  allocates by default a percentage of RAM that
 happens to be too small  for my use of /tmp.  What is the Debianish
 way to avoid using this  system for /tmp so that it uses whatever is
 available on /?

 Set TEMPDIR appropriately for the processes in question.

 TEMPDIR?  Did you mean TMPDIR?

 As in:

   mkdir -p $HOME/tmp export TMPDIR=$HOME/tmp

 ??  That is a useful configuration.  Although not every program is
 coded to honor TMPDIR, most do.

Yes, setting TMPDIR for programs requiring large storage seems the
saner way to go.

Thanks,

-- 
Seb


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8762ezjzqp@kolob.subpolar.dyndns.org



Re: [Feedback needed] Setting the right size for /tmp

2012-02-21 Thread Bob Proulx
John Hasler wrote:
 Bob writes:
  Did you mean TMPDIR?
 
 Yes.  Note that you may want to provide for cleanup.  Consider tmpreaper.

I like tmpreaper quite a bit.  It is great for /tmp and /var/tmp.  For
$HOME/tmp I don't think it is needed.  For $HOME/tmp just running find
$HOME/tmp with some combination of -atime or -ctime depending upon
noatime settings and then -delete.  And probably an @reboot helper.  A
lot of individual overhead that is already handled system wide with
/tmp.

Bob


signature.asc
Description: Digital signature


Re: [Feedback needed] Setting the right size for /tmp

2011-11-29 Thread Camaleón
On Mon, 28 Nov 2011 18:07:43 +, Camaleón wrote:

 I'm running an updated wheezy and today faced with this little
 problematic.

(...)

 Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
 more situations like this in the future so some questions arise. As the
 current tmpfs default settings for /tmp seem a bit unrealistic (just %
 20 of the RAM?) for even doing common tasks:
 
 1/ How many room should be set for a /tmp partition? I never had it
 one so I can't make any good estimation.
 
 2/ Would be better to simply disable tmpfs for /tmp? This is how I've
 been doing all these years.
 
 Any comments are welcome :-)

Jerome, Bob, Dom... thank you all for your input :-)

After carefully reading your suggestions I have decided to disable tpmfs 
for /tmp and use the old method of having /tmp inside a partition.

@Jerome, why not a dedicated partition to hold /tmp? Because I would have 
to decide a fixed partition size and to be sincere, I don't think there 
is any gain for this specific case, this is a small netbook I use mainly 
for testing purposes so I don't need to be excesive careful with security 
or privacy options nor need for speed :-). I prefer to keep things as 
easy as possible.

@Bob, thanks for pointing out that development mailing list thread. Very 
interesting. By reading it, I see this is also issue for other users and 
I have to agree that the defaults are a bit (to say at least) 
conservative. I'm usually fine with Debian defaults and try to keep them 
as long as  there is no compelling reason for editing them, e.g., when 
they choke with common tasks, like making MC to crash for the simple fact 
of exploring a 75 MiB compressed file :-) 

@Dom, I agree, having /tmp on the same / directory is also the most 
suitable deal for me.

So, in the end I have set RAMTMP=no option at /etc/default/rcS.

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.11.29.16.13...@gmail.com



[Feedback needed] Setting the right size for /tmp

2011-11-28 Thread Camaleón
Hello,

I'm running an updated wheezy and today faced with this little 
problematic.

While running Midnight Commander to open (on-the-fly decompression for 
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file) 
I got this error:

http://picpaste.com/mc-error-YXdyRawO.gif

My Atom based netbook is not a powerful system but has 2 GiB of ram and 
250 hard disk so, what was happening?

df -H told me:

S.ficheros Tamaño Usado  Disp Uso% Montado en
/dev/sda2247G  7,7G  239G   4% /
tmpfs5,3M  4,1k  5,3M   1% /lib/init/rw
tmpfs212M  664k  211M   1% /run
tmpfs5,3M 0  5,3M   0% /run/lock
tmpfs423M  423M 0 100% /tmp --- here!
udev 1,1G 0  1,1G   0% /dev
tmpfs423M  238k  423M   1% /run/shm

Okay, so /tmp is full. Fine. I know how to solve it but I can foresee 
more situations like this in the future so some questions arise. As the 
current tmpfs default settings for /tmp seem a bit unrealistic (just %
20 of the RAM?) for even doing common tasks:

1/ How many room should be set for a /tmp partition? I never had it one 
so I can't make any good estimation.

2/ Would be better to simply disable tmpfs for /tmp? This is how I've 
been doing all these years.

Any comments are welcome :-)

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/pan.2011.11.28.18.07...@gmail.com



Re: [Feedback needed] Setting the right size for /tmp

2011-11-28 Thread Jerome BENOIT



On 28/11/11 19:07, Camaleón wrote:

Hello,

I'm running an updated wheezy and today faced with this little
problematic.

While running Midnight Commander to open (on-the-fly decompression for
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file)
I got this error:

http://picpaste.com/mc-error-YXdyRawO.gif

My Atom based netbook is not a powerful system but has 2 GiB of ram and
250 hard disk so, what was happening?

df -H told me:

S.ficheros Tamaño Usado  Disp Uso% Montado en
/dev/sda2247G  7,7G  239G   4% /
tmpfs5,3M  4,1k  5,3M   1% /lib/init/rw
tmpfs212M  664k  211M   1% /run
tmpfs5,3M 0  5,3M   0% /run/lock
tmpfs423M  423M 0 100% /tmp --- here!
udev 1,1G 0  1,1G   0% /dev
tmpfs423M  238k  423M   1% /run/shm

Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
more situations like this in the future so some questions arise. As the
current tmpfs default settings for /tmp seem a bit unrealistic (just %
20 of the RAM?) for even doing common tasks:

1/ How many room should be set for a /tmp partition? I never had it one
so I can't make any good estimation.


on my  laptop my /tmp partition is about 225 Mb:
1] most of the time it is empty (right now only 1% is used);
2] I have a huge /scratch partition that is used when the /tmp
is not big enough;
3] I guess that the relevant size depends on what kind of file is used on fly 
(read, uncompress, compress, write, ...).



2/ Would be better to simply disable tmpfs for /tmp? This is how I've
been doing all these years.


I guess the /tmp mounted on a partition of /dev/sda is better idea than tmpfs 
one.
(having a sepated partion for /tmp is good idea.)



Any comments are welcome :-)


My 2 cents,
Jerome



Greetings,




--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ed3dbed.30...@rezozer.net



Re: [Feedback needed] Setting the right size for /tmp

2011-11-28 Thread Bob Proulx
Camaleón wrote:
 /dev/sda2247G  7,7G  239G   4% /
 tmpfs423M  423M 0 100% /tmp   --- here!

 Okay, so /tmp is full. Fine. ...

Especially when you have 250G of space it seems egregious to clamp it
down to only 423M.

 1/ How many room should be set for a /tmp partition? I never had it one 
 so I can't make any good estimation.

It is so application space dependent that no one single answer can be
correct for everyone.

 2/ Would be better to simply disable tmpfs for /tmp? This is how I've 
 been doing all these years.

I have yet to find an acceptable tmpfs configuration that works for me
for use as /tmp.  I have tried but so far none of the options I have
tried have worked out well.

On my laptop I don't have a separate /tmp partition and simply share
space with the root filesystem so that all available space is
available to me.  I would do that for your netbook if I were using it.

On servers I always set up lvm and so set up an appropriately sized
partition just for /tmp.  However appropriately varies greatly
depending upon the machine and task.  Since it is lvm I can resize it
as needed to tune it for the machine and applications.

 Any comments are welcome :-)

If you want to read a *lot* of strong opinions you can browser through
this recent thread on debian-devel about it:

  http://lists.debian.org/debian-devel/2011/11/msg00281.html

Bob


signature.asc
Description: Digital signature


Re: [Feedback needed] Setting the right size for /tmp

2011-11-28 Thread Dom

On 28/11/11 18:07, Camaleón wrote:

Hello,

I'm running an updated wheezy and today faced with this little
problematic.

While running Midnight Commander to open (on-the-fly decompression for
browsing the archive) the kernel source package (a ~75 MiB .tar.bz2 file)
I got this error:

http://picpaste.com/mc-error-YXdyRawO.gif

My Atom based netbook is not a powerful system but has 2 GiB of ram and
250 hard disk so, what was happening?

df -H told me:

S.ficheros Tamaño Usado  Disp Uso% Montado en
/dev/sda2247G  7,7G  239G   4% /
tmpfs5,3M  4,1k  5,3M   1% /lib/init/rw
tmpfs212M  664k  211M   1% /run
tmpfs5,3M 0  5,3M   0% /run/lock
tmpfs423M  423M 0 100% /tmp --- here!
udev 1,1G 0  1,1G   0% /dev
tmpfs423M  238k  423M   1% /run/shm

Okay, so /tmp is full. Fine. I know how to solve it but I can foresee
more situations like this in the future so some questions arise. As the
current tmpfs default settings for /tmp seem a bit unrealistic (just %
20 of the RAM?) for even doing common tasks:

1/ How many room should be set for a /tmp partition? I never had it one
so I can't make any good estimation.

2/ Would be better to simply disable tmpfs for /tmp? This is how I've
been doing all these years.

Any comments are welcome :-)


I don't use tmpfs for /tmp for a couple of reasons.

Firstly, some of my PCs don't have much RAM (as low as 32MB), so it's 
just not practical, and on the others I sometimes store up to 4.7GB of 
files to put on DVDs.


I know that I could create tmpfs filesystems bigger than that and they 
would use swap when physical RAM is exceeded, but that would slow the 
systems down to an almost unusable level.


I'd rather either not have /tmp as a separate file system, or allocate 
at least 10GB to it. Disk is still cheaper than RAM, although slower.


--
Dom


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Archive: http://lists.debian.org/4ed3e4ae.8010...@rpdom.net