02-07-2007
Unreadable Unix File
Hi Everyone,
I have a question for you all. I am working at a company and we are trying to recover .dat files which were created on an older linux box and we have a folder of .dat files that are unreadable. When you try to open them in a text editor you get jibberish all shapes and sizes and when you try to open the files in a file viewer it shows them as a hexadecimal/binary file. These .dat files ultimately have or should have readable data in them stating what we need. If anyone has some solutions or would like to know further details I really would appreciate it. I also checked the permissions on the files and the user it belongs to on the unix box and we were unable to open them on the unix box or on the windows box.
Thanks
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Guys,
I have one query. Say I have one script named test.sh.
My Question: There is any method by which I can make this script (test.sh)
non-human readable( like Encrypt) format as well as it should be executable also(mean to say it (test.sh) should not change its behaviour).
Thanks... (3 Replies)
Discussion started by: SanjayLinux
3 Replies
2. UNIX for Dummies Questions & Answers
I am trying to parse emails sent from a blackberry. I am using fetchmail to download email through IMAP from my exchange server and then forward to local Linux mail. (This part works fine.)
When viewing and saving messages sent as plain text from Outlook, everything works fine. However, when... (1 Reply)
Discussion started by: Squeakygoose
1 Replies
3. Red Hat
hi all,
i executed this command "pstree" on redhat ent 4 and i got this below with unreadable chars:
init─┬─acpid
â”─amqzxma0─┬─amqrrmfa
│ â”─amqzdmaa
│ â”─amqzfuma
│ â”─5*
│ â”─amqzmgr0─┬─amqpcsea
│ │ ... (2 Replies)
Discussion started by: itik
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
can someone explain what does this mean and why does this happen? i had this problem last week, and Unix admin said that he has to rebuild the file system. Now i am getting this error again.
aaaa% ls
. unreadable
:mad: (7 Replies)
Discussion started by: treneryy
7 Replies
5. Shell Programming and Scripting
I have a file like this 07200900.SUP,in a windows directory I need to FTP this file to UNIX , the directory in unix is N:\orgs\Financial Aid\MIIS\0910\FTP
I am getting this error
miis_ftp.ELM_SUP.shl: =cd orgs/"Financial Aid"/"MIIS"/"0910"/"FTP" : not found
IN THE LOG FILE
Activities for Mon... (3 Replies)
Discussion started by: rechever
3 Replies
6. Shell Programming and Scripting
I will appreciate any help with this...
I have a file in this directory that looks like: this
07210900.SUP, I am getting the following error:
Activities for Tue Jul 21 07:29:14 EDT 2009:
File 07210900.SUP does not exist or unreadable
End of activities
The idea is to capture the file in... (1 Reply)
Discussion started by: rechever
1 Replies
7. Filesystems, Disks and Memory
I found a document: Bad block HOWTO for smartmontools
My hard drive is Maxtor:
root]# fdisk -lu /dev/hda
Disk /dev/hda: 81.9 GB, 81964302336 bytes
255 heads, 63 sectors/track, 9964 cylinders, total 160086528 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x3f4e3f4d
... (0 Replies)
Discussion started by: justinian
0 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I developed a java application in Windows and transferred it to a HP-UX environment(using WinSCP) for deployment.
I used "chmod 777 ..." for granting rights to the files.
After I did this, whenever I go into that directory(or it's immediate parent directory) and hit "ls"......it... (4 Replies)
Discussion started by: agnivaccent
4 Replies
9. UNIX and Linux Applications
Can anyone explain why a editable pdf becomes unreadable after edited with okular? (5 Replies)
Discussion started by: cokedude
5 Replies
10. AIX
Hello Folks,
I have got this message:
When I contacted support, they said this is logical filesystem error and it has to do with the filesystem. How can I find out ? (1 Reply)
Discussion started by: filosophizer
1 Replies
LEARN ABOUT CENTOS
trace-cmd-restore
TRACE-CMD-RESTORE(1) TRACE-CMD-RESTORE(1)
NAME
trace-cmd-restore - restore a failed trace record
SYNOPSIS
trace-cmd restore [OPTIONS] [command] cpu-file [cpu-file ...]
DESCRIPTION
The trace-cmd(1) restore command will restore a crashed trace-cmd-record(1) file. If for some reason a trace-cmd record fails, it will
leave a the per-cpu data files and not create the final trace.dat file. The trace-cmd restore will append the files to create a working
trace.dat file that can be read with trace-cmd-report(1).
When trace-cmd record runs, it spawns off a process per CPU and writes to a per cpu file usually called trace.dat.cpuX, where X represents
the CPU number that it is tracing. If the -o option was used in the trace-cmd record, then the CPU data files will have that name instead
of the trace.dat name. If a unexpected crash occurs before the tracing is finished, then the per CPU files will still exist but there will
not be any trace.dat file to read from. trace-cmd restore will allow you to create a trace.dat file with the existing data files.
OPTIONS
-c
Create a partial trace.dat file from the machine, to be used with a full trace-cmd restore at another time. This option is useful for
embedded devices. If a server contains the cpu files of a crashed trace-cmd record (or trace-cmd listen), trace-cmd restore can be
executed on the embedded device with the -c option to get all the stored information of that embedded device. Then the file created
could be copied to the server to run the trace-cmd restore there with the cpu files.
If *-o* is not specified, then the file created will be called
'trace-partial.dat'. This is because the file is not a full version
of something that trace-cmd-report(1) could use.
-t tracing_dir
Used with -c, it overrides the location to read the events from. By default, tracing information is read from the debugfs/tracing
directory. -t will use that location instead. This can be useful if the trace.dat file to create is from another machine. Just tar
-cvf events.tar debugfs/tracing and copy and untar that file locally, and use that directory instead.
-k kallsyms
Used with -c, it overrides where to read the kallsyms file from. By default, /proc/kallsyms is used. -k will override the file to read
the kallsyms from. This can be useful if the trace.dat file to create is from another machine. Just copy the /proc/kallsyms file
locally, and use -k to point to that file.
-o output'
By default, trace-cmd restore will create a trace.dat file (or trace-partial.dat if -c is specified). You can specify a different file
to write to with the -o option.
-i input
By default, trace-cmd restore will read the information of the current system to create the initial data stored in the trace.dat file.
If the crash was on another machine, then that machine should have the trace-cmd restore run with the -c option to create the trace.dat
partial file. Then that file can be copied to the current machine where trace-cmd restore will use -i to load that file instead of
reading from the current system.
EXAMPLES
If a crash happened on another box, you could run:
$ trace-cmd restore -c -o box-partial.dat
Then on the server that has the cpu files:
$ trace-cmd restore -i box-partial.dat trace.dat.cpu0 trace.dat.cpu1
This would create a trace.dat file for the embedded box.
SEE ALSO
trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-extract(1), trace-cmd-reset(1),
trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1)
AUTHOR
Written by Steven Rostedt, <rostedt@goodmis.org[1]>
RESOURCES
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
COPYING
Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under the terms of the GNU Public License (GPL).
NOTES
1. rostedt@goodmis.org
mailto:rostedt@goodmis.org
06/11/2014 TRACE-CMD-RESTORE(1)