Re: tar -> unresponsive machine

2013-03-01 Thread Vincent Lefevre
On 2013-02-28 16:39:23 +, Claudius Hubig wrote: > IOW, some more information on your setup (disk type, output of free > -m etc) might be helpful. I could reproduce the problem when Firefox was running. Here are two outputs of "free -m" while tar was running: ypig:~> free -m tota

Re: tar -> unresponsive machine

2013-03-01 Thread Morel Bérenger
Le Jeu 28 février 2013 19:22, Vincent Lefevre a écrit : > But isn't it possible to lower the priority automatically (without > an additional command like ionice) when a process takes all the I/O > resources. Perhaps this isn't clear, but what I mean is that a process > shouldn't take constantly all

Re: tar -> unresponsive machine

2013-02-28 Thread green
Darac Marjal wrote at 2013-02-28 10:50 -0600: > On Thu, Feb 28, 2013 at 11:38:23AM -0500, m...@neidorff.com wrote: > > Yes. You may want to change the "nice" level of the tar command so that > > it doesn't take up so much disk time. > > "nice tar" won't actually change how heavily tar uses the di

Re: tar -> unresponsive machine

2013-02-28 Thread Vincent Lefevre
Dear Claudius, On 2013-02-28 16:39:23 +, Claudius Hubig wrote: > Vincent Lefevre wrote: > > the whole machine becomes unresponsive, e.g. several dozens of seconds > > to do some operation (e.g. starting an xterm, or making Firefox react)? > > Depending on the IO priority of the tar command (p

Re: tar -> unresponsive machine

2013-02-28 Thread Vincent Lefevre
Thanks to all who replied. To answer some questions, it is a spinning hard drive, and here's mount information: /dev/disk/by-uuid/e3631277-c4d0-460e-a2a3-6de16013e050 on / type ext3 (rw,relatime,errors=remount-ro,barrier=1,data=ordered) and there was plenty of free RAM as usual (the machine has

Re: tar -> unresponsive machine

2013-02-28 Thread Dan Ritter
On Thu, Feb 28, 2013 at 05:27:19PM +0100, Vincent Lefevre wrote: > Is it normal that when using the "tar" command to create a big archive, > the whole machine becomes unresponsive, e.g. several dozens of seconds > to do some operation (e.g. starting an xterm, or making Firefox react)? > > htop sho

Re: tar -> unresponsive machine

2013-02-28 Thread Claudius Hubig
Dear Vincent, Vincent Lefevre wrote: > the whole machine becomes unresponsive, e.g. several dozens of seconds > to do some operation (e.g. starting an xterm, or making Firefox react)? Depending on the IO priority of the tar command (probably higher if run as root, check with ionice) and the disk

Re: tar -> unresponsive machine

2013-02-28 Thread Darac Marjal
On Thu, Feb 28, 2013 at 11:38:23AM -0500, m...@neidorff.com wrote: > > Is it normal that when using the "tar" command to create a big archive, > > the whole machine becomes unresponsive, e.g. several dozens of seconds > > to do some operation (e.g. starting an xterm, or making Firefox react)? > > >

Re: tar -> unresponsive machine

2013-02-28 Thread Jochen Spieker
Vincent Lefevre: > > Is it normal that when using the "tar" command to create a big archive, > the whole machine becomes unresponsive, e.g. several dozens of seconds > to do some operation (e.g. starting an xterm, or making Firefox react)? No. What storage device is tar writing to/reading from? J

Re: tar -> unresponsive machine

2013-02-28 Thread mark
> Is it normal that when using the "tar" command to create a big archive, > the whole machine becomes unresponsive, e.g. several dozens of seconds > to do some operation (e.g. starting an xterm, or making Firefox react)? > > htop shows that there is still plenty of memory and atop shows nothing > s