Sponsored Content
Top Forums UNIX for Dummies Questions & Answers ls is taking long time to list Post 302717943 by Don Cragun on Thursday 18th of October 2012 06:09:41 PM
Old 10-18-2012
When you use NFS to access remote files, it keeps a cache of recently accessed blocks. As time goes by the cache is filled with more recently accessed files. So the first access when the cache is empty is relatively slow and later reads of the same page are relatively fast until those pages have been pushed out of the cache.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

fetchmail taking long time to fetchmail...

Hi peeps, We are having around 60 users. The time set to retrieve the mail is 300 sec. But it's taking around 1 hour to deliver mails. I am using debian sarge 3.1. any clues? And how it will affect if I decrease the time? My machine has got 1 p4 3.0 GHZ processor and 1 GB ram. The home... (2 Replies)
Discussion started by: squid04
2 Replies

2. Red Hat

login process taking a long time

I'm having a bit of a login performance issue.. wondering if anyone has any ideas where I might look. Here's the scenario... Linux Red Hat ES 4 update 5 regardless of where I login from (ssh or on the text console) after providing the password the system seems to pause for between 30... (4 Replies)
Discussion started by: retlaw
4 Replies

3. Shell Programming and Scripting

For Loop Taking Too Long

I'm new from UNIX scripting. Please help. I have about 10,000 files from the $ROOTDIR/scp/inbox/string1 directory to compare with the 50 files from /$ROOTDIR/output/tma/pnt/bad/string1/ directory and it takes about 2 hours plus to complete the for loop. Is there a better way to re-write the... (5 Replies)
Discussion started by: hanie123
5 Replies

4. Shell Programming and Scripting

<AIX>Problem in purge script, taking very very long time to complete 18.30hrs

Hi, I have here a script which is used to purge older files/directories based on defined purge period. The script consists of 45 find commands, where each command will need to traverse through more than a million directories. Therefore a single find command executes around 22-25 mins... (7 Replies)
Discussion started by: sravicha
7 Replies

5. UNIX for Dummies Questions & Answers

gref -f taking long time for big file

grep -f taking long time to compare for big files, any alternate for fast check I am using grep -f file1 file2 to check - to ckeck dups/common rows prsents. But my files contains file1 contains 5gb and file 2 contains 50 mb and its taking such a long time to compare the files. Do we have any... (10 Replies)
Discussion started by: gkskumar
10 Replies

6. UNIX for Dummies Questions & Answers

Job is taking long time

Hi , We have 20 jobs are scheduled. In that one of our job is taking long time ,it's not completing. If we are not terminating it's running infinity time actually the job completion time is 5 minutes. The job is deleting some records from the table and two insert statements and one select... (7 Replies)
Discussion started by: ajaykumarkona
7 Replies

7. Solaris

How to find out bottleneck if system is taking long time in gzip

Dear All, OS = Solaris 5.10 Hardware Sun Fire T2000 with 1 Ghz quode core We have oracle application 11i with 10g database. When ever i am trying to take cold backup of database with 55GB size its taking long time to finish. As the application is down nobody is using the server at all... (8 Replies)
Discussion started by: yoojamu
8 Replies

8. Shell Programming and Scripting

While loop problem taking too long

while read myhosts do while read discovered do echo "$discovered" done < $LOGFILE | grep -Pi "|" | egrep... (7 Replies)
Discussion started by: SkySmart
7 Replies

9. Shell Programming and Scripting

Long list file display different time format.

Hi Gurus, I have some weird issue. when using ls -l the result shows different time format: -rw-r--r-- 1 abc gourp1 3032605576 Jun 14 2013 abc -rw-rw-r-- 1 abc gourp1 1689948832 Aug 10 06:22 abc one display 2013 which is year; another one displays 06:22 which is time. ... (4 Replies)
Discussion started by: ken6503
4 Replies

10. Shell Programming and Scripting

Rm -rf is taking very long, will it timeout?

I have so many (hundreds of thousands) files and directories within this one specific directory that my "rm -rf" command to delete them has been taking forever. I did this via the SSH, my question is: if my SSH connection times out before rm -rf finishes, will it continue to delete all of those... (5 Replies)
Discussion started by: phpchick
5 Replies
FS_CHECKSERVERS(1)					       AFS Command Reference						FS_CHECKSERVERS(1)

NAME
fs_checkservers - Displays the status of server machines SYNOPSIS
fs checkservers [-cell <cell to check>] [-all] [-fast] [-interval <seconds between probes>] [-help] fs checks [-c <cell to check>] [-a] [-f] [-i <seconds between probes>] [-h] DESCRIPTION
The fs checkservers command reports whether certain AFS server machines are accessible from the local client machine. The machines belong to one of two classes, and the Cache Manager maintains a list of them in kernel memory: o The database server machines for every cell listed in the local /etc/openafs/CellServDB file, plus any machines added to the memory list by the fs newcell command since the last reboot. o All file server machines the Cache Manager has recently contacted, and which it probably needs to contact again soon. In most cases, the Cache Manager holds a callback on a file or volume fetched from the machine. If the Cache Manager is unable to contact the vlserver process on a database server machine or the fileserver process on a file server machine, it marks the machine as inaccessible. (Actually, if a file server machine is multihomed, the Cache Manager attempts to contact all of the machine's interfaces, and only marks the machine as down if the fileserver fails to reply via any of them.) The Cache Manager then periodically (by default, every three minutes) sends a probe to each marked machine, to see if it is still inaccessible. If a previously inaccessible machine responds, the Cache Manager marks it as accessible and no longer sends the periodic probes to it. The fs checkservers command updates the list of inaccessible machines by having the Cache Manager probe a specified set of them: o By default, only machines that are marked inaccessible and belong to the local cell (the cell listed in the local /etc/openafs/ThisCell file). o If the -cell argument is included, only machines that are marked inaccessible and belong to the specified cell. o If the -all flag is included, all machines marked inaccessible. If the -fast flag is included, the Cache Manager does not probe any machines, but instead reports the results of the most recent previous probe. To set the interval between probes rather than produce a list of inaccessible machines, use the -interval argument. The non-default setting persists until the machine reboots; to preserve it across reboots, put the appropriate fs checkservers command in the machine's AFS initialization files. CAUTIONS
The command can take quite a while to complete, if a number of machines do not respond to the Cache Manager's probe. The Cache Manager probes machines sequentially and waits a standard timeout period before marking the machine as unresponsive, to allow for slow network communication. To make the command shell prompt return quickly, put the command in the background. It is harmless to interrupt the command by typing Ctrl-C or another interrupt signal. Note that the Cache Manager probes only server machines marked inaccessible in its memory list. A server machine's absence from the output does not necessarily mean that it is functioning, because it possibly is not included in the memory list at all (if, for example, the Cache Manager has not contacted it recently). For the same reason, the output is likely to vary on different client machines. Unlike most fs commands, the fs checkservers command does not refer to the AFSCELL environment variable. OPTIONS
-cell <cell to check> Names each cell in which to probe server machines marked as inaccessible. Provide the fully qualified domain name, or a shortened form that disambiguates it from the other cells listed in the local /etc/openafs/CellServDB file. Combine this argument with the -fast flag if desired, but not with the -all flag. Omit both this argument and the -all flag to probe machines in the local cell only. -all Probes all machines in the Cache Manager's memory list that are marked inaccessible. Combine this argument with the -fast flag if desired, but not with the -cell argument. Omit both this flag and the -cell argument to probe machines in the local cell only. -fast Displays the Cache Manager's current list of machines that are inaccessible, rather than sending new probes. The output can as old as the current setting of the probe interval (by default three minutes, and maximum ten minutes). -interval <seconds between probes> Sets or reports the number of seconds between the Cache Manager's probes to machines in the memory list that are marked inaccessible: o To set the interval, specify a value from the range between 1 and 600 (10 minutes); the default is 180 (three minutes). The issuer must be logged in as the local superuser "root". The altered setting persists until again changed with this command, or until the machine reboots, at which time the setting returns to the default. o Provide a value of 0 (zero) to display the current interval setting. No privilege is required. Do not combine this argument with any other. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
If there are no machines marked as inaccessible, or if all of them now respond to the Cache Manager's probe, the output is: All servers are running. Note that this message does not mean that all server machines in each relevant cell are running. The output indicates the status of only those machines that the Cache Manager probes. If a machine fails to respond to the probe within the timeout period, the output begins with the string These servers unavailable due to network or server problems: and lists the hostname of each machine on its own line. The Cache Manager stores machine records by Internet address, so the format of each hostname (uppercase or lowercase letters, or an Internet address in dotted decimal format) depends on how the local cell's name service translates it at the time the command is issued. If a server machine is multihomed, the output lists only one of its interfaces (usually, the currently most preferred one). If the -interval argument is provided with a value between 1 and 600, there is no output. If the value is 0, the output reports the probe interval as follows: The current down server probe interval is <interval> secs EXAMPLES
The following command displays the Cache Manager's current list of unresponsive machines in the local cell, rather than probing them again. The output indicates that if there were any machines marked inaccessible, they all responded to the previous probe. % fs checkservers -fast All servers are running. The following example probes machines in the Cache Manager's memory list that belong to the "stateu.edu" cell: % fs checkservers -cell stateu.edu All servers are running. The following example probes all server machines in the Cache Manager's memory list. It reports that two machines did not respond to the probe. % fs checkservers -all These servers unavailable due to network or server problems: fs1.abc.com SV3.STATE.EDU. PRIVILEGE REQUIRED
To set the probe interval, the issuer must be logged in as the local superuser "root". Otherwise, no privilege is required. SEE ALSO
CellServDB(5), ThisCell(5), fs_newcell(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FS_CHECKSERVERS(1)
All times are GMT -4. The time now is 11:26 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy