lkml.org 
[lkml]   [2009]   [Feb]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: XFS kernel BUG at fs/buffer.c:470! with 2.6.28.4
    From
    Date
    On Mon, 2009-02-09 at 09:16 +1100, Dave Chinner wrote:
    > On Sat, Feb 07, 2009 at 02:06:13PM +0100, Alessandro Bono wrote:
    > > Hi all
    > >
    > > This time I hit kernel bug without any particular operation, normal
    > > browsing, mail, news, etc
    > > tell me if you need info asap because I want to reformat this machine
    > > and switch back to ext3.
    > >
    > > xfs seems really unstable in this particular
    > > machine and after this crash I lose again configuration file of opened
    > > program at crash time
    >
    > That's not XFS's fault - that's a broken application that does not
    > safely overwrite files and hence you lose data on crash.

    In the past I lose configuration files from kde, gconf based programs (gnome), pan, firefox, etc
    maybe xfs expose more this problem

    >
    > > Feb 7 12:43:12 champagne kernel: [ 5828.167041] ------------[ cut
    > > here ]------------
    > > Feb 7 12:43:12 champagne kernel: [ 5828.167048] kernel BUG at
    > > fs/buffer.c:470!
    >
    > I can't remember seeing that problem before.
    >
    > > Call Trace:
    > > [<ffffffff8022806f>] ? need_resched+0x1e/0x28
    > > [<ffffffff8030be35>] ? __up_write+0x12/0x45
    > > [<ffffffffa01c2269>] ? xfs_destroy_ioend+0x23/0x71 [xfs]
    > > [<ffffffffa01c23db>] ? xfs_end_bio_delalloc+0x0/0x19 [xfs]
    > > [<ffffffffa01c23db>] ? xfs_end_bio_delalloc+0x0/0x19 [xfs]
    > > [<ffffffff80242d5e>] ? run_workqueue+0x79/0xfe
    > > [<ffffffff80242ed3>] ? worker_thread+0xf0/0x102
    > > [<ffffffff802461cd>] ? autoremove_wake_function+0x0/0x2e
    > > [<ffffffff80242de3>] ? worker_thread+0x0/0x102
    > > [<ffffffff80245ea2>] ? kthread+0x47/0x73
    > > [<ffffffff80231bfa>] ? schedule_tail+0x27/0x60
    > > [<ffffffff8020c3f9>] ? child_rip+0xa/0x11
    > > [<ffffffff80245e5b>] ? kthread+0x0/0x73
    > > [<ffffffff8020c3ef>] ? child_rip+0x0/0x11
    >
    > Standard delayed allocation IO completion trace. No idea what
    > could have caused it. Perhaps a memory error?

    I'm starting to think the same thing
    If needed I can replace memory dimm, this is my principal notebook and I
    need it to work

    >
    > Can you send the output of xfs_info on that filesystem, and
    > perhaps run an xfs_repair -n on it to see if there are any
    > undetected errors on disk?

    root@champagne:/home/sandro# xfs_info /
    meta-data=/dev/mapper/vol00-root isize=256 agcount=17, agsize=1600000
    blks
    = sectsz=512 attr=1
    data = bsize=4096 blocks=26781696,
    imaxpct=25
    = sunit=0 swidth=0 blks
    naming =version 2 bsize=4096
    log =internal bsize=4096 blocks=12500, version=1
    = sectsz=512 sunit=0 blks, lazy-count=0
    realtime =none extsz=4096 blocks=0, rtextents=0


    root fs on lvm on dm_crypt
    to run xfs_repair I have to boot from a live distribution that support
    this stack, I need some time

    >
    > Also, I note that you are using ext4 on some disks. Does this
    > problem show up if you don't use ext4 at all? (We have had problems
    > in the past with one filesystem not leaving bufferheads in the
    > correct state and the system crashing when a different type of
    > filesystem got them reallocated).

    First time of this bug, not sure if it's ext4 related
    Ext4 disk is my personal mirror of data taken from my server, I can
    reformat ext4 disk to xfs
    Ironically I started test ext4 to replace xfs on this machine :-(

    thanks

    >
    > Cheers,
    >
    > Dave.
    --
    ---
    Cordiali Saluti
    Alessandro Bono



    \
     
     \ /
      Last update: 2009-02-09 00:27    [W:0.038 / U:0.048 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site