10 More Discussions You Might Find Interesting
1. Solaris
SunOS 5.10 Generic_142900-15 sun4u sparc SUNW,SPARC-Enterprise
How can I tell if "clustering" is being used in my shop?
I have to file systems that are identical. These filesystems are nfs mounted. But how can I tell if they are being kept in sync as a result of clustering or some other... (2 Replies)
Discussion started by: Harleyrci
2 Replies
2. Shell Programming and Scripting
I need a scrip that will show me the filesystems that are greater than 70%...but not sure how to filter using the df -h | grep
Thank you for your help!! (6 Replies)
Discussion started by: eponcedeleonc
6 Replies
3. Shell Programming and Scripting
i need to write a shell script for printing the list of filesystems whose disk utilization is more than 75%...i tried using df -h along with awk but cud'nt make the combination work.....:wall:
when we do df -h then the filesystems which are using more than 75% capacity shud be printed according to... (11 Replies)
Discussion started by: xtatic
11 Replies
4. UNIX for Dummies Questions & Answers
hi guys
suse 10.2
today some guys are adding some luns from a SAN so in order to add them I followed this command
echo 1 > /sys/class/fc_host/host1/issue_lip
echo "- - -" > /sys/class/scsi_host/host<number>/scan
nice now
after that I tried to create a folder in /
but it won't let... (2 Replies)
Discussion started by: karlochacon
2 Replies
5. UNIX for Dummies Questions & Answers
how to check the record of previously mounted remote filesystems after the filesystems are unmounted .operating system is solaris 10 (0 Replies)
Discussion started by: ravijanjanam12
0 Replies
6. AIX
hi is that any command to find out which filesystems occupying more process in cpu utilisation (4 Replies)
Discussion started by: senmak
4 Replies
7. AIX
Hi to all
i want to increase the /usr size.
but, it is mirrored on hdisk0 and hdisk1.
i know that chfs will work, but i am not confident about mirroring.
can anyone tell me the procedure.
thanks (2 Replies)
Discussion started by: honeym210
2 Replies
8. UNIX for Advanced & Expert Users
Dear All
We have HP9000 rp7400 Server running with hp-ux 11i.
Our Disk storage has two volume groups and are allocated as follows:
1. /#vgdisplay -v
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available... (1 Reply)
Discussion started by: mhbd
1 Replies
9. UNIX for Dummies Questions & Answers
If you have multiple hard drives and multiple mounted filesystems, how can you tell which filesystem resides on which disk? (3 Replies)
Discussion started by: jalburger
3 Replies
10. UNIX for Advanced & Expert Users
my partner change the server's ip address and now i can't to mount the oracle's filesystem, what i do? i don't want to reinstall Unix. My unix is SCO UNIX 5.0.5 (9 Replies)
Discussion started by: marun
9 Replies
FSCK(8) BSD System Manager's Manual FSCK(8)
NAME
fsck -- filesystem consistency check and interactive repair
SYNOPSIS
fsck -p [-f]
fsck [-l maxparallel] [-q] [-y] [-n] [-d]
DESCRIPTION
The first form of fsck preens a standard set of filesystems or the specified filesystems. It is normally used in the script /etc/rc during
automatic reboot. Here fsck reads the filesystem descriptor table (using getfsent(3)) to determine which filesystems to check. Only parti-
tions that have ``rw,'' ``rq'' or ``ro'' as options, and that have non-zero pass number are checked. Filesystems with pass number 1 (nor-
mally just the root filesystem) are checked one at a time. When pass 1 completes, all remaining filesystems are checked, running one process
per disk drive. The disk drive containing each filesystem is inferred from the shortest prefix of the device name that ends in one or more
digits; the remaining characters are assumed to be the partition designator. In preening mode, filesystems that are marked clean are
skipped. Filesystems are marked clean when they are unmounted, when they have been mounted read-only, or when fsck runs on them success-
fully.
It should be noted that fsck is now essentially a wrapper that invokes other fsck_XXX utilities as needed. Currently, fsck can invoke
fsck_hfs, fsck_msdos, fsck_exfat, and fsck_udf. If this underlying process that fsck invokes encounters serious inconsistencies or the
filesystem type is not one of the above, it exits with an abnormal return status and an automatic reboot will then fail. For each corrected
inconsistency one or more lines will be printed identifying the filesystem on which the correction will take place, and the nature of the
correction.
If sent a QUIT signal, fsck will finish the filesystem checks, then exit with an abnormal return status that causes an automatic reboot to
fail. This is useful when you want to finish the filesystem checks during an automatic reboot, but do not want the machine to come up multi-
user after the checks complete.
Without the -p option, fsck audits and interactively repairs inconsistent conditions for filesystems. It should be noted that some of the
corrective actions which are not correctable under the -p option will result in some loss of data. The amount and severity of data lost may
be determined from the diagnostic output. If the operator does not have write permission on the filesystem fsck will default to a -n action.
The following flags are interpreted by fsck and passed along to the underlying tool that it spawns.
-f Force fsck to check `clean' filesystems when preening.
-l Limit the number of parallel checks to the number specified in the following argument. By default, the limit is the number of
disks, running one process per disk. If a smaller limit is given, the disks are checked round-robin, one filesystem at a time.
-p "Preen" mode, described above.
-q Do a quick check to determine if the filesystem was unmounted cleanly.
-y Assume a yes response to all questions asked by fsck; this should be used with great caution as this is a free license to con-
tinue after essentially unlimited trouble has been encountered.
-n Assume a no response to all questions asked by fsck except for 'CONTINUE?', which is assumed to be affirmative; do not open the
filesystem for writing.
If no filesystems are given to fsck then a default list of filesystems is read using getfsent(3).
Because of inconsistencies between the block device and the buffer cache, the raw device should always be used.
SEE ALSO
fs(5), fsck_hfs(8), fsck_msdos(8), getfsent(3), reboot(8)
4th Berkeley Distribution May 18, 2010 4th Berkeley Distribution