Mailinglist Archive: opensuse (2912 mails)

< Previous Next >
Re: [SLE] Failed ReiserFS (more)
  • From: Rikard Johnels <rikjoh@xxxxxxxxx>
  • Date: Thu, 10 Feb 2005 05:09:25 +0100
  • Message-id: <200502100509.25613.rikjoh@xxxxxxxxx>
On Wednesday 09 February 2005 15.33, Rikard Johnels wrote:
> Hi all!
>
> I have a client that have lost two 30 gig disks with a huge number of
> files he uses in a project.
> The server (Linux SuSE 9.1) suddenly hickuped, and when it came back there
> was files on the discs but no NFS. ('df showed about 75% usage of the
> discs) After restart of NFS a 'df' shows total use 1% and the files are
> gone By some reason (so far unknown) the disk is suddenly empty.
> They are created under Linux and uses ReiserFS, so he thought them to be
> "safe". (No he didn't back them up regardles of warnings from me)
>
> I did a 'dd if=/dev/hdc of=image.hdc and if i look at that file i can see
> all the data. I can find all filenames but the fat seems empty.
> Is there a safe way to try to restore the lost files?
> Parttitiontable is OK. ReiserFS in it self didn't complain about anything,
> and SMART didn't register any failing disks.
>
> Where shall i start to look?
> --
>
> /Rikard
>
> ---------------------------------------------------------------
> Rikard Johnels email : rikjoh@xxxxxxxxx
> Web : http://www.rikjoh.com/users/rikjoh
> Mob : +46 735 05 51 01
> PGP : 0x461CEE56
> ---------------------------------------------------------------

Tried running a recovery as described in the manpages;

talen:~ # reiserfsck --rebuild-tree -S /dev/hdc1
--logfile /root/reisercheck.logfile

reiserfsck 3.6.13 (2003 www.namesys.com)

*************************************************************
** Do not run the program with --rebuild-tree unless **
** something is broken and MAKE A BACKUP before using it. **
** If you have bad sectors on a drive it is usually a bad **
** idea to continue using it. Then you probably should get **
** a working hard drive, copy the file system from the bad **
** drive to the good one -- dd_rescue is a good tool for **
** that -- and only then run this program. **
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@xxxxxxxxxxx, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************

Will rebuild the filesystem (/dev/hdc1) tree
Will put log info to '/root/reisercheck.logfile'

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
Replaying journal..
Reiserfs journal '/dev/hdc1' in blocks [18..8211]: 0 transactions replayed
###########
reiserfsck --rebuild-tree started at Thu Feb 10 04:06:56 2005
###########

Pass 0:
The whole partition (7504544 blocks) is to be scanned
Skipping 8440 blocks (super block, journal, bitmaps) 7496104 blocks will be
read
0%....20%....40%....60%....80%....100% left 0,
4152 /sec
"r5" hash is selected
Flushing..finished
Read blocks (but not data blocks) 7496104
Leaves among those 11690
- corrected leaves 2
- leaves all contents of which could not be saved and
deleted 3
Objectids found 7008

Pass 1 (will try to insert 11687 leaves):
Looking for allocable blocks .. finished
0%....20%....40%....60%....80%....100% left 0,
299 /sec
Flushing..finished
11687 leaves read
9652 inserted
2035 not inserted
non-unique pointers in indirect items (zeroed) 95044

Pass 2:
0%....20%....40%....60%....80%....100% left 0,
2035 /sec
Flushing..finished
Leaves inserted item by item 2035
Pass 3 (semantic):
Flushing..finished
Files found: 4292
Directories found: 356
Broken (of files/symlinks/others): 3
Files with fixed size: 1
Names pointing to nowhere (removed): 112
Pass 3a (looking for lost dir/files):
Looking for lost directories:
Looking for lost files:
lost+found.c 348 pass_3a_look_for_lost
look_for_lost: The entry 'lost+found' could not be found in the root
directory.
Aborted

talen:~ # ls -l /lost+found
(trimmed)
drwxr-xr-x 4 root root 80 Feb 10 04:09 lost+found
talen:~ #


The lines;
'lost+found.c 348 pass_3a_look_for_lost
look_for_lost: The entry 'lost+found' could not be found in the root
directory. '
seems to be very wrong.
What can i do?


--

/Rikard

---------------------------------------------------------------
Rikard Johnels email : rikjoh@xxxxxxxxx
Web : http://www.rikjoh.com/users/rikjoh
Mob : +46 735 05 51 01
PGP : 0x461CEE56
---------------------------------------------------------------

< Previous Next >
Follow Ups
References