Any idea how? I have read every guide I can find on the internet with no luck.
Well, how did you encrypt it in the first place? How does it usually get mounted?
Quote:
What does Magic Rescue do that photorec can't do?
Magic Rescue works much the same way as Photorec -- scan every block to see if it's the start of a file -- but it's lot more sophisticated, using script-like plugins to recognize many types of files instead of recognizing a simple few hardcoded ones.
This is also what makes it slower, since it does a lot more work on each block it reads, checking them all to see what they are.
You seem to be having lots and lots of data loss problems lately. A good backup might be an idea.
I noticed this in a search for more security tools...
It IS possible to "undelete" a file; I suppose recover would be a better term for it. I suppose we've all made the boo-boo (that we all hopefully learned from) of deleting a file, and finding that you do not have a backup. I wouldn't... (1 Reply)
I am helping a company recover a system that is SCO OS 5.0.5 - they have their backup media, cd copies of SCO, but they do not have their license keys to install and SCO is being difficult in validating their license.
Does anyone have an install license key for 5.0.5 that they would be willing... (1 Reply)
Hiiii,
I have written a script which takes backup of some log files.
let say the backuplocation is ---
/abc/backuplocation
-rw-r--r-- 1 webmut2 spgroup 0 Jan 27 02:41 ansrpt23994.log
-rw-r--r-- 1 webmut2 spgroup 0 Jan 27 02:41 ansrpt3601.log
-rw-r--r-- 1... (2 Replies)
Hi Guys,
I have an user's home directory set to /home/A
And A contains the following directories B & C
Is there some way in solaris by which i can prevent the directories B and C from getting deleted by the user but the contents of the directories B & C can be deleted ?
Also i have... (2 Replies)
I've been working with SCO Unix for several years now but have never had to restore a system from a bare drive.
I have a bootable CD that contains what appears to be the correct files necessary to recover the boot and root filesystems.
I've got the BIOS setup such that the CD is the first... (12 Replies)
Hi,My system is not booting and at the startup it is getting struck.In HMC error code is coming as 0000, I know the reason of failing.I have few queries on recovery, please answer:1. I have mksysb of the system from which I can restore the system but problem is my few application mount point was a... (5 Replies)
One of my directory code where i have stored all my scripts have disappeared . I have no idea on how it got deleted.Could someone pls help me to track-back on what would have happened? I left the office yesterday and today when i just logged in to work with the scripts I could not find the... (13 Replies)
Friends,
I have accidently, as root, created a directory gabsf under /home. Now I cannot delete this thing, I have tried rm and rmdir, as well as explicit path name, but it is really undeleteable. Here is what ls -l says.
# ls -l /home
total 6
drwxr-xr-x 2 dawood dawood 2 Sep 5... (3 Replies)
Discussion started by: gabam
3 Replies
LEARN ABOUT MOJAVE
undelete
UNDELETE(2) BSD System Calls Manual UNDELETE(2)NAME
undelete -- attempt to recover a deleted file
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <unistd.h>
int
undelete(const char *path);
DESCRIPTION
The undelete() system call attempts to recover the deleted file named by path. Currently, this works only when the named object is a white-
out in a union file system. The system call removes the whiteout causing any objects in a lower layer of the union stack to become visible
once more.
Eventually, the undelete() functionality may be expanded to other file systems able to recover deleted files such as the log-structured file
system.
RETURN VALUES
The undelete() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indi-
cate the error.
ERRORS
The undelete() succeeds unless:
[ENOTDIR] A component of the path prefix is not a directory.
[ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters.
[EEXIST] The path does not reference a whiteout.
[ENOENT] The named whiteout does not exist.
[EACCES] Search permission is denied for a component of the path prefix.
[EACCES] Write permission is denied on the directory containing the name to be undeleted.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[EPERM] The directory containing the name is marked sticky, and the containing directory is not owned by the effective user ID.
[EINVAL] The last component of the path is '..'.
[EIO] An I/O error occurred while updating the directory entry.
[EROFS] The name resides on a read-only file system.
[EFAULT] The path argument points outside the process's allocated address space.
SEE ALSO unlink(2)HISTORY
The undelete() system call first appeared in 4.4BSD-Lite.
BSD January 22, 2006 BSD