From: Michael Morrison <mliam@adelphia.net>
To: xfs@oss.sgi.com
Subject: XFS internal error when making hard link on full fs.
Date: Thu, 19 Jul 2007 20:00:33 -0700 [thread overview]
Message-ID: <46A02551.8040409@adelphia.net> (raw)
Got the following when I tried to make a hard link on a full filesystem:
I'm running Linux kernel 2.6.18. I'm unable to try a newer kernel at
the present time.
The application was properly given ENOSPC in errno when the link call
failed.
The filesystem is built on a linux software raid0 with 8 drives using
the following command lines:
/sbin/mdadm --create /dev/md0 --level=0 \
--chunk=64 \
--raid-devices=8 \
/dev/sda /dev/sde \
/dev/sdb /dev/sdf \
/dev/sdc /dev/sdg \
/dev/sdd /dev/sdh
/sbin/mkfs -t xfs -f -d unwritten=0 -l version=2,sunit=128,internal
/dev/md0
/bin/mount -t xfs /dev/md0 /mnt/dmag -o noatime,nodiratime,logbufs=4
Filesystem "md0": XFS internal error xfs_trans_cancel at line 1138 of
file fs/xfs/xfs_trans.c. Caller 0xc02d53a5
[<c02cb987>] xfs_trans_cancel+0x108/0x14f
[<c02d53a5>] xfs_link+0x40f/0x585
[<c02d53a5>] xfs_link+0x40f/0x585
[<c04937ab>] _spin_unlock+0xd/0x21
[<c02e19d5>] xfs_vn_link+0x64/0xd3
[<c0181b66>] mntput_no_expire+0x1c/0x75
[<c017de95>] __d_lookup+0x8f/0x13b
[<c016e2b2>] vfs_stat+0x1f/0x23
[<c0172788>] cached_lookup+0x23/0x85
[<c01725de>] permission+0x85/0xaa
[<c0175e24>] vfs_link+0xc7/0x183
[<c0176008>] sys_linkat+0x128/0x14a
[<c0176059>] sys_link+0x2f/0x33
[<c0102ecd>] sysenter_past_esp+0x56/0x79
xfs_force_shutdown(md0,0x8) called from line 1139 of file
fs/xfs/xfs_trans.c. Return address = 0xc02cb9ad
Filesystem "md0": Corruption of in-memory data detected. Shutting down
filesystem: md0
Please umount the filesystem, and rectify the problem(s)
Unmounting the fs and running xfs_check did not produce any output. The
filesystem seems happy after mounting it again.
next reply other threads:[~2007-07-20 3:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 3:00 Michael Morrison [this message]
2007-07-22 22:37 ` XFS internal error when making hard link on full fs David 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=46A02551.8040409@adelphia.net \
--to=mliam@adelphia.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox