ReiserFS question

ReiserFS question

[Samium Gromoff]

      Hi People...
   got a following "dead of alive" question:
   how to find a root block on a ReiserFS partition
   with a corrupted superblock?

   reiserfsprogs-3.x.0.9j simply writes -2^32
   there at start (reset_super_block) and then simply
   crashes when attempting to access to such mad place
          ... got nearly lost my main partition ...


 sorry for bad english

Re: ReiserFS question

[Chris Mason]

On Thursday, April 26, 2001 11:05:25 PM +0400 Samium Gromoff
<_deepfire@mail.ru> wrote:

>       Hi People...
>    got a following "dead of alive" question:
>    how to find a root block on a ReiserFS partition
>    with a corrupted superblock?
> 
>    reiserfsprogs-3.x.0.9j simply writes -2^32
>    there at start (reset_super_block) and then simply
>    crashes when attempting to access to such mad place
>           ... got nearly lost my main partition ...
> 
> 

The reiserfsck ---rebuild-tree will find the root block for you.  Now that
you've rebuilt the super, run with --rebuild-tree and it should find
everything.

-chris

Re[2]: Q: HowTo Nullify journal on badblks?

[Samium Gromoff]

         Hello busy peoples, again me...
      Today got my 45gb drive slightly badblocked:
   about 70 MB in beginning... thus problem arose:
   bitmaps are heavily corrupted, and debugreiserfs  
   with -p crashes while trying to dump journal
   (he`s not alone in such behaviour: evryone doing
    that fails with Segfault). I need to dump
   all metadata to refresh bitmaps etc, but i can`t.
   
   3.x.0j-pre2/linux-2.4.4

   what do i have to do?

   i can provide a strace of segfaulted --fix-fixable
            thanks in advance        

Re[2]: ReiserFS question

[Samium Gromoff]

       Info addon, sorry for that:
    these bblks are quite writeable, so it`s ok to
    rewrite `em to rebuild.

reiserfs question

[lk]

Hi,

I run slackware-linux 8.0 and when I restart my box without issuing the
halt command, I see the following message when the kernel boots:

reiserfs: checking transaction log (device 03:01) ...
Warning, log replay starting on readonly filesystem
Using r5 hash to sort names
ReiserFS version 3.6.25
VFS: Mounted root (reiserfs filesystem) readonly.
Mounted devfs on /dev
Freeing unused kernel memory: 184k freed
Adding Swap: 100796k swap-space (priority -1)

My question is: why does it says "Warning...." ? The boot scripts are the
ones installed by slackware installer by default. Is the root filesystem
supposed to be mounted read/write at boot (i ask this because when I had
an ext2 partition it was mounted first readonly, and then readwrite) ?


Regards,

Re: reiserfs question

[Justin Guyett]

On Sun, 19 Aug 2001 lk@Aniela.EU.ORG wrote:

> I run slackware-linux 8.0 and when I restart my box without issuing the
> halt command, I see the following message when the kernel boots:
>
> reiserfs: checking transaction log (device 03:01) ...
> Warning, log replay starting on readonly filesystem

Perhaps you have a "read-only" line in the lilo.conf section for whatever
kernel you're booting.  It's possible that initscripts are remounting the
partition read-only, but not likely, and if you're using journalling, it's
best to check your initscripts and get rid of all the junk that runs
e2fsck and then remounts read-write.


justin