Mailinglist Archive: opensuse-factory (1578 mails)
| < Previous | Next > |
[opensuse-factory] Timewarp (was Re: [12.1] massive data loss in /var/tmp/)
- From: Linda Walsh <suse@xxxxxxxxx>
- Date: Sat, 19 Nov 2011 15:13:01 -0800
- Message-id: <4EC837FD.50102@tlinx.org>
Cristian Rodríguez wrote:
----
[*ouch*....that hurts.]
I don't have hmmm, actually I do have gigabytes hmmm...
I was gonna complain because I use /tmp to tranfer tars of user dirs that
can be (under pathological cases) up to 20-30GB, but USUALLY are <5GB (they are roaming profiles, so I prefer to keep them under 2-3GB)...
And for a second I thought those were 'large' files...and to have them
consume memory and swap.....but then ...I realized, I'm in 2011, not 199x.
*sigh*...Actually, wait-- it STILL could be a problem...
Still... 2-3 GB can be large -- photoshop had a cow with a 2.6GB
tif this morning -- thought I was 'hosed'...couldn't open it for the longest time...(some layer had been 'distorted' and as a result grew to enormous proportions -- thought it wasn't visible as it was contained in a
small ~100px mask....the layer had been a pouring of a paintbucket...
Photoshop stores such things as bitmasks...it started as a 4.5Kx4.5K image, so each such "fill layer" (in quotes, cuz there is an official
fill layer type, that if chosen, won't create the bit mask, but it's
not the default, and it's not an option in the default new-layer dialog).
So when it got resized -- apparently via 'perspective', instead of distort, a small shift at one end made the other end VERY large...
from the size increase, (1.1G added, and PS gets about 75% compression
on a unicolor layer, , it added about 4.4G of pixels, or apparently
blew up my 'solid black color for my 100px^2 shape to a 69,000px^2
32 bit/px, image. Oddly, it just hung, trying to open (disk trashing
with PS's TMP files...as it self monitors physmem usage and then
does it's own spill's to tmp. Had 11G free and 0 swap usage (on an SSD).
Hmmm...
Right now, for a 1.5G image, PS is using 163GB in /tmp (actually a per-user tmp)....and THAT actually would be a problem if it was on a tmpfs... as I don't have SWAP configged at 4-8X available memory.
May not be an issue...BUT..that had been done on windows, I'd be screwed.
To edit images I have to keep almost half my hard disk free for Adobe Photoshop 5 -- unbelievable.
What a Frickin pig!
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
It is unrelated to this topic and /tmp is no longer a directory that
resides in your hard disk, but in shared memory, if you are running out
of memory, it will be put in swap. there is nothing you have to be
worried or configure, the kernel will do the work for you.
----
[*ouch*....that hurts.]
I don't have hmmm, actually I do have gigabytes hmmm...
I was gonna complain because I use /tmp to tranfer tars of user dirs that
can be (under pathological cases) up to 20-30GB, but USUALLY are <5GB (they are roaming profiles, so I prefer to keep them under 2-3GB)...
And for a second I thought those were 'large' files...and to have them
consume memory and swap.....but then ...I realized, I'm in 2011, not 199x.
*sigh*...Actually, wait-- it STILL could be a problem...
Still... 2-3 GB can be large -- photoshop had a cow with a 2.6GB
tif this morning -- thought I was 'hosed'...couldn't open it for the longest time...(some layer had been 'distorted' and as a result grew to enormous proportions -- thought it wasn't visible as it was contained in a
small ~100px mask....the layer had been a pouring of a paintbucket...
Photoshop stores such things as bitmasks...it started as a 4.5Kx4.5K image, so each such "fill layer" (in quotes, cuz there is an official
fill layer type, that if chosen, won't create the bit mask, but it's
not the default, and it's not an option in the default new-layer dialog).
So when it got resized -- apparently via 'perspective', instead of distort, a small shift at one end made the other end VERY large...
from the size increase, (1.1G added, and PS gets about 75% compression
on a unicolor layer, , it added about 4.4G of pixels, or apparently
blew up my 'solid black color for my 100px^2 shape to a 69,000px^2
32 bit/px, image. Oddly, it just hung, trying to open (disk trashing
with PS's TMP files...as it self monitors physmem usage and then
does it's own spill's to tmp. Had 11G free and 0 swap usage (on an SSD).
Hmmm...
Right now, for a 1.5G image, PS is using 163GB in /tmp (actually a per-user tmp)....and THAT actually would be a problem if it was on a tmpfs... as I don't have SWAP configged at 4-8X available memory.
May not be an issue...BUT..that had been done on windows, I'd be screwed.
To edit images I have to keep almost half my hard disk free for Adobe Photoshop 5 -- unbelievable.
What a Frickin pig!
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx
| < Previous | Next > |