09-19-2012
I'm not familiar enough with SCO but I guess it support more than one file system type so are you using the same one, and which one is it ?
@dextergenious: you are right with the -v option. As it is not POSIX, it has been dropped in other Unix implementations.
You states "space used by filesystem entities = 26.1 gb". Did you reboot and you perform a fsck to rule out deleted still open files and file system corruption ?
Last edited by jlliagre; 09-19-2012 at 01:06 PM..
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have to do a lot of reporting for the company that I work for and was wondering if anyone had suggestions for a way to create professional looking reports. I currently use Filepro so much that I rarely see the shell. Any help is appreciated. (3 Replies)
Discussion started by: Mike11
3 Replies
2. UNIX for Dummies Questions & Answers
Hi everyone, I'm completely new to the board and to UNIX and I have the following question regarding a script I am building.
I am trying to copy an entire directory into a new directory and I was wondering if there is any way of printing on screen a progress report, for example a percentage. It... (9 Replies)
Discussion started by: Ypnos
9 Replies
3. SCO
hi,
i m having a sco unix system...i want to store the output of dfspace command ie %free space of each partition to different variable so that i can use it for further processing.......can anybody pls help me out
thx
girish (1 Reply)
Discussion started by: girish_shukla
1 Replies
4. Shell Programming and Scripting
Hi:-
I am working on an audit report that produces a monthly summary of account activity on a particular AIX host. I am struggling with su activity and failed logins as these tend to come back with more then a month's data.
Is there a easy way that these files can be rotated/cleaned out on a... (1 Reply)
Discussion started by: janet
1 Replies
5. UNIX for Dummies Questions & Answers
I am very new to unix/linux and am unsure how to do the following tasks within my script
1) append a log file and add a timestamped echo "Error occured" to it, if posibble to print it to file and on screen at the same time would be even better.
2) As my main script will be calling on a couple... (1 Reply)
Discussion started by: shamwick
1 Replies
6. Filesystems, Disks and Memory
Hi.
How do you guys, monitor/report your Storage environment? I have people (don't we all? ) that like to have monthly reports on space (raw/assigned/available), ports available/used, switches and the such.
Do you use anything special? Or are you like me, a nice big Excel spreadsheet? How... (1 Reply)
Discussion started by: Stephan
1 Replies
7. Shell Programming and Scripting
I need to accomplish the following task -
I have a number of accounts for a number of applications that i deploy on a unix server. There are a number of directories for each account in /prod/apps directory. eg. For an account Application1 I have /prod/apps/Application1_1 /prod/apps/Application1_2... (4 Replies)
Discussion started by: niranjandighe
4 Replies
8. Solaris
Hi,
I am hunting for a low cost Monitoring & Reporting Tool for the SUN Environment.
I have all and all SUN Environment with LDOMs, Zones.
The monitoring Tool
1. Hardware failure.
2. Disk space and failure.
3. LDOMS,Zones.
4. CPU,Memory Utilization.
5. ping,URL Monitors
6. Send... (4 Replies)
Discussion started by: menonk
4 Replies
9. Shell Programming and Scripting
Below is a typical report
each of the lines represent the fields in the report
component1
component2
<pattern>
..
..
n lines ...
..
VIOL = 2
the command should display
component1
component2
VIOL = 2
only if pattern field of the report is "good"
component1 and... (8 Replies)
Discussion started by: dll_fpga
8 Replies
LEARN ABOUT OPENSOLARIS
fsck.minix
FSCK.MINIX(8) System Administration FSCK.MINIX(8)
NAME
fsck.minix - check consistency of Minix filesystem
SYNOPSIS
fsck.minix [options] device
DESCRIPTION
fsck.minix performs a consistency check for the Linux MINIX filesystem.
The program assumes the filesystem is quiescent. fsck.minix should not be used on a mounted device unless you can be sure nobody is writ-
ing to it. Remember that the kernel can write to device when it searches for files.
The device name will usually have the following form:
/dev/hda[1-63] IDE disk 1
/dev/hdb[1-63] IDE disk 2
/dev/sda[1-15] SCSI disk 1
/dev/sdb[1-15] SCSI disk 2
If the filesystem was changed, i.e., repaired, then fsck.minix will print "FILE SYSTEM HAS CHANGED" and will sync(2) three times before
exiting. There is no need to reboot after check.
WARNING
fsck.minix should not be used on a mounted filesystem. Using fsck.minix on a mounted filesystem is very dangerous, due to the possibility
that deleted files are still in use, and can seriously damage a perfectly good filesystem! If you absolutely have to run fsck.minix on a
mounted filesystem, such as the root filesystem, make sure nothing is writing to the disk, and that no files are "zombies" waiting for
deletion.
OPTIONS
-l, --list
List all filenames.
-r, --repair
Perform interactive repairs.
-a, --auto
Perform automatic repairs. This option implies --repair and serves to answer all of the questions asked with the default. Note
that this can be extremely dangerous in the case of extensive filesystem damage.
-v, --verbose
Be verbose.
-s, --super
Output super-block information.
-m, --uncleared
Activate MINIX-like "mode not cleared" warnings.
-f, --force
Force a filesystem check even if the filesystem was marked as valid. Marking is done by the kernel when the filesystem is
unmounted.
-V, --version
Display version information and exit.
-h, --help
Display help text and exit.
DIAGNOSTICS
There are numerous diagnostic messages. The ones mentioned here are the most commonly seen in normal usage.
If the device does not exist, fsck.minix will print "unable to read super block". If the device exists, but is not a MINIX filesystem,
fsck.minix will print "bad magic number in super-block".
EXIT CODES
The exit code returned by fsck.minix is the sum of the following:
0 No errors
3 Filesystem errors corrected, system should be rebooted if filesystem was mounted
4 Filesystem errors left uncorrected
7 Combination of exit codes 3 and 4
8 Operational error
16 Usage or syntax error
AUTHORS
Linus Torvalds <torvalds@cs.helsinki.fi>
Error code values by Rik Faith <faith@cs.unc.edu>
Added support for filesystem valid flag: Dr. Wettstein <greg%wind.uucp@plains.nodak.edu>.
Check to prevent fsck of mounted filesystem added by Daniel Quinlan <quinlan@yggdrasil.com>.
Minix v2 fs support by Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>, updated by Nicolai Langfeldt <janl@math.uio.no>.
Portability patch by Russell King <rmk@ecs.soton.ac.uk>.
SEE ALSO
fsck(8), fsck.ext2(8), mkfs(8), mkfs.ext2(8), mkfs.minix(8), reboot(8)
AVAILABILITY
The fsck.minix command is part of the util-linux package and is available from Linux Kernel Archive <https://www.kernel.org/pub/linux/utils
/util-linux/>.
util-linux June 2015 FSCK.MINIX(8)