All of lore.kernel.org
 help / color / mirror / Atom feed
From: Claas Langbehn <claas@rootdir.de>
To: linux-kernel@vger.kernel.org
Subject: XFS forced shutdown with kernel 2.6.0
Date: Fri, 2 Jan 2004 10:50:51 +0100	[thread overview]
Message-ID: <20040102095051.GA19872@rootdir.de> (raw)

Hello!


Last night one of my machines running xfs shut down my /homes partition.

That machine was running Azureus (a bittorrent client) with probably
high memory usage.

But even if the memory usage of one program is going near to 100% it
should not force the filesystem to shutdown. Instead it should crash
the application.

I could also think of bad memory, but we did test the SDRAM modules
only a week ago, and they passed memtest86.

After rebooting everything was working fine, again.

So, is this a bug of xfs?


regards,
Claas



kernel: Filesystem "hdb3": XFS internal error xfs_btree_check_lblock at line 222 of file fs/xfs/xfs_btree.c.  Caller 0xc01d770c
kernel: Call Trace:
kernel:  [<c01da8be>] xfs_btree_check_lblock+0x5e/0x190
kernel:  [<c01d770c>] xfs_bmbt_lookup+0x18c/0x550
kernel:  [<c01d770c>] xfs_bmbt_lookup+0x18c/0x550
kernel:  [<c01cabe9>] xfs_bmap_add_extent_delay_real+0x11b9/0x16a0
kernel:  [<c01cdc64>] xfs_bmap_alloc+0xb34/0x1870
kernel:  [<d0a9998d>] __nvsym00795+0x31/0x50 [nvidia]
kernel:  [<c01d957f>] xfs_bmbt_get_state+0x2f/0x40
kernel:  [<c01c989f>] xfs_bmap_add_extent+0x38f/0x520
kernel:  [<c01d2283>] xfs_bmapi+0x783/0x1600
kernel:  [<c01d957f>] xfs_bmbt_get_state+0x2f/0x40
kernel:  [<c01d033c>] xfs_bmap_do_search_extents+0xbc/0x3f0
kernel:  [<c02013dd>] xfs_log_reserve+0xbd/0xd0
kernel:  [<c02269f8>] xfs_iomap_write_allocate+0x2a8/0x4d0
kernel:  [<c01d1df3>] xfs_bmapi+0x2f3/0x1600
kernel:  [<c0225cec>] xfs_iomap+0x40c/0x550
kernel:  [<c0220ae2>] map_blocks+0x72/0x130
kernel:  [<c0221ba7>] page_state_convert+0x4c7/0x620
kernel:  [<c02223bc>] linvfs_writepage+0x5c/0x110
kernel:  [<c0174953>] mpage_writepages+0x203/0x2f0
kernel:  [<c0222360>] linvfs_writepage+0x0/0x110
kernel:  [<c013d846>] do_writepages+0x36/0x40
kernel:  [<c0137e7e>] __filemap_fdatawrite+0xbe/0xd0
kernel:  [<c0137ea7>] filemap_fdatawrite+0x17/0x20
kernel:  [<c01736f0>] generic_osync_inode+0x120/0x130
kernel:  [<c013a27f>] generic_file_aio_write_nolock+0x5af/0xb90
kernel:  [<c011cb10>] default_wake_function+0x0/0x20
kernel:  [<c01fdde0>] xfs_ichgtime+0x120/0x122
kernel:  [<c0211729>] xfs_trans_unlocked_item+0x39/0x60
kernel:  [<c0228e1b>] xfs_write+0x29b/0x860
kernel:  [<d0a99a8d>] __nvsym00727+0x31/0x38 [nvidia]
kernel:  [<c0109d16>] apic_timer_interrupt+0x1a/0x20
kernel:  [<c02228c1>] linvfs_write+0xb1/0x120
kernel:  [<c01536bb>] do_sync_write+0x8b/0xc0
kernel:  [<c0147ae9>] find_extend_vma+0x29/0x90
kernel:  [<c011cb10>] default_wake_function+0x0/0x20
kernel:  [<c0127fc6>] update_process_times+0x46/0x60
kernel:  [<c0127e2b>] update_wall_time+0xb/0x40
kernel:  [<c012829f>] do_timer+0xdf/0xf0
kernel:  [<c0153630>] do_sync_write+0x0/0xc0
kernel:  [<c01537a8>] vfs_write+0xb8/0x130
kernel:  [<c01538d2>] sys_write+0x42/0x70
kernel:  [<c0109387>] syscall_call+0x7/0xb
kernel: 
kernel: xfs_force_shutdown(hdb3,0x8) called from line 1070 of file fs/xfs/xfs_trans.c.  Return address = 0xc022aa0c
kernel: Filesystem "hdb3": Corruption of in-memory data detected.  Shutting down filesystem: hdb3
kernel: Please umount the filesystem, and rectify the problem(s)

- about 30mins later: -

kernel: Out of Memory: Killed process 2825 (java).



             reply	other threads:[~2004-01-02  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-02  9:50 Claas Langbehn [this message]
2004-01-02 18:29 ` XFS forced shutdown with kernel 2.6.0 Christoph Hellwig
2004-01-02 20:27   ` Valdis.Kletnieks
2004-01-02 20:35     ` Christoph Hellwig
     [not found]   ` <04a601c415a5$0513b020$d100000a@sbs2003.local>
2004-03-29 16:05     ` Christoph Hellwig

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=20040102095051.GA19872@rootdir.de \
    --to=claas@rootdir.de \
    --cc=linux-kernel@vger.kernel.org \
    /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 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.