All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Affolter <christian.affolter@stepping-stone.ch>
To: xfs@oss.sgi.com
Subject: Corruption of in-memory data detected - on heavy  hard linking
Date: Wed, 23 Jul 2008 19:40:19 +0200	[thread overview]
Message-ID: <48876D03.8010804@stepping-stone.ch> (raw)

Dear XFS users

While using rsnapshot [1] on an XFS filesystem I encountered the 
following error, which I can reproduce using the bash command below:

i=0; while (( $i <20 )); do
     rm -rf link-dir;
     cp -al orig-dir link-dir

     echo "Round $i over"; let i++;
done

The problem mostly happens between the 6th and 10th run.

"orig-dir" contains around 12 GB of data and around 40'000 files (the 
filesystem is 50 GB whereas 27 GB are free, mount options: 
rw,noatime,usrquota).

The problem doesn't occur with a reiserfs filesystem (on the same device).

Kernel-Error:
Filesystem "sdc1": XFS internal error xfs_trans_cancel at line 1163 of 
file fs/xfs/xfs_trans.c.  Caller 0xffffffff803a4fcf
Pid: 22816, comm: cp Not tainted 2.6.24-gentoo-r8 #1

Call Trace:
  [<ffffffff803a4fcf>] xfs_link+0x26f/0x390
  [<ffffffff8039c656>] xfs_trans_cancel+0x126/0x150
  [<ffffffff803a4fcf>] xfs_link+0x26f/0x390
  [<ffffffff8039cf4b>] xfs_trans_unlocked_item+0x3b/0x60
  [<ffffffff803aff8c>] xfs_vn_link+0x3c/0xb0
  [<ffffffff802952b3>] vfs_link+0x123/0x180
  [<ffffffff802984b1>] sys_linkat+0x151/0x180
  [<ffffffff802901b7>] cp_new_stat+0xe7/0x100
  [<ffffffff80290276>] sys_newlstat+0x36/0x50
  [<ffffffff8020bbce>] system_call+0x7e/0x83

xfs_force_shutdown(sdc1,0x8) called from line 1164 of file 
fs/xfs/xfs_trans.c.  Return address = 0xffffffff8039c66f
Filesystem "sdc1": Corruption of in-memory data detected.  Shutting down 
filesystem: sdc1
Please umount the filesystem, and rectify the problem(s)
xfs_force_shutdown(sdc1,0x1) called from line 420 of file 
fs/xfs/xfs_rw.c.  Return address = 0xffffffff803a7fe9
xfs_force_shutdown(sdc1,0x1) called from line 420 of file 
fs/xfs/xfs_rw.c.  Return address = 0xffffffff803a7fe9

After remounting, everything seems to be fine, even xfs_repair (xfsprogs 
2.8.11) doesn't find any problems on the filesystem.

The above error happens on a 2.6.24-gentoo-r8 SMP 64bit kernel with 4 GB 
of memory (~3G free), Intel 5000V chipset (ASUS DSBV-D), on top of a 
Areca ARC-1160 (V1.42) RAID controller.

According to memcheck the memory seems to be OK, anyway I replaced the 
DIMMs with no success.

Google leads to a lot of results, for the above error message, however I 
only found one forum entry [2] which seems to look similar.


Any help would be highly appreciated

Many thanks!
Chris


[1]http://www.rsnapshot.org/
[2]http://ubuntuforums.org/showthread.php?t=741425

-- 
stepping stone GmbH
Pappelweg 41
CH-3013 Bern

Telefon: +41 31 332 53 63
www.stepping-stone.ch
christian.affolter@stepping-stone.ch

             reply	other threads:[~2008-07-23 17:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-23 17:40 Christian Affolter [this message]
2008-07-25  5:20 ` Corruption of in-memory data detected - on heavy hard linking Christoph Hellwig
2008-08-04 16:47   ` Christian Affolter
2008-08-05  0:19     ` Dave Chinner
     [not found]       ` <48A02FF6.70703@stepping-stone.ch>
2008-08-11 23:52         ` Dave Chinner

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=48876D03.8010804@stepping-stone.ch \
    --to=christian.affolter@stepping-stone.ch \
    --cc=xfs@oss.sgi.com \
    /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.