Dear friend,
Please start a new thread if you are starting a new topic. Please do not just
reply to a list message for this purpose, since people like me who use
threaded email clients (which show mails as a conversation thread based on
their internal headers) will see your message as part of another conversation
thread and it can disrupt their productivity since they are as a result
unable to peruse their own thread quickly. This is especially true if your
own posting escalates into a long thread of its own.
I am reposting your post as a separate thread.
Thank you.
---------- Forwarded Message ----------
Subject: [SLE] reiserfsck: fubar?
Date: Sunday 04 Sep 2005 12:44
From: Hans Witvliet
To: suse-linux-e@suse.com
Hi list,
Any experience with reiserfsck?
Second drive began report weird messages, and later un-boota-able, that
according too google related to reiser.
Tried reiserfsck, that reported me to issue an reiserfsck --rebuild-tree
Tried it, pass1,2,3 but at the point of syncing, system frooze.
Waited several hours (just in case), then reboot.
Drive remained unbootable.
Again, reiserfsck (without any options) reported that rebuild did not
finish.
re-issued with --rebuild again. finished with some repairs.
tried reiser-fsck: told me id did not complete....
According to the pages, i should have made a copy with dd, but i did not
have some 120G empty space arround.
Am i correct in the thought that the partition is FUBAR
(f* up beyond any repair/recognition) ?
(currently 9.2,
Hans
=============================================================================
ursa:~ # reiserfsck /dev/hdb2 --rebuild-tree
reiserfsck 3.6.18 (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@namesys.com, **
** 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/hdb2) tree
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
Replaying journal..
Reiserfs journal '/dev/hdb2' in blocks [18..8211]: 0 transactions
replayed
###########
reiserfsck --rebuild-tree started at Sat Sep 3 12:30:30 2005
###########
Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 22773899 blocks marked used
Skipping 9097 blocks (super block, journal, bitmaps) 22764802 blocks
will be read
0%.block 1462673: The number of items (14) is incorrect, should be (0) -
corrected
block 1462673: The free space (1459) is incorrect, should be (4072) -
corrected
block 1462685: The number of items (14) is incorrect, should be (0) -
corrected
block 1462685: The free space (1504) is incorrect, should be (4072) -
corrected
Message from syslogd@ursa at Sat Sep 3 12:57:44 2005 ...
ursa kernel: Bad page state at free_hot_cold_page (in process 'kswapd0',
page c1061900)
Message from syslogd@ursa at Sat Sep 3 12:57:44 2005 ...
ursa kernel: flags:0x20000008 mapping:f7b29c98 mapcount:0 count:0
Message from syslogd@ursa at Sat Sep 3 12:57:44 2005 ...
ursa kernel: Backtrace:
Message from syslogd@ursa at Sat Sep 3 12:57:44 2005 ...
ursa kernel: Trying to fix it up, but a reboot is needed
406106 directory entries were hashed with "r5" hash.
"r5" hash is selected
Flushing..finished
Read blocks (but not data blocks) 22764802
Leaves among those 111306
- corrected leaves 1
- leaves all contents of which could not be
saved and deleted 3
pointers in indirect items to wrong area 7 (zeroed)
Objectids found 403843
Pass 1 (will try to insert 111303 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
Flushing..finished
111303 leaves read
109242 inserted
- pointers in indirect items pointing to
metadata 6 (zeroed)
2061 not inserted
####### Pass 2 #######
Pass 2:
0%....20%....40%....60%....80%....100% left 0,
2061 /sec
Flushing..finished
Leaves inserted item by item 2061
Pass 3 (semantic):
####### Pass 3 #########
/tmp/10.0.3/SUSE-10.0-CD-OSS-i386-Beta3-CD1.isovpf-10680: The file
[774014 773995] has the wrong block count in the StatData (1341072) -
corrected to (13410
16)
/usr/local/bin/wx-configvpf-10660: The file [6467 279056] has too big
size in the StatData (16) - corrected to (0)
vpf-10680: The link [6467 279056] has the wrong block count in the
StatData (1) - corrected to (0)
/root/transcode-0.6.10/import/v4l/common.ovpf-10660: The file [240448
241460] has too big size in the StatData (9) - corrected to (0)
vpf-10680: The link [240448 241460] has the wrong block count in the
StatData (1) - corrected to (0)
/frequencies.ovpf-10660: The file [240448 241463] has too big size in
the StatData (14) - corrected to (0)
vpf-10680: The link [240448 241463] has the wrong block count in the
StatData (1) - corrected to (0)
/video.ovpf-10660: The file [240448 241461] has too big size in the
StatData (8) - corrected to (0)
vpf-10680: The link [240448 241461] has the wrong block count in the
StatData (1) - corrected to (0)
/audio.ovpf-10660: The file [240448 241462] has too big size in the
StatData (8) - corrected to (0)
vpf-10680: The link [240448 241462] has the wrong block count in the
StatData (1) - corrected to (0)
Flushing..finished
Files found: 355304
Directories found: 28131
Symlinks found: 7570
Others: 12827
Files with fixed size: 5
Pass 3a (looking for lost dir/files):
####### Pass 3a (lost+found pass) #########
Looking for lost directories:
Looking for lost files:8 /sec
Flushing..finished, 1202 /sec
Objects without names 5
Files linked to /lost+found 5
Pass 4 - finisheddone 54426, 2267 /sec
Flushing..finished
Syncing..
