Oleg Drokin wrote:
Hello!
On Tue, Aug 20, 2002 at 04:24:13PM -0400, Chris Mason wrote:
make sure it was valid, regardless of where you stored it. The problem
is that if you store it in the tree somehow, you've got a chicken and
egg problem that you can't read the list until the tree is
On Mon, 2002-08-19 at 06:20, Oleg Drokin wrote:
Hello!
On Mon, Aug 19, 2002 at 02:07:26PM +0400, Hans Reiser wrote:
He suggests that user should specify list of bad blocks each time user runs
reiserfsck.
This sounds reasonable. You can probably even have a default location
Not
Hi Vitaly,
Your analysis is dead-on!
I ran reiserfsck a second time, and this time it stopped later.
The strange thing is this disk and installation are relatively new
(March 2002), and digging back through syslogs shows occurances
(kernel)(.*)(hda) only on:
4 May 20 (2 sectors)
370 Aug 15
Hi Matthias,
No way fsck caused these. The problems were there, you just did not see
them, because you did not read the defective blocks before. Unless the
drive has suffered inadequate treatment, (dropped, computer kicked or
bumped into, overheat) better return it for warranty repair or
Gerrit Hannaert [EMAIL PROTECTED] writes:
Is there a difference in the way reiserfs formats as opposed to ext2/3?
Your mentioning the defective blocks were never read before reminds me
Well, the long explanation is, that the blocks may not have been used
for some time, or that they have gone
Stefan Fleiter [EMAIL PROTECTED] writes:
Hi Vitaly!
On Thu, 15 Aug 2002 Vitaly Fertman wrote:
Ah, I guess I know what happened. I think you have some fatal corruptions and
rebuild-tree is required. In this case check and fix-fixable do not perform
semantic check.
Then reiserfsck
On Fri, 16 Aug 2002, at 6:24pm, Hans Reiser wrote:
A colleague of mine back when I was part of a sysadmin department used to
write to every block on the drive before installing the OS on it. I think
he was right to do so. I have considered having mkreiserfs ask the user
if he wants to do
