Sponsored Content
Full Discussion: file corruption
Top Forums UNIX for Advanced & Expert Users file corruption Post 27707 by shibz on Thursday 5th of September 2002 11:30:08 AM
Old 09-05-2002
file corruption

Hi,

All of a sudden I landed in a strange problem.

I was working with my C source code in vi editor. I did a wq! and
when reopened, the file is full of "data".. I mean the text contents are gone!!.

I believe this is a file corruption. I have tried the -r option with vi, but no success.

Is there any way to recover the file. ??

Thanks in Advance...
 

10 More Discussions You Might Find Interesting

1. Windows & DOS: Issues & Discussions

NTFS corruption under w2k but not under suse 9.2

Hello all, I´ve bumped into some strange things with a NTFS partition of mine. I am running a dual boot machine with w2k and suse 9.2. I just reinstalled w2k on it. After that one of my NTFS partitions stopped working under windows. Though it is perfectly readable from linux. Windows sees the... (4 Replies)
Discussion started by: mickepe
4 Replies

2. UNIX for Advanced & Expert Users

rsync data corruption

Dear Peoples I am using the following command to transfer the files inbetween two servers, i am using this command in a crontab for doing it in every 1 hour on all days. rsync --stats --archive --verbose --compress --force --rsh=ssh --exclude-from=/root/cfg/mkt_scn.exclude... (1 Reply)
Discussion started by: thameema
1 Replies

3. AIX

File System Corruption on IBM DS8300

Hi All, We are facing the problem of file system corruption on DS8300,we have done very much effort to find out the root cause of problem but we still not get any success, we have AIX 5.3 OS installed on system with latest patches, we have upgraded HBA firmwares, DS8300 firmware, System... (5 Replies)
Discussion started by: m_raheelahmed
5 Replies

4. Solaris

Data corruption

I have a solaris 5.6 on which oracle is installed. we have an alert file alert_net1.log now whenever any datacorruption happens we get the file id and block id in the above file. through this file and block id , we try to find out which table is corrupted and then try to... (1 Reply)
Discussion started by: asalman.qazi
1 Replies

5. Emergency UNIX and Linux Support

DSEE LDAP corruption

Today when someone was using Sun Identity Manager to modify a directory managed by Sun Directory Server Enterprise Edition (DSEE 6.3) IDM spit out an object class violation error (I verified that the input data was valid). It also corrupted the directory to the point where I can't even get dsadm to... (7 Replies)
Discussion started by: ilikecows
7 Replies

6. UNIX for Advanced & Expert Users

File system testing for Data corruption

Hi, could any one tell is there any test-suite or any idea How to do data corruption validation testing, means there is no any data corruption ? Regards Manish (1 Reply)
Discussion started by: manish_tcs_hp
1 Replies

7. Emergency UNIX and Linux Support

XDMCP and VNC graphics corruption

I'm trying to create a persistent KDE session and access that login remotely. While logged into the remote machine I have enabled XDMCP and started a VNC server that requests a login screen. vnc4server -query localhost -geometry 800x480 -depth 8 When I try to view that vnc screen the... (5 Replies)
Discussion started by: cue
5 Replies

8. Programming

FORTRAN: double free or corruption

Hello. I'm looking for a quite "interesting" bug I'm using fortran 90, compiler gfortran and the main idea is for every time step I build a bin structure for search contact between particles, for this at the begining TYPE :: circle_index INTEGER(kind = 4) :: ind_p TYPE(circle_index),... (1 Reply)
Discussion started by: Marce
1 Replies

9. UNIX for Advanced & Expert Users

File System corruption

Hi, While a tar file was created, the file system got full and there was no message on the tar failure. Then the system was shut down and the administrator says because the file system was full the shut down procedure corrupted the file system. I'm wondering, unix should have given some... (2 Replies)
Discussion started by: manivanm
2 Replies

10. Solaris

Root user not recognizing on Solaris-10 (shadow file corruption)

Hello, I got into a wired state on one of solaris 10 server. When I noticed that server is having some issue, I found that there were dumpadm.conf entries in /etc/shadow and real entries were wiped of. Probably somebody fat fingers. I was able to boot into failsafe, break SVM mirror, copied... (25 Replies)
Discussion started by: solaris_1977
25 Replies
REISERFSCK(8)						      System Manager's Manual						     REISERFSCK(8)

NAME
reiserfsck - check a Linux Reiserfs file system SYNOPSIS
reiserfsck [ -afprVy ] [ --check | --fix-fixable | --rebuild-sb | --rebuild-tree | --clean-attributes ] [ -j | --journal-device device ] [ --no-journal-available ] [ -z | --adjust-file-size ] [ -S | --scan-whole-partition ] [ -l | --logfile filename ] [ -n | --nolog ] [ -q | --quiet ] device DESCRIPTION
Reiserfsck searches for a Reiserfs filesystem on a device, replays any necessary transactions, and either checks or repairs the file sys- tem. device is the special file corresponding to the device or partition (e.g /dev/hdXX for IDE disk partition or /dev/sdXX for SCSI disk parti- tion). OPTIONS
--check This default action checks file system consistency and reports but does not repair any corruption that it finds. This option may be used on a read-only file system mount. The --check option exits with status 0 to indicate that no corruption was found. Otherwise, reiserfsck returns 1 to indicate corruption that can be fixed with --fix-fixable and 2 to indicate corruption that requires --rebuild-tree. --fix-fixable This option recovers certain kinds of corruption that do not require rebuilding the entire file system tree (--rebuild-tree). Nor- mally you only need this option if the --check option reports "corruption that can be fixed with --fix-fixable". This includes: zeroing invalid data-block pointers, correcting st_size and st_blocks for directories, and deleting invalid directory entries. --rebuild-sb This option recovers the superblock on a Reiserfs partition. Normally you only need this option if mount reports "read_super_block: can't find a reiserfs file system" and you are sure that a Reiserfs file system is there. --rebuild-tree This option rebuilds the entire file system tree using leaf nodes found on the device. Normally you only need this option if the --check option reports "corruption that can be fixed only during --rebuild-tree". You are strongly encouraged to make a backup copy of the whole partition before attempting the --rebuild-tree option. --clean-attributes This option cleans reserved fields of Stat-Data items. --journal-device device , -j device This option supplies the device name of the current file system journal. This option is required when the journal resides on a sep- arate device from the main data device (although it can be avoided with the expert option --no-journal-available). --adjust-file-size, -z This option causes reiserfsck to correct file sizes that are larger than the offset of the last discovered byte. This implies that holes at the end of a file will be removed. File sizes that are smaller than the offset of the last discovered byte are corrected by --fix-fixable. --logfile filename, -l filename This option causes reiserfsck to report any corruption it finds to the specified log file rather than stderr. --nolog, -n This option prevents reiserfsck from reporting any kinds of corruption. --quiet, -q This option prevents reiserfsck from reporting its rate of progress. -a, -p These options are usually passed by fsck -A during the automatic checking of /etc/fstab partitions. For compatibility, these options simply cause reiserfsck to print information about the specified file system. No checks are performed. When it is set - reiserfsck assumes that it is called by fsck -A, provides some information about the specified filesystem and exits. -V This option prints the reiserfsprogs version and exit. -r, -p, -y These options are ignored. -V, -f prints version and exits EXPERT OPTIONS
DO NOT USE THESE OPTIONS UNLESS YOU KNOW WHAT YOU ARE DOING. WE ARE NOT RESPONSIBLE IF YOU LOSE DATA AS A RESULT OF THESE OPTIONS. --no-journal-available This option allows reiserfsck to proceed when the journal device is not available. This option has no effect when the journal is located on the main data device. NOTE: after this operation you must use reiserfstune to specify a new journal device. --scan-whole-partition, -S This option causes --rebuild-tree to scan the whole partition, not only used space on the partition. EXAMPLE OF USING
1. You think something may be wrong with a reiserfs partition on /dev/hda1 or you would just like to perform a periodic disk check. 2. Run reiserfsck --check --logfile check.log /dev/hda1. If reiserfsck --check exits with status 0 it means no errors were discovered. 3. If reiserfsck --check exits with status 1 (and reports about fixable corruptions) it means that you should run reiserfsck --fix-fixable --logfile fixable.log /dev/hda1. 4. If reiserfsck --check exits with status 2 (and reports about fatal corruptions) it means that you need to run reiserfsck --rebuild-tree. If reiserfsck --check fails in some way you should also run reiserfsck --rebuild-tree, but we also encourage you to submit this as a bug report. 5. Before running reiserfsck --rebuild-tree, please make a backup of the whole partition before proceeding. Then run reiserfsck --rebuild- tree --logfile rebuild.log /dev/hda1. 6. If the --rebuild-tree step fails or does not recover what you expected, please submit this as a bug report. Try to provide as much information as possible and we will try to help solve the problem. SH EXIT CODES eiserfsck uses the following exit codes: 0 - No errors. 1 - Errors found, esierfsck --fix-fixable needs to be launched. 2 - Errors found, esierfsck --rebuild-tree needs to be launched. 8 - Operational error. 16 - Usage or syntax error. AUTHOR
This version of reiserfsck has been written by Vitaly Fertman <vitaly@namesys.com> and Vladimir Saveliev <vs@namesys.com>. BUGS
There are likely to be some bugs. Please report bugs to the ReiserFS mail-list <reiserfs-list@namesys.com>. TODO
Faster recovering, signal handling, i/o error handling, return reasonable exit codes, etc. SEE ALSO
mkreiserfs(8), debugreiserfs(8), reiserfstune(8) Reiserfsprogs-3.6.4 January 2002 REISERFSCK(8)
All times are GMT -4. The time now is 01:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy