All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Markus Müller" <mm@priv.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Reiserfsck dies
Date: Wed, 03 May 2006 19:19:21 +0200	[thread overview]
Message-ID: <4458E619.8090501@priv.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0605031842260.13546@yvahk01.tjqt.qr>

Hi Jan Engelhardt,
>> Hi Linux kernel users,
>>
>> reiserfsck told me that I have to run --rebuild-tree to fix all errors. But
>> this don't work (see below), I tried two times (every time I am waiting 28
>> hours). If I mount the filesystem, there are no files in it. What can I do?
>>     
>
> Is the harddisk broken? (Check for spurious IDE warnings in /var/log/...)
> It is possible that fsck zeroed out many entries because they were not 
> readable.
>   
no, the hdd is a software raid 5, /dev/md0, which is piped through aes
via cryptsetup, so it is accessed via /dev/mapper/hdb (it is not
/dev/hdb, which you could think about the name, but /dev/md0). There
were memory problems, so the reiserfs got inconsistent. But it STILL
worked before I run reiserfsck --rebuild-tree! Just reiserfsck --check
told me to run this command, this is the only cause I run it.
>   
>> stacker:/# dmesg
>> oop0: warning: vs-5150: search_by_key: invalid format found in block 1770409.
>> Fsck?
>> ReiserFS: loop0: warning: vs-13070: reiserfs_read_locked_inode: i/o failure
>>     
> [...]
>
> reiserfs warnings, but no lowlevel warnings :-/
> Did, by chance, you use dm-flakey?
>   
Please tell me, what is dm-flakey?

Regards
Markus Mueller



  reply	other threads:[~2006-05-03 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-03 14:56 Reiserfsck dies Markus Müller
2006-05-03 16:45 ` Jan Engelhardt
2006-05-03 17:19   ` Markus Müller [this message]
2006-05-03 17:30     ` Andreas Steinmetz
2006-05-03 17:48       ` Markus Müller
     [not found]       ` <4458ECE0.7030901@priv.de>
2006-05-03 17:52         ` Andreas Steinmetz
2006-05-03 17:56 ` Sergey Vlasov
2006-05-03 18:18   ` Markus Müller
2006-05-03 19:12     ` Jan Engelhardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4458E619.8090501@priv.de \
    --to=mm@priv.de \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.