mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sonny Rao <sonny@burdell.org>
To: Hans Reiser <reiser@namesys.com>
Cc: Chris Mason <mason@suse.com>, Dave Jones <davej@redhat.com>,
	linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
	Vitaly Fertman <vetalf@inbox.ru>
Subject: Re: kernel oops: trying to mount a corrupted xfs partition (2.6.16-rc3)
Date: Mon, 20 Feb 2006 11:41:20 -0500	[thread overview]
Message-ID: <20060220164120.GA24077@kevlar.burdell.org> (raw)
In-Reply-To: <43F96DE9.7070209@namesys.com>

(trimmed the cc list a bit since this is all Reiserfs specific)

On Sun, Feb 19, 2006 at 11:21:13PM -0800, Hans Reiser wrote:
> Thanks kindly Sonny, Chris is this bug known/fixed?

Hi, I'm still seeing the issue on 2.6.16-rc4 so I don't think it's
fixed yet. 

Here's some output :

Feb 20 10:36:25 localhost kernel: ReiserFS: loop0: found reiserfs format "3.6" with standard journal
Feb 20 10:36:25 localhost kernel: ReiserFS: loop0: using ordered data mode
Feb 20 10:36:25 localhost kernel: ReiserFS: loop0: journal params: device loop0, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
Feb 20 10:36:25 localhost kernel: ReiserFS: loop0: checking transaction log (loop0)
Feb 20 10:36:27 localhost kernel: __find_get_block_slow() failed. block=18446744072887476243, b_blocknr=3472891923
Feb 20 10:36:27 localhost kernel: b_state=0x00000020, b_size=4096
Feb 20 10:36:27 localhost kernel: device blocksize: 4096
Feb 20 10:36:27 localhost kernel: __find_get_block_slow() failed. block=18446744072887476243, b_blocknr=3472891923
Feb 20 10:36:27 localhost kernel: b_state=0x00000020, b_size=4096
Feb 20 10:36:27 localhost kernel: device blocksize: 4096
Feb 20 10:36:27 localhost kernel: __find_get_block_slow() failed. block=18446744072887476243, b_blocknr=3472891923
Feb 20 10:36:27 localhost kernel: b_state=0x00000020, b_size=4096
Feb 20 10:36:27 localhost kernel: device blocksize: 4096
Feb 20 10:36:27 localhost kernel: __find_get_block_slow() failed. block=18446744072887476243, b_blocknr=3472891923
Feb 20 10:36:27 localhost kernel: b_state=0x00000020, b_size=4096
Feb 20 10:36:27 localhost kernel: device blocksize: 4096
...
ad infinitum

I'll try and add a dump_stack() to the code that prints this stuff later today

Sonny




> 
> Sonny Rao wrote:
> 
> >On Sun, Feb 19, 2006 at 04:52:09PM -0500, Dave Jones wrote:
> ><snip> 
> >  
> >
> >>Just for kicks, I just hacked this up..
> >>
> >>#!/bin/bash
> >>wget http://www.digitaldwarf.be/products/mangle.c
> >>gcc mangle.c -o mangle
> >>
> >>dd if=/dev/zero of=data.img count=70000
> >>
> >>while [ 1 ];
> >>do
> >>        mkfs.xfs -f data.img >/dev/null
> >>		./mangle data.img $RANDOM
> >>        sudo mount -t xfs data.img mntpt -o loop
> >>        sudo ls -R mntpt
> >>        sudo umount mntpt
> >>done
> >>    
> >>
> >
> >Cool script, you might want to multiply $RANDOM by some factor (I used
> >8) to catch some more stuff, I know JFS, for example, doesn't put
> >anything in the first 32k, so the first time I ran it on JFS it did
> >nothing ;-) 
> >
> >
> >Reiserfs folks, 
> >
> >I also found an infinte loop in Reiserfs on 2.6.15, if the Reiser
> >folks are interested, I've gziped the fs and put it here:
> >
> >http://burdell.org/~sonny/data.img.breaks.reiserfs.gz
> >
> >The fs is only 52k when zipped, so its not too bad to download.
> >
> >This is under stock 2.6.15, sorry I can't post dmesg output because I
> >end up having to reboot when it happens and don't have time to debug
> >right now.  It looks like it's in the journal replay code where it
> >keeps trying to grab some block with a ridiculously large offset. 
> >
> >
> >  
> >
> >>xfs wins the award for 'noisiest fs in the face of corruption' :-)
> >>After a few dozen backtraces from xfs_corruption_error,
> >>this fell out...
> >>
> >>divide error: 0000 [1] SMP
> >>    
> >>
> ><snip trace>
> > 
> >  
> >
> >>(The kernel is based on 2.6.16rc4)
> >>    
> >>
> >
> >I see a similar breakage (divide error) on x86 using 2.6.15
> >
> >Sonny
> >
> >
> >  
> >

  reply	other threads:[~2006-02-20 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 18:36 bjd
2006-02-16 19:31 ` Nathan Scott
2006-02-17 16:54   ` Jan Engelhardt
2006-02-19 21:29     ` Nathan Scott
2006-02-19 21:52       ` Dave Jones
2006-02-20  7:09         ` Sonny Rao
2006-02-20  7:21           ` Hans Reiser
2006-02-20 16:41             ` Sonny Rao [this message]
2006-02-20 17:11               ` Sonny Rao
2006-02-21  2:04           ` Nathan Scott
2006-02-21  4:06             ` Sonny Rao

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=20060220164120.GA24077@kevlar.burdell.org \
    --to=sonny@burdell.org \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@suse.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vetalf@inbox.ru \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®