I have OpenSUSE 11.3 and need to resize a /tmp file. Actually, I have to add
5GB to it.
Is there any easy way to do it?
Thanks a lot!
Nebojsa
__________ Information from ESET Smart Security, version of virus signature database 5683 (20101208) __________
The message was checked by ESET Smart Security.
what are you trying to do? and why?
normally there is no need to mess with anything in /tmp, which might
be in use by the system...
if the system needs it larger it will happen, like magic..
--
see caveat: http://tinyurl.com/6aagco
DenverD via Thunderbird 2.0.0.23 (20090817), KDE 3.5.7 "release
72-11", openSUSE Linux 10.3, 2.6.22.19-0.4-default #1 SMP i686 athlon
> On 02/20/2011 07:02 PM, Nebojsa Subanovic wrote:
>> Hi folks!
>>
>> I have OpenSUSE 11.3 and need to resize a /tmp file. Actually, I have to
>> add 5GB to it.
>> Is there any easy way to do it?
>
> what are you trying to do? and why?
>
> normally there is no need to mess with anything in /tmp, which might
> be in use by the system...
>
> if the system needs it larger it will happen, like magic..
Only if /tmp is a tmpfs filesystem.
--
Lew Pitcher
Master Codewright & JOAT-in-training | Registered Linux User #112576
Me: http://pitcher.digitalfreehold.ca/ | Just Linux: http://justlinux.ca/
---------- Slackware - Because I know what I'm doing. ------
Do you mean that the /tmp partition is running out of space?
The default setup is to have one partition for /home and another for /
(in other words, everything else including /tmp shares the rest of the
disk space.)
If you have created your own /tmp partition then you presumably had a
good reason to do that and you presumably would also know how to manage
and resize partitions.
So I'm a bit confused. Can you let us know:
1. Is /tmp filling up? What is filling it up? If it is log files then
you probably have some other problem that needs fixing, and allocating
more space to /tmp won't solve it, because sooner or later it'll fill up
again.
2. What is the output of the following two commands:
mount
and
df -h
?
3. If the problem is that you have a very large logfile in /tmp and you
need to shrink that file, how you do that depends on what program is
generating the file and whether you can take that program down
temporarily, and whether a reboot is possible (not a problem on a home
machine but can be a problem on a server.) e.g. some programs such as
Oracle are generate logfiles many GB in size over time, some of these
files can be safely trimmed with the db running but some will need the
database to be stopped temporarily.
--
Ulick Magee
Free software and free formats for free information for free people.
LibreOffice for Windows/OSX/Linux: www.documentfoundation.org/download
openSUSE Linux: http://en.opensuse.org
> 1. Is /tmp filling up? What is filling it up? If it is log files ...
Log files? Which applications would be writing log files to /tmp ?
I get such response:
"wgrib is not on your path or can not write to /tmp/g11065.tmp (full disk or
permissions)"
But when the file is small, it works properly.
So, I concluded that the tmp folder is to small and wanted to make it
bigger.
Regards!
> I run a numrical model and in one phase it creates a temporary file
> which puts into tmp file.
> When this file extends some amount the tmp doesn't permit the model to
> write in it.
>
> I get such response:
>
> "wgrib is not on your path or can not write to /tmp/g11065.tmp (full
> disk or permissions)"
>
> But when the file is small, it works properly.
>
> So, I concluded that the tmp folder is to small and wanted to make it
> bigger.
What does it mean for a folder to be too small?
I believe the message is trying to tell you is that you've run out of
room in the partition in which /tmp resides - that would probably be /
though it could be a partition of it's own.
> Hi folks!
>
> I have OpenSUSE 11.3 and need to resize a /tmp file. Actually, I have to
> add 5GB to it.
> Is there any easy way to do it?
>
Yeah easy enough if you have the disk space. Create a new partition (can be
on same old hard drive or a new hard drive) and mount it at /tmp. Make it as
big as you want. Yast->partitioner can do all this.
The less easy way would be to convert your setup to LVM. I believe you could
then 'transparently' add in more disk space by assigning more Physical
Volumes to the LVM group, at will. I don't have much experience there but I
don't see why it wouldn't work for /tmp.
HTH :)
> Thanks a lot!
>
> Nebojsa
>> I believe the message is trying to tell you is that you've run out of
>> room in the partition in which /tmp resides - that would probably be /
>> though it could be a partition of it's own.
>>
>But there's only one partition on the hard disc. So, if there's no
>limitation in tmp itself, than it can use all 390GB of the rest free space.
>
How big is the actual file?
--
Regards
David
fundamentalism (n.): fund = give cash to; amentalism = brainlessness
To protect your friend's email addresses from spammers please delete all
old email addresses and send bulk emails as "Bcc". Many thanks.
It can go up to 5GB. I've noticed when it is <1GB it works and when it is
>2GB it fails. Didn't check for intermeditate amounts.
Perhaps it is not problem in tmp size but in file size permission?
>> How big is the actual file?
>
>It can go up to 5GB. I've noticed when it is <1GB it works and when it is
> >2GB it fails. Didn't check for intermeditate amounts.
>Perhaps it is not problem in tmp size but in file size permission?
>
What FS are you using? If the /tmp directory is on an NTFS file system
you could be running into the M$ 2GB limit.
Well, I do not know the answer. Where I can see what FS I'm using?
Anyway, I've checked the partitions:
/dev/sda1 457GB Linux native
/dev/sda2 7.92GB Extended
/dev/sda5 7.92GB Linux swap
Regards
Nebojsa
Badly written ones :) especially if CLEAR_TMP_DIRS_AT_BOOTUP="yes" is
set in /etc/sysconfig/cron :)
You're right, I was thinking of /var/log, but most users have everything
except /home on the same partition anyway so it makes no difference to
them whether it's /var or /tmp that fills up all the free space on / .
do these in a terminal, and return the output back to here:
df -h
sudo /sbin/fdisk -l
cat /proc/partitions
cat /etc/fstab
mount
i guess the partition on which you have /tmp is becomming full OR is
using a file system which limits the max size of the file..
--
LSMFT
Force shits upon the Back of Reason...
Ben Franklin-
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x6d5fc73e
Device Boot Start End Blocks Id System
/dev/sda1 * 1 59767 480078396 83 Linux
/dev/sda2 59768 60801 8305605 5 Extended
/dev/sda5 59768 60801 8305573+ 82 Linux swap / Solaris
major minor #blocks name
8 0 488386584 sda
8 1 480078396 sda1
8 2 1 sda2
8 5 8305573 sda5
/dev/disk/by-id/ata-TOSHIBA_MK5056GSY_408AFAI2S-part5 swap
swap defaults 0 0
/dev/disk/by-id/ata-TOSHIBA_MK5056GSY_408AFAI2S-part1 /
ext4 acl,user_xattr 1 1
proc /proc proc defaults 0
0
sysfs /sys sysfs noauto 0
0
debugfs /sys/kernel/debug debugfs noauto 0
0
usbfs /proc/bus/usb usbfs noauto 0
0
devpts /dev/pts devpts mode=0620,gid=5 0
0
/dev/sda1 on / type ext4 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
devtmpfs on /dev type devtmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,mode=1777)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
securityfs on /sys/kernel/security type securityfs (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
gvfs-fuse-daemon on /home/nebojsa/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev,user=nebojsa)
Can't adjusti it cause this numerical model is a kind of "black box". I can
only adjust some input parametars, but not the model itself.
> Filesystem Size Used Avail Use% Mounted on
> /dev/sda1 451G 30G 399G 7% /
> devtmpfs 1.9G 256K 1.9G 1% /dev
> tmpfs 1.9G 216K 1.9G 1% /dev/shm
[snip]
> Device Boot Start End Blocks Id System
> /dev/sda1 * 1 59767 480078396 83 Linux
> /dev/sda2 59768 60801 8305605 5 Extended
> /dev/sda5 59768 60801 8305573+ 82 Linux swap /
[snip]
> /dev/disk/by-id/ata-TOSHIBA_MK5056GSY_408AFAI2S-part5 swap
> swap defaults 0 0
> /dev/disk/by-id/ata-TOSHIBA_MK5056GSY_408AFAI2S-part1 /
> ext4 acl,user_xattr 1 1
> proc /proc proc defaults
> 0 0
> sysfs /sys sysfs noauto
> 0 0
> debugfs /sys/kernel/debug debugfs noauto
> 0 0
> usbfs /proc/bus/usb usbfs noauto
> 0 0
> devpts /dev/pts devpts mode=0620,gid=5
> 0 0
[snip]
It appears that, in your installation, the entire directory tree
(including /tmp) is held within the /dev/sda1 filesystem space. In other
words, you don't have a separate /tmp filesystem, and space allocated to
files in /tmp will come from the freespace of /dev/sda1.
It also appears that you don't have any additional disk freespace, as your
entire drive is divided into /dev/sda1 for the complete filesystem
and /dev/sda5 for paging space.
Your /dev/sda1 has 399Gb (that's GigaBytes) of freespace at the moment.
Are you telling us that your temporary file can reach up to 399Gb in size?
That's how big it would have to be to run out of filesystem space.
I think that you might have run into a per-user or per-process filesize
limit rather than the hard-disk's freespace limit.
If it fills up the disk , chances are that the file will be appended. If
so: above actions will reroute to /dev/null.
If the file gets recreated: no luck. An 'friendly' mail to the
developers might help in that scenario.
Good luck!
--
Kind regards, JT
This machine is used only for run this numrical model so I wanted to give it
all possible recources.
> I think that you might have run into a per-user or per-process filesize
> limit rather than the hard-disk's freespace limit.
It seems. How can I check/change this limitation.
Regards!
Nebojsa
What does 'ulimit -a' report?
CORRECT>unlimit -a (y|n|e|a)?
>> What does 'ulimit -a' report?
>
> CORRECT>unlimit -a (y|n|e|a)?
Not 'unlimit' but 'ulimit'
That all looks good - unlimited file size. I noted on another reply that
it looks like your file system is ext4 which should handle files to
several TB.
I'm afraid I'm about out of ideas. Anyone else?
Big problem:
either 201102200000_nmm_wrfout_d01.grb is missing or not a grib file
wgrib is not on your path or can not write to /tmp/g11065.tmp (full disk or
permissions)
This grb file exists in every run og the model. But when this grb file is
<1GB the model works proprely and when is >2GB it fails with this messagge.
Do not know for intermediate sizes.
Just for grins, let's see if you can even create a 5gb file. Try the
following command to attempt to create one. Be patient it may take a
while - if you can't stand it or if it goes beyond, say, 5 minutes, just
kill it.
dd ibs=1024 obs=1024 count=5242880 of=junk.tmp if=/dev/zero
should create a 5gb file - check it's size with ls.
BTW - I'm expecting that this will work - if so, I don't have any more
ideas.
I wouldn't be surprised if there is an error in the code (pointer size
too small)
a signed 32-bit integer allows 2^31 positive values, if this is used as
a pointer referencing data bytes in a file it will fail if the file is
larger than 2GB.
http://dss.ucar.edu/datasets/common/ecmwf/ERA40/software/wgribdescription.html
Do you have wgrib installed?
Is this what you are using it for?
http://www.cpc.ncep.noaa.gov/products/wesley/wgrib.html
Why are you using a Windows product to access this newsgroup, when you
have Linux installed?
WLS
>User-Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:2.0b12pre) Gecko/20110221 Firefox/4.0b12pre SeaMonkey/2.1b3pre
[...]
>
>Why are you using a Windows product to access this newsgroup, when you
>have Linux installed?
>
Since when has Firefox been a Windoze product?
> Nebojsa Subanovic wrote:
>> Perhaps this could help: the numerical model fails with this messagge:
>>
>> Big problem:
>> either 201102200000_nmm_wrfout_d01.grb is missing or not a grib file
>> wgrib is not on your path or can not write to /tmp/g11065.tmp (full
>> disk or permissions)
>>
>> This grb file exists in every run og the model. But when this grb file
>> is <1GB the model works proprely and when is>2GB it fails with this
>> messagge. Do not know for intermediate sizes.
>>
>>
>>
>> __________ Information from ESET Smart Security, version of virus
>> signature database 5683 (20101208) __________
>>
>> The message was checked by ESET Smart Security.
>>
>> http://www.eset.com
>>
>>
>>
>>
> Looks to me like the answer is "wgrib is not in your path"
>
> http://dss.ucar.edu/datasets/common/ecmwf/ERA40/software/
wgribdescription.html
>
> Do you have wgrib installed?
Thanks WLS - it would seem this is the entire problem:
Wgrib is limited to 2 GB files when used on 32-bit machines such as a
pentium-4. (2 GB is the maximum value of a 32-bit integer.) On 64-bit
machines, the 2 gig limit is replaced by a really big number.
ok, i'll try this.
Have you been running this software under another user maybe? There
might be a left-over file from that run. If this run is trying to remove
a /tmp-file of another user I would expect a permission issue.
--
Kind regards, JT
The OP is using a Windows product to access the NG.
Microsoft Outlook Express 6.00.2900.5931
Damn, I thought I had you kill filed. Bye!
WLS
Or tmpfs, which is also often used for /tmp
(which essentially means /tmp is RAM based, not on disk).
--
******************************************************************
** Eef Hartman, Delft University of Technology, dept. SSC/ICT **
** e-mail: E.J.M....@tudelft.nl - phone: +31-15-27 82525 **
******************************************************************
I read the group from Windows, so what! My Linux machine is busy doing
other things.
Well, it created 5GB file in /tmp...So, tmp by itself is not problem.
What now?
Thanks all for help!
> Hi folks!
>
> I have OpenSUSE 11.3 and need to resize a /tmp file. Actually, I have to
> add 5GB to it.
> Is there any easy way to do it?
>
> Thanks a lot!
>
> Nebojsa
>
>
>
> __________ Information from ESET Smart Security, version of virus
> signature database 5683 (20101208) __________
>
> The message was checked by ESET Smart Security.
>
> http://www.eset.com
Any chance that there are user or group quotas set on your system?
Please read the thread before you make new postulatings...
We sorted it out. The issue is that the software only supports 2gb files.