I am having redhat linux 5.3 (Tikanga) with GFS file system and its very very slow for executing ls -ls command also.Please see the below for 2minits 12 second takes.
Please help me to fix the issue.
Thanks,
Susi.S
Last edited by Corona688; 03-30-2012 at 12:07 PM..
Reason: code tags for code, please
We have an egrep search in a while loop.
egrep -w "$key" ${PICKUP_DIR}/new_update >> ${PICKUP_DIR}/update_record_new
${PICKUP_DIR}/new_update is 210 MB file
In each iteration, the egrep on an average takes around 50-60 seconds to search. Ther'es nothing significant in the loop other... (7 Replies)
Hi all
We have got issues with copying a 2.6 GB file from one folder to another folder.
Well, this is not the first issue we are having on the box currently, i will try to explain everything we have done from the past 2 days.
We got a message 2 days back saying that our Production is 98%... (3 Replies)
Hi,
I have a bit knowledge of GFS. As per my understanding it is the file system used in the cluster environment.
I have a question. Is GFS 6.2 same as GFS 2 files system?
Please some one clear my confusion.
Thanks in advance. (1 Reply)
hi guys
We are seeing weird issues on my Linux Suse 10, it has lotus 8.5
and 1 filesystem for OS and another for Lotus Database.
the issue is when the Lotus service starts wait on top is very high about 25% percent and in general CPU usage is very high
we found that when this happens if we... (0 Replies)
Please, I need help tuning my script. It works but it's too slow.
The code reads an acivity log file with 50.000 - 100.000 lines and filters error messages from it. The data in the actlog file look similar to this:
02/08/2011 00:25:01,ANR2034E QUERY MOUNT: No match found using this criteria.... (5 Replies)
There is a big problem with the server (VPS based on OpenVZ, CentOS 5, 3GB RAM). The problem is the following. The first 15-20 minutes after starting the server is operating normally, the load average is less than or about 1.0, but then begins to increase sharply% wa, then hovers around 95-99%.... (2 Replies)
I have identical M5000 machines that are needing to transfer very large amounts of data between them. These are fully loaded machines, and I've already checked IO, memory usage, etc... I get poor network performance even when the machines are idle or copying via loopback. The 10 GB NICs are... (7 Replies)
Discussion started by: christr
7 Replies
LEARN ABOUT DEBIAN
gfs_quota
gfs_quota(8) System Manager's Manual gfs_quota(8)NAME
gfs_quota - Manipulate GFS disk quotas
SYNOPSIS
gfs_quota <list|sync|get|limit|warn|check|init> [OPTION]...
DESCRIPTION
gfs_quota is used to examine and change quota values in a GFS filesystem. This command has a number of different actions.
ACTIONS
list List the contents of the quota file. Only IDs that have a non-zero hard limit, warn limit, or value are printed.
sync Sync any local quota changes to the quota file.
get Get the current data for the ID specified by the -u or -g argument.
limit Set the current hard limit for the ID specified by the -u or -g argument to the value specified by the -l argument on the specified
filesystem. The filesystem won't let the user or group use more than this much space. A value of zero here means that no limit is
enforced.
warn Set the current warn limit for the ID specified by the -u or -g argument to the value specified by the -l argument on the specified
filesystem. The filesystem will start complaining to the user or group when more than this much space is used. A value of zero
here means that the user won't ever be warned.
check Scan a filesystem and make sure that what's out there on the disk matches what's in the quota file. This is only accurate if the
filesystem is idle when this is running. If there is a mismatch, it is printed to stdout. Note: GFS quotas are transactional and a
quota check is not needed every time there is a system crash.
init Scan a filesystem and initialize the quota file with the values obtained from the scan. The filesystem should be idle when this is
run. You should only need to do this if you upgrade a pre-quota GFS filesystem (pre-GFS 5.1).
OPTIONS -b The units for disk space are filesystem blocks.
-d Don't include the space allocated to GFS' hidden files in what's reported for the root UID and GID values. This is useful if you're
trying to get the numbers reported by gfs_quota to match up with the numbers reported by du.
-f Directory
Specifies which filesystem to perform the action on.
-g GID Specifies the group ID for get, limit, or warn. It can be either the group name from the group file, or the GID number.
-h Print out a help message describing available options, then exit.
-k The units for disk space are kilobytes.
-l Size
Specifies the new value for the limit or warn actions. The value is assumed to be in the units specified by the -m, -k, -s, -b
arguments. The default is megabytes.
-m The units for disk space are megabytes. This is the default.
-n Don't try to resolve UIDs and GIDs into user and group names.
-s The units for disk space are sectors (512-byte blocks).
-u UID Specifies the user ID for get, limit, or warn. It can be either the username from the password file, or the UID number.
-V Print program version information, then exit.
EXAMPLE
To set the hard limit for user "nobody" to 1048576 kilobytes on filesystem /gfs0
gfs_quota limit -l 1048576 -k -u nobody -f /gfs0
gfs_quota(8)