Df reporting double size of du after fsck & reboot
Solaris 8
running on a Sparcstation 5 (Aurora) with 170MHz processor and 256MB ram
This is AFTER doing fsck and reboot.
820030k vs 385252k
All other files in /usr/asm not in /usr/asm/sys or /usr/asm/data amount to 43k. The /usr/asm/lost+found is 8k. somehow df and other applications flagging for disk full are seeing an extra 400000k, where is this?
this is run as superuser, so all hidden files should be shown right?
I have several questions here, would like to confirm with. First why in Linux everytime let say i boot up around nearly to a month i got a message during the Services Loading such as "FSCK havent run for 29 days performing fsck ".
Is there to disable it? Why beacause i want to run it mannualy,... (2 Replies)
Hi all,
Thanks to Merlin & Djtrippin for comments in another thread.
Does anyone know of any issues with harddrive size and Mandrake 9.0? I have installed Mandrake (like a dream) on a 10gb drive but it refuses to go beyond the partition check on my 80gb unit. The 80 is new and I have... (5 Replies)
I have a system that upon boot, will declare a bad trap and reboot, whereupon it encounters the same bad trap and reboots in an endless cycle until I stop it. I can get to the ok prompt. An attempt to boot in single user mode left the box completely hung and required a power cycle to re-establish... (3 Replies)
I need to find to find duplicate lines in a document and then print the line numbers of the duplicates
The files contain multiple lines with about 100 numbers on each line I need something that will output the line numbers where duplicates were found ie 1=5=7, 2=34=76
Any suggestions would be... (5 Replies)
Dear Gurus,
I would like to know if fsck is executed automatically during reboot for AIX?
Is there any logs which I can refer to? or any documentation reference for this?
Thank You. (2 Replies)
Could you please help with problem with megaraid controller and Dell PowerEdge 2850, all that I can see on thi screenshot:
All drives successfuly passed verifing from LSI controllers (Ctrl+A at startup), also I tried to boot from rescue llive cd and mount all the morrored drives and check... (22 Replies)
So I was patching a Solaris 10 U08 X86 X2200 box in preparation for an Oracle upgrade. Rebooted the box because the patches failed and the box will not boot successfully. I need to back up the zones on the 2 drives before going further. I pulled the drives and attempted to mount them on my Ubuntu... (0 Replies)
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
I have been searching both on Unix.com and Google and have not been able to find the answer to my question. I think it is partly because I can't come up with the right search terms.
Recently, my virtual server switched storage devices and I think the problem may be related to that change.... (2 Replies)
Discussion started by: jmgibby
2 Replies
LEARN ABOUT MOJAVE
fsck
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_apfs, 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.
-R Specify a particular passno number for which fsck is to check. You may only specify 1 or 2. Only those filesystems matching
that particular passno entry (if using fstab) will be checked. For more information on the passno field, see fstab(5).
-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_apfs(8), fsck_msdos(8), getfsent(3), fstab(5,) reboot(8)4th Berkeley Distribution May 18, 2010 4th Berkeley Distribution