Sponsored Content
Full Discussion: Undelete, backup inodes
Operating Systems Solaris Undelete, backup inodes Post 302894554 by hicksd8 on Wednesday 26th of March 2014 06:32:18 AM
Old 03-26-2014
I'm not sure that I understand your question because, looking at your profile on this forum, you are a significant contributor. Therefore, I apologise in advance if I have completely missed the point.

There's no easy way AFAIK to 'backup' (and therefore restore) inodes. However, if it's idiots deleting files that you're concerned about, then sysadmins can manage that by creating a second 'link' to a file, in for example, another directory. If a user accidently/deliberately deletes a file then they only delete that link and the actual data isn't lost until all links are removed. Therefore, putting the link back where is should be will instantly 'restore' the file.

Does that help? Or, as I say, have I misunderstood the question?

Last edited by hicksd8; 03-26-2014 at 07:38 AM..
This User Gave Thanks to hicksd8 For This Post:
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

undelete

Hi All, I just given $rm abc.pc, I don't have backup also. is there any way to recover? thanks in advance krishna (3 Replies)
Discussion started by: krishna
3 Replies

2. Solaris

inodes

hi i need to find all the files that r linked to the current file as i need to delete the file as well as few of its links :confused: thnx in advance (1 Reply)
Discussion started by: livemyway
1 Replies

3. Filesystems, Disks and Memory

Undelete files

Right, a mate of mine screwed up today and deleted the entire contents of a directory and he really needs to get the files back. He's using Red Hat Enterprise Edition 4. The files were deleted using rm *. He can't remember if the hard drive was formatted using ext2 or ext3. Anybody have any idea... (0 Replies)
Discussion started by: Bacchus
0 Replies

4. UNIX for Dummies Questions & Answers

inodes

how is the location of inodes in the physical disk. are they sequential like: bootblock|superblock|inode1|inode2| ....| datablock1|datablock2|datablock3 or are they distributed among data blocks like: bootblock|superblock|inode1|datablock1|inode2|datablock2|datablock3|inode3 |datablock4 (3 Replies)
Discussion started by: gfhgfnhhn
3 Replies

5. UNIX for Dummies Questions & Answers

Undelete files in Unix

Hi Is there any way to restore files accidentally deleted in Unix (other than rm -i) (10 Replies)
Discussion started by: misenkiser
10 Replies

6. UNIX for Advanced & Expert Users

How to undelete

Hi Is there a way by which I can recover the last deleted file file from a folder. OR I had a file in a path .(i didnt notice the size at that time ) I tried ftp that file to my windows but got file of zero size. I want to check whether the file was already empty when I tried ftping it... (1 Reply)
Discussion started by: pratim09
1 Replies

7. UNIX for Advanced & Expert Users

UNDELETE a file

Hi, In tcsh, I mistakenly deleted some files under a dir with rm * Is there any way by which I can recover those files (without restoring to an earlier backup point) ? I mean any command like undelete or anything similar (10 Replies)
Discussion started by: snowline84
10 Replies

8. UNIX for Advanced & Expert Users

Help with Inodes please

How can i trace Inode structure and modify it in UNIX kernel? We want to change the inode structure in the sense that we want to add a new field to the inode data structure. So we want to know how and where to trace inode (7 Replies)
Discussion started by: Group_Inode
7 Replies

9. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

Hi Everyone, we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment? Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies

10. SCO

Versioning through undelete

Hi , I am using SCO openserver realease 3.2 and tried to test versioning on a directory with undelete -s . The command executes well but it is not creating any versions of the files in it. I have also setted versioning options via filesystem and then remounted it but of ... (0 Replies)
Discussion started by: dextergenious
0 Replies
SYMLINK(2)							System Calls Manual							SYMLINK(2)

NAME
symlink - make symbolic link to a file SYNOPSIS
symlink(name1, name2) char *name1, *name2; DESCRIPTION
A symbolic link name2 is created to name1 (name2 is the name of the file created, name1 is the string used in creating the symbolic link). Either name may be an arbitrary path name; the files need not be on the same file system. RETURN VALUE
Upon successful completion, a zero value is returned. If an error occurs, the error code is stored in errno and a -1 value is returned. ERRORS
The symbolic link is made unless on or more of the following are true: [ENOTDIR] A component of the name2 prefix is not a directory. [EINVAL] Either name1 or name2 contains a character with the high-order bit set. [ENAMETOOLONG] A component of either pathname exceeded 255 characters, or the entire length of either path name exceeded 1023 characters. [ENOENT] The named file does not exist. [EACCES] A component of the name2 path prefix denies search permission. [ELOOP] Too many symbolic links were encountered in translating the pathname. [EEXIST] Name2 already exists. [EIO] An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the link contents of name2. [EROFS] The file name2 would reside on a read-only file system. [ENOSPC] The directory in which the entry for the new symbolic link is being placed cannot be extended because there is no space left on the file system containing the directory. [ENOSPC] The new symbolic link cannot be created because there there is no space left on the file system that will contain the sym- bolic link. [ENOSPC] There are no free inodes on the file system on which the symbolic link is being created. [EDQUOT] The directory in which the entry for the new symbolic link is being placed cannot be extended because the user's quota of disk blocks on the file system containing the directory has been exhausted. [EDQUOT] The new symbolic link cannot be created because the user's quota of disk blocks on the file system that will contain the symbolic link has been exhausted. [EDQUOT] The user's quota of inodes on the file system on which the symbolic link is being created has been exhausted. [EIO] An I/O error occurred while making the directory entry or allocating the inode. [EFAULT] Name1 or name2 points outside the process's allocated address space. SEE ALSO
link(2), ln(1), unlink(2) 4.2 Berkeley Distribution August 26, 1985 SYMLINK(2)
All times are GMT -4. The time now is 08:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy