Sponsored Content
Full Discussion: restore kernel file
Operating Systems Solaris restore kernel file Post 302433822 by jlliagre on Wednesday 30th of June 2010 03:43:45 PM
Old 06-30-2010
Are you trying to fix a system that has lost a kernel related file or just investigating how to fix it should it happen ?
Please clarify.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

How do I restore the etc/shadow file

removed this from a friends solaris box via telnet. root can not login at this point is there anyway to fix this via telnet. I have one session open that is not root (2 Replies)
Discussion started by: Youngadmin
2 Replies

2. Solaris

tar - restore a file

We use tar for backing up a server. I need to restore just one file from this backup. Anyone know the syntax? (2 Replies)
Discussion started by: frustrated1
2 Replies

3. Linux

how can i restore a deleted file

I am a relatively new linux user.would like to know how to undo a deleted file (2 Replies)
Discussion started by: wojtyla
2 Replies

4. AIX

4.3.3 restore from file

I had a hard drive fail and am trying to restore a system backup from a file I created about two years ago. At the time I did not have a tape device to use nor a writeable CD drive so I just backed up the machine to a NFS drive. When I created the backup, I used it to set up another machine with... (8 Replies)
Discussion started by: SeanU
8 Replies

5. UNIX for Dummies Questions & Answers

How to restore splitted DD file

I backup a file to tape by using "dd", since the size is too large it took two tape for the backup, the question is how to restore the said file? The "dd" doesn't ask me insert next tape while restoration. (3 Replies)
Discussion started by: coolmans
3 Replies

6. AIX

mksysb restore - Wrong OS level for restore

Hi all, I am still working on my mksysb restore. My latest issue is during an alt_disk_install from tape I got the following error after all the data had been restored. 0505-143 alt_disk_install: Unable to match mksysb level 5.2.0 with any available boot images. Please correct this... (0 Replies)
Discussion started by: pobman
0 Replies

7. Solaris

Which file is read by kernel to set its default system kernel parameters values?

Hi gurus Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value Is it /dev/kmem file or something... (1 Reply)
Discussion started by: girish.batra
1 Replies

8. Ubuntu

How can I restore a file?

Hello! I deleted the disk of my camera by rm, and I need to restore these files. I cannot do it by unrm because that utility is meant for use in ext/ufs filesystem, and that disk is msdosfs. Someone help me! Thanks for any answer! (4 Replies)
Discussion started by: mghis
4 Replies

9. Shell Programming and Scripting

restore deleted file

I accidently deleted the files from linux machine. How to restore back the files. (1 Reply)
Discussion started by: sandy1028
1 Replies

10. UNIX for Dummies Questions & Answers

restore cpio file

Hi, under unix aix , i had to put a catostrophic patch from an editor ... i had first made a cpio backup connected root cd /application find . –print | cpio –ocvBm > /sauvegarde/sauvegarde.cpio Does someone know the command to restore my cpio backup ? thanks in advandce to everyone ... (7 Replies)
Discussion started by: bzh35
7 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 05:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy