All of lore.kernel.org
 help / color / mirror / Atom feed
* No mount of reiserfs 3.6 after power loss
@ 2010-05-10 16:03 Bernhard Sadlowski
  2010-05-11 12:10 ` Bernhard Sadlowski
  0 siblings, 1 reply; 2+ messages in thread
From: Bernhard Sadlowski @ 2010-05-10 16:03 UTC (permalink / raw)
  To: reiserfs-devel

Hello,

I have trouble to mount a reiserfs 3.6 filesystem after a power loss. It is 
living on a md raid1 (2xSATA) with cryptsetup. I have used this setup for 
years without any problem so far. With "strings" I see data and text inside 
the /dev/mapper/... device, so it seems the data could be intact.

[139977.209415] REISERFS (device dm-2): found reiserfs format "3.6" with 
standard journal
[139977.209852] REISERFS (device dm-2): using ordered data mode
[139977.214845] attempt to access beyond end of device
[139977.214858] dm-2: rw=0, want=18401083744, limit=1781801088
[139977.214870] REISERFS warning (device dm-2): sh-459 journal_init: unable to 
read journal header
[139977.247350] REISERFS warning (device dm-2): sh-2022 reiserfs_fill_super: 
unable to initialize journal space

I found also a mail with similiar content from 5/2009 but no solution: 
http://marc.info/?l=reiserfs-devel&m=124143380020910&w=2

I can break the mirror and experiment with the second copy. 

The System is Debian:

# uname -a
Linux k8 2.6.32-trunk-vserver-amd64 #1 SMP Sun Jan 10 23:45:41 UTC 2010 x86_64 
GNU/Linux

# fdisk -l /dev/sda

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xff7911e5

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        3917    31463271    7  HPFS/NTFS
/dev/sda2            3918       10445    52436160   83  Linux
/dev/sda3           10446       10689     1959930   82  Linux swap / Solaris
/dev/sda4           10690      121601   890900640   fd  Linux raid autodetect

#fdisk -l /dev/sdb

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00f7cee4

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1        3917    31463271    b  W95 FAT32
/dev/sdb2   *        3918       10445    52436160   83  Linux
/dev/sdb3           10446       10689     1959930   82  Linux swap / Solaris
/dev/sdb4           10690      121601   890900640   fd  Linux raid autodetect

sda4 + sdb4 are the mirrors.

My Steps so far:

1) I tried to reiserfsck with --check, result:

bread: Cannot read the block (2535232620): (Invalid argument).

reiserfs_open: Your partition is not big enough to contain the 
filesystem of (2535232620) blocks as was specified in the found super block.
Failed to open the filesystem.

If the partition table has not been changed, and the partition is
valid  and  it really  contains  a reiserfs  partition,  then the
superblock  is corrupted and you need to run this utility with
--rebuild-sb.

2) next --rebuild-sb and then --check tells me to run --rebuild-tree. After

# reiserfsck --rebuild-tree
 
most of the files are gone. 

3) I will just try to recover with the -S option, but I hoped to get the 
directory structure intact without any files in lost+found.

Any advice? 

Thanks,
Bernhard

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: No mount of reiserfs 3.6 after power loss
  2010-05-10 16:03 No mount of reiserfs 3.6 after power loss Bernhard Sadlowski
@ 2010-05-11 12:10 ` Bernhard Sadlowski
  0 siblings, 0 replies; 2+ messages in thread
From: Bernhard Sadlowski @ 2010-05-11 12:10 UTC (permalink / raw)
  To: reiserfs-devel

Am Montag 10 Mai 2010 schrieb Bernhard Sadlowski:
> Hello,
>
> I have trouble to mount a reiserfs 3.6 filesystem after a power loss. It is
> living on a md raid1 (2xSATA) with cryptsetup. I have used this setup for
> years without any problem so far. With "strings" I see data and text inside
> the /dev/mapper/... device, so it seems the data could be intact.
>
> [139977.209415] REISERFS (device dm-2): found reiserfs format "3.6" with
> standard journal
> [139977.209852] REISERFS (device dm-2): using ordered data mode
> [139977.214845] attempt to access beyond end of device
> [139977.214858] dm-2: rw=0, want=18401083744, limit=1781801088
> [139977.214870] REISERFS warning (device dm-2): sh-459 journal_init: unable
> to read journal header
> [139977.247350] REISERFS warning (device dm-2): sh-2022
> reiserfs_fill_super: unable to initialize journal space
>
> I found also a mail with similiar content from 5/2009 but no solution:
> http://marc.info/?l=reiserfs-devel&m=124143380020910&w=2
>
> I can break the mirror and experiment with the second copy.

Everything is fine again! I can mount the filesystem again. Solution for
my issue and to the issue above was, that the wrong cipher was used. 

I did an upgrade of debian/sid and got updates for the kernel 2.6.32 and
for cryptsetup to version 1.1.0. Probably the default cipher did change
without notice. After a power loss and reboot this problem occured, but
it was not the power loss itself.

Bernhard

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2010-05-11 12:10 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-05-10 16:03 No mount of reiserfs 3.6 after power loss Bernhard Sadlowski
2010-05-11 12:10 ` Bernhard Sadlowski

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.