Hello,
As the subject would imply, I've been having problems with 2.4.x. I have
my root partition (/dev/hda1) as reiserfs and also have another harddrive
with a reiserfs partition (/dev/hdc1). Several programs write (e.g. save
files to) /dev/hdc1, and I also store files there. Under 2.4.2, whenever
manually copying files from hda1 to hdc1, I would get a kernel panic, the
kernel would dump the contentx of the registers onto any consoles open at
that moment, and then the machine would freeze. Upon rebooting, the
machine would work flawlessly until I tried to repeat the same procedure.
Curiously enough, this did not happen under 2.4.1 (I would sometimes
reboot under 2.4.1, do my copying, then reboot back under 2.4.2). I'm
fairly sure that I checked that this did not happen under 2.4.3.
Tonight,however, I tried to copy from hda1 to hdc1 and had several
problems. The first 2 times I did it, I received segfaults. The third
time, the process hung. I changed from X to the console to kill it. After
doing this, the keyboard would not communicate with X, meaning that all I
could do was move the mouse, or change back to the console. After changing
back to the console again, the kernel panicked, dumped the registers, and
crashed. Upon reboot, the kernel panicked when reiserfs was called (in
init). Upon a 2nd reboot (and all non-floppy boots since then), I receive
"Error 17" from GRUB and the computer hangs.
My apologies that I can't provide a log, but I can't access the
computer. I've tried rebooting with a rescue disk, and I get a message
when reiserfs is called that contains the following messages (among
others):
reiserfs_read_super: can't find reiserfs filesystem on dev 03:01
Invalid session # or type of track
Kernel panic: VFS: Unable to mount root fs on 03:01
In case it's any help, I'm running Debian "sid" under kernel 2.4.3. hda
is a Western Digital WD400 (UDMA 100) while hdc is a Maxtor 36.5 GB. I
have a 900 Mhz Athlon on an Abit KT7A, the latter containing the South
Bridge VIA VT82C686B and a North Bridge VIA VT8363A.
Any info on how I could possibly retrieve data from my disk (hda) would
be greatly appreciated...
Thanks
Jason Frantz
On Friday, April 27, 2001 02:40:50 AM -0700 jason
<[email protected]> wrote:
[ ouch ]
>
> reiserfs_read_super: can't find reiserfs filesystem on dev 03:01
> Invalid session # or type of track
> Kernel panic: VFS: Unable to mount root fs on 03:01
>
> In case it's any help, I'm running Debian "sid" under kernel 2.4.3. hda
> is a Western Digital WD400 (UDMA 100) while hdc is a Maxtor 36.5 GB. I
> have a 900 Mhz Athlon on an Abit KT7A, the latter containing the South
> Bridge VIA VT82C686B and a North Bridge VIA VT8363A.
> Any info on how I could possibly retrieve data from my disk (hda) would
> be greatly appreciated...
>
Looks like you've hit the pot-luck of VIA problems, and elevator bugs
(2.4.1). When the last crash hit, did you recycle with the power button or
the reset button?
Step one, if you can, get a backup of the raw device. This will make
everything easier if there are problems in step 3.
Step two, grab the latest reiserfsprogs from
ftp.reiserfs.org/pub/reiserfsprogs.
Step three, reiserfsck --rebuild-sb ; reiserfsck --rebuild-tree
Drop me a line if there are any questions.
-chris
jason wrote:
> Hello,
>
> As the subject would imply, I've been having problems with 2.4.x. I have
> my root partition (/dev/hda1) as reiserfs and also have another harddrive
> with a reiserfs partition (/dev/hdc1). Several programs write (e.g. save
> files to) /dev/hdc1, and I also store files there. Under 2.4.2, whenever
> manually copying files from hda1 to hdc1, I would get a kernel panic, the
Reiserfs doesn't cope well with crashes.... Under 2.4 I wouldn't
recommend using it on any kind of critical server - it seems to
progressively corrupt itself (I'm looking at the second reformat and
reinstall in a week, and I'm not a happy bunny).
As the warning on reiserfsck says, the rebuild-tree option is a last
resort. It's as likely to make the problem worse then improve it (It
rounds all the file lengths up to a block size, padding with zeros,
which breaks lots of stuff). Backup what you can first.
I find that if you run reiserfsck -x /dev/hda1 a couple of dozen times
it slowly fixes stuff that it couldn't fix on the previous pass.One
thing that can't fix is the bug that seems to make random files on the
FS unreadable even for root.The only way I've found around that one is a
periodic format/reinstall.
Tony
--
Where a calculator on the ENIAC is equpped with 18,000 vaccuum
tubes and weighs 30 tons, computers in the future may have only
1,000 vaccuum tubes and perhaps weigh 1 1\2 tons.
-- Popular Mechanics, March 1949
[email protected]
On Friday, April 27, 2001 04:33:15 PM +0100 Tony Hoyle
<[email protected]> wrote:
> Reiserfs doesn't cope well with crashes.... Under 2.4 I wouldn't
> recommend using it on any kind of critical server - it seems to
> progressively corrupt itself (I'm looking at the second reformat and
> reinstall in a week, and I'm not a happy bunny).
Could you please forward along the details of these corruptions (including
hardware)?
>
> As the warning on reiserfsck says, the rebuild-tree option is a last
> resort. It's as likely to make the problem worse then improve it (It
> rounds all the file lengths up to a block size, padding with zeros, which
> breaks lots of stuff). Backup what you can first.
It shouldn't always do this, most of the time it has enough info to get the
size right. Which reiserfsck did you use?
-chris
To your complaint, I have to add my kudos. I frequently run into
crashes and I have only had reiserfs filesystem that I had to rebuild in
well over a year of using it on half a dozen workstations. I use 2.4
exclusively and have often had "premature restarts".
David
Tony Hoyle wrote:
> jason wrote:
>
>> Hello,
>>
>> As the subject would imply, I've been having problems with 2.4.x. I have
>> my root partition (/dev/hda1) as reiserfs and also have another
>> harddrive
>> with a reiserfs partition (/dev/hdc1). Several programs write (e.g. save
>> files to) /dev/hdc1, and I also store files there. Under 2.4.2, whenever
>> manually copying files from hda1 to hdc1, I would get a kernel panic,
>> the
>
>
>
> Reiserfs doesn't cope well with crashes.... Under 2.4 I wouldn't
> recommend using it on any kind of critical server - it seems to
> progressively corrupt itself (I'm looking at the second reformat and
> reinstall in a week, and I'm not a happy bunny).
>
> As the warning on reiserfsck says, the rebuild-tree option is a last
> resort. It's as likely to make the problem worse then improve it (It
> rounds all the file lengths up to a block size, padding with zeros,
> which breaks lots of stuff). Backup what you can first.
>
> I find that if you run reiserfsck -x /dev/hda1 a couple of dozen times
> it slowly fixes stuff that it couldn't fix on the previous pass.One
> thing that can't fix is the bug that seems to make random files on the
> FS unreadable even for root.The only way I've found around that one is
> a periodic format/reinstall.
>
> Tony
>