03-04-2017
Fsck was designed to check the file system integrity and to repair it when possible. There is no way with fsck to repair the files themselves. Even if all of their blocks are readable, that doesn't mean they are not (silently) corrupted.
That's one of the reasons why UFS is essentially obsolete and replaced by ZFS under Solaris.
With ZFS, you can use "scrub" to check and repair everything, including file contents when there is redundancy (ditto blocks, raidz or mirror).
These 3 Users Gave Thanks to jlliagre For This Post:
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello !
Does anyone knows which de limit of files in the ufs filesystem in the Solaris 2.6 ??
Danke,
Witt (2 Replies)
Discussion started by: witt
2 Replies
2. Solaris
Hi,
I have a 2,1 TB RAID0 Array (3- 750GB discs).
I have Solaris 10 x86 installed.
When I try to create a volume on this drive I receive the following error:
"
WARNING: /pci@0/pci8086/..../sd@6,0 (sd7) disk capacity is too large for current cbd length
"
I assume I can not format... (5 Replies)
Discussion started by: narrok
5 Replies
3. Solaris
Hi there,
I am trying to mount a SAN volume (which is mapped to solaris sparc) partitioned with ufs filesystem onto a linux (intel processor 64bit) server.
*I have re-compiled the linux kernel t support ufs fstype with ro mount support.
filesystem on solaris:... (3 Replies)
Discussion started by: ilan
3 Replies
4. Solaris
I have two Unix (Solaris) hosts that are both attached to our SAN. They are both presented with the same luns.
What I want to do is have the same UFS filesystem mounted on both hosts at the same time. What I am trying to accomplish is creating a zone that will reside on both hosts but only... (2 Replies)
Discussion started by: beaker457
2 Replies
5. BSD
Hi, I'm new to BSD and would like to create a dual-boot between Solaris Express Community Edition and FreeBSD.
I would just like to know if the Solaris UFS file system can be written to by BSD?
I know that BSD uses UFS2, but I'm hoping that it is backwards compatible with UFS1 provided that... (0 Replies)
Discussion started by: Johnny SSH
0 Replies
6. Solaris
Hi Gurus
I want to know the command & tips regarding, how to increase or decrease inode number of the particular ufs filesystem. Is it possible to do it in a live/production environment.
Regards (3 Replies)
Discussion started by: girish.batra
3 Replies
7. Solaris
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)
Discussion started by: getrue
4 Replies
8. Solaris
I need to increase the /var (UFS) filesystem and root disk under veritas control or root disk is encapsulated
# df -k /var
Filesystem kbytes used avail capacity Mounted on
/dev/vx/dsk/var 13241195 12475897 674524 96% /var
# fstyp /dev/vx/dsk/var
ufs
# pkginfo... (1 Reply)
Discussion started by: amity
1 Replies
FSCK(1) General Commands Manual FSCK(1)
NAME
fsck, fsck1 - perform file system consistency check
SYNOPSIS
fsck [-aclmrs] [device] ...
OPTIONS
-a Automatically repair inconsistencies
-c Check and list only the specified i-nodes
-l List the files and directories in the filesytem
-r Prompt user for repairs if inconsistencies are found
-s List the superblock of the file system
EXAMPLES
fsck /dev/hd4 # Check file system on /dev/hd4
fsck -a /dev/at0 # Automatically fix errors on /dev/at0
fsck -l /dev/fd0 # List the contents of /dev/fd0
fsck -c 2 3 /dev/hd3
# Check and list /dev/hd3 i-nodes 2 & 3
DESCRIPTION
Fsck performs consistency checks on the file systems which reside on the specified devices. Fsck1 is an alternate version for use on obso-
lete V1 file systems. When either the -a or -r flags are given, the file system will be repaired if errors are found. Before running fsck
on a mounted file system, it must first be unmounted. Trying to repair a mounted file system is dangerous and should not be attempted.
To repair the root file system (which cannot be unmounted), first type CTRL-F9 at the console to kill any and all processes. Log back in
as root, type sync to force any buffered changes to disk, run fsck on the root file system and immediately reboot the computer by typing
reboot.
It is necessary to kill all processes before repairing the root file system to prevent them from modifying any disk blocks while fsck is
running. This is only necessary for the root file system, any other file system can simply be unmounted before it is checked.
SEE ALSO
mkfs(1), mount(1).
FSCK(1)