Sponsored Content
Top Forums UNIX for Advanced & Expert Users Recover Deleted Folder using rm command Post 302693321 by vbe on Wednesday 29th of August 2012 04:29:50 AM
Old 08-29-2012
Unfortunately UNIX is not MS...
If its deadly important your only hope is that if you did no transactions since, to crash your system ( yes cut the power...) hoping the system did not already sync... and best deal after is to take the disk to a specialist for recovery but even that we cant be sure it works since you did not mention what OS and more important what type of file system you are using... (Above worked on HFS and if you knew well your system you could have tried an attempt yourself using fsck... but its very very tricky...)
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Recover deleted files

Is there a Unix tool, like in Novell, to recover accidentally deleted files? (2 Replies)
Discussion started by: kuultak
2 Replies

2. AIX

recover deleted files

How to recover deleted files in AIX ? (1 Reply)
Discussion started by: vjm
1 Replies

3. Shell Programming and Scripting

Is there a way to recover files deleted using rm command???

Hi All, I just mistakingly deleted some files using rm command.Is there a way to get it back?i work on Solaris 10 Thanks, Kumar (1 Reply)
Discussion started by: kumarsaravana_s
1 Replies

4. Solaris

How to recover deleted logical volume.

My Solaris system administrator has doing troubleshooting to my server. He has accidental remove the hardware raid. Is it possible to recover it back? (4 Replies)
Discussion started by: webster5u
4 Replies

5. Shell Programming and Scripting

Need to Recover Deleted Files

Hi, By mistake, executed the following command : rm -rf * and ALL files got deleted. But I need to get back these files as they are very very important. Please help me how to recover this file. Its Urgent for me please. Thanks in advance. (6 Replies)
Discussion started by: unx100
6 Replies

6. Solaris

how to recover from deleted etc in solaris 9

Recently our Server Room got burnt and we lost everything including a sunfire V880 server. I had a backup and restored it on our 2nd server. I mistakenly restored the etc folder from the burnt server too. After rebooting the 2nd server I can't get the root directory and other volumes mounting. I... (11 Replies)
Discussion started by: rahmantanko
11 Replies

7. Emergency UNIX and Linux Support

Recover deleted partition

Hi, I have got 2 hdds (2x Seagate 7200.12, 500GB). I had two RAID volumes on them: 1: 100GB RAID0 (strip) 2: ~415GB RAID1 (mirror) due to problems with matrix I removed RAID0 and RAID1 - i thougth that all data from RAID1 would be available. Unfortunately it is not. On 1 disk I set... (7 Replies)
Discussion started by: Chrisdot
7 Replies

8. Solaris

How to recover deleted file in Solaris?

dear all please tell me how can i recover deleted file in solaris. i am removing file with rm command. thanks in advance. (3 Replies)
Discussion started by: nikhil kasar
3 Replies

9. UNIX for Dummies Questions & Answers

How to recover deleted file?

Hi All By mistake i have deleted some file in a directory, is there any way to get it back in Unix( i am using sh ) (2 Replies)
Discussion started by: parthmittal2007
2 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 08:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy