public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Sonny Rao <sonny@burdell.org>, Chris Mason <mason@suse.com>
Cc: Dave Jones <davej@redhat.com>, Nathan Scott <nathans@sgi.com>,
	Jan Engelhardt <jengelh@linux01.gwdg.de>, bjd <bjdouma@xs4all.nl>,
	linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com,
	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: Sun, 19 Feb 2006 23:21:13 -0800	[thread overview]
Message-ID: <43F96DE9.7070209@namesys.com> (raw)
In-Reply-To: <20060220070916.GA8101@kevlar.burdell.org>

Thanks kindly Sonny, Chris is this bug known/fixed?

Hans

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  7:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-16 18:36 kernel oops: trying to mount a corrupted xfs partition (2.6.16-rc3) 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 [this message]
2006-02-20 16:41             ` Sonny Rao
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=43F96DE9.7070209@namesys.com \
    --to=reiser@namesys.com \
    --cc=bjdouma@xs4all.nl \
    --cc=davej@redhat.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=mason@suse.com \
    --cc=nathans@sgi.com \
    --cc=reiserfs-list@namesys.com \
    --cc=sonny@burdell.org \
    --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