05-15-2008
Unfortunately it's not really scriptable as the inode entries are lost. Your only option is to discern from the content what the file is and where it should be linked into the FS tree.
If you know where a bunch should go and need a way to automate this process (ie you can describe exactly what the process should be) then we can script _that_, otherwise it's going to be a long, slow, process sorry
I take it restoring from backup isn't an option?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
after a crash of our SUN Server 220R on file system was corrupt
and I had run fsck getting a lost of files/dir's in the lost+found
of the file system loking like
drwxrwxr-x 2 lmxadmin DOS---- 512 Oct 31 21:04 #0007680
drwxrwxr-x 2 lammer DOS---- 512 Jan 29 09:29... (6 Replies)
Discussion started by: DPAI
6 Replies
2. UNIX for Advanced & Expert Users
Hi all
I am using SOLARIS 8 on Sun enterpris3000 server. Last night i got a file system corrupted adn some inconsistancy in the file system were shown when i run fsck -o p option.
Then i tried to fix it with fsck -F ufs -y /dev/md/rdsk/d1 option as i have given all yes response i cd not able to... (4 Replies)
Discussion started by: Prafulla
4 Replies
3. UNIX for Dummies Questions & Answers
what is the directory "lost+found" and how is it used? (2 Replies)
Discussion started by: Ben070371
2 Replies
4. UNIX for Advanced & Expert Users
hi all,
just wanted to know what is lost+found dir for?
tnx (1 Reply)
Discussion started by: bok
1 Replies
5. AIX
Hi,
I have a AIX 4.3.3 running on IBM pseries server.
I have some jfs filesystems running on it.
I dont see Lost+Found directory in them.
Can anybody guide me why it is not available.
Cheers,
Vinod.. (4 Replies)
Discussion started by: vinod2all
4 Replies
6. Solaris
If you delete your lost & found directory, how do you get it back, just do a mkdir? (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies
7. UNIX for Dummies Questions & Answers
Hi, upon reboot of our test solaris 9 box, I was prompted to run fsck on one of the filesystems (/var). This resulted in placing all the files in the lost+found directory. I have no backup. What are my options to place the files back to /var (from lost+found, is it possible?).
Appreciate any... (1 Reply)
Discussion started by: spricks
1 Replies
8. UNIX for Advanced & Expert Users
Does anyone have or know of a script to help sort and display a large lost+found directory? i've googled this but not much help
solaris 9
thanks (3 Replies)
Discussion started by: morrish
3 Replies
9. Red Hat
Hi All,
I am facing a problem of filesystem corruption,where i am trying to recover data with fsck -f <device name> ,now it restore the corrupted data in lost+found directory.Please let me know how to recover the data from lost+found directory.
Thanks,
Shailesh (1 Reply)
Discussion started by: sbapotikar
1 Replies
10. Red Hat
Hi,
What is lost+found in linux ?
Cheers,
snj (2 Replies)
Discussion started by: snjksh
2 Replies
gcore(1) User Commands gcore(1)
NAME
gcore - get core images of running processes
SYNOPSIS
gcore [-pgF] [-o filename] [-c content] process-id...
DESCRIPTION
The gcore utility creates a core image of each specified process. By default, the name of the core image file for the process whose process
ID is process-id will be core.process-id.
OPTIONS
The following options are supported:
-c content Produces core image files with the specified content. The content description uses the same tokens as in coreadm(1M). The
-c option does not apply to cores produced due to the -p or -g flags.
-F Force. Grabs the target process even if another process has control.
-g Produces core image files in the global core file repository with the global content as configured by coreadm(1M). The com-
mand will fail if the user does not have permissions to the global core file repository.
-o filename Substitutes filename in place of core as the first part of the name of the core image files. filename can contain the same
tokens to be expanded as the paths in coreadm(1M).
-p Produces a core image file in the process-specific location with the process-specific content for each process as config-
ured by coreadm(1M). The command will fail if the user does not have permissions to the per-process core file repository.
OPERANDS
The following operand is supported:
process-id process ID
EXIT STATUS
The following exit values are returned:
0 On success.
non-zero On failure, such as non-existent process ID.
FILES
core.process-id core images
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWtoo |
+-----------------------------+-----------------------------+
|Interface Stability |See below. |
+-----------------------------+-----------------------------+
Command Syntax is Evolving. Output Format(s) are Unstable.
SEE ALSO
kill(1), coreadm(1M), setrlimit(2), core(4), proc(4), attributes(5)
NOTES
gcore is unaffected by the setrlimit(2) system call using the RLIMIT_CORE value.
SunOS 5.10 11 Feb 2004 gcore(1)