Sponsored Content
Operating Systems Solaris Deep checking Solaris ufs filesystem Post 302992986 by jlliagre on Saturday 4th of March 2017 11:15:43 AM
Old 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

limit of files in the ufs filesystem

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

How to create a 2 TB UFS filesystem?

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

How can I mount a ufs filesystem on a solaris 10 sparc onto a Linux server

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

UFS filesystem mounted on 2 hosts question

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

FreeBSD compatibility with Solaris UFS filesystem?

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

How to increase or decrease inode number of the particular UFS filesystem

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

unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)

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

How to increase the /var (UFS) filesystem and root disk under veritas control?

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_HFS(8)						    BSD System Manager's Manual 					       FSCK_HFS(8)

NAME
fsck.hfs -- HFS file system consistency check SYNOPSIS
fsck.hfs -q [-df] special ... fsck.hfs -p [-df] special ... fsck.hfs [-n | -y | -r] [-dfgl] [-m mode] [-c size] special ... DESCRIPTION
The fsck.hfs utility verifies and repairs standard HFS and HFS+ file systems. The first form of fsck.hfs quickly checks the specified file systems to determine whether they were cleanly unmounted. The second form of fsck.hfs preens the specified file systems. It is normally started by fsck(8) during systen boot, when a HFS file system is detected. When preening file systems, fsck.hfs will fix common inconsistencies for file systems that were not unmounted cleanly. If more serious problems are found, fsck.hfs does not try to fix them, indicates that it was not successful, and exits. The third form of fsck.hfs checks the specified file systems and tries to repair all detected inconsistencies. If no options are specified fsck.hfs will always check and attempt to fix the specified file systems. The options are as follows: -c size Specify the size of the cache used by fsck.hfs internally. Bigger size can result in better performance but can result in deadlock when used with -l option. Size can be specified as a decimal, octal, or hexadecimal number. If the number ends with a ``k'', ``m'', or ``g'', the number is multiplied by 1024 (1K), 1048576 (1M), or 1073741824 (1G), respectively. -d Display debugging information. This option may provide useful information when fsck.hfs cannot repair a damaged file system. -f When used with the -p option, force fsck.hfs to check `clean' file systems, otherwise it means force fsck.hfs to check and repair journaled HFS+ file systems. -g Causes fsck.hfs to generate its output strings in GUI format. This option is used when another application with a graphical user interface (like Mac OS X Disk Utility) is invoking the fsck.hfs tool. -l Lock down the file system and perform a test-only check. This makes it possible to check a file system that is currently mounted, although no repairs can be made. -m mode Mode is an octal number that will be used to set the permissions for the lost+found directory when it is created. The lost+found directory is only created when a volume is repaired and orphaned files or directories are detected. fsck.hfs places orphaned files and directories into the lost+found directory (located at the root of the volume). The default mode is 01777. -p Preen the specified file systems. -q Causes fsck.hfs to quickly check whether the volume was unmounted cleanly. If the volume was unmounted cleanly, then the exit status is 0. If the volume was not unmounted cleanly, then the exit status will be non-zero. In either case, a message is printed to standard output describing whether the volume was clean or dirty. -y Always attempt to repair any damage that is found. -n Never attempt to repair any damage that is found. -r Rebuild the catalog file on the specified file system. This option currently will only work if there is enough contiguous space on the specified file system for a new catalog file and if there is no damage to the leaf nodes in the existing catalog file. SEE ALSO
fsck(8) BUGS
fsck.hfs is not able to fix some inconsistencies that it detects. HISTORY
The fsck.hfs command appeared in Mac OS X Server 1.0 . Mac OS X November 21, 2002 Mac OS X
All times are GMT -4. The time now is 04:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy