From: Federico Sevilla III <jijo@free.net.ph>
To: XFS Mailing List <xfs@oss.sgi.com>
Subject: Filesystem Shutdown due to Error 22
Date: Sun, 30 Jul 2006 11:38:02 +0800 [thread overview]
Message-ID: <20060730033802.GA3647@free.net.ph> (raw)
Hi,
I am running Linux 2.6.17.7 on a Debian GNU/Linux Sarge machine
(xfsprogs 2.6.20 and xfsdump 2.2.27). I was hit recently by the dir2
corruption problem, but already fixed this using the procedure in the
FAQ after upgrading the kernel.
I have a weekly scheduled task that runs xfs_fsr and this morning found
that my server's filesystem (the same one previously hit by the dir2
issue) had been shut down. I don't have console access to this server
but managed to get the following off the logs which are on a separate
filesystem:
kernel: xfs_inotobp: xfs_imap() returned an error 22 on md1. Returning error.
kernel: xfs_iunlink_remove: xfs_inotobp() returned an error 22 on md1. Returning error.
kernel: xfs_inactive:^Ixfs_ifree() returned an error = 22 on md1
kernel: xfs_force_shutdown(md1,0x1) called from line 1763 of file fs/xfs/xfs_vnodeops.c. Return address = 0xc01fa80c
I ran xfs_repair, and found 20 disconnected inodes of which 16 are
filled with nulls. No other problems were found with the filesystem.
I have an identical server (hardware, kernel and core utilities, albeit
different applications) which went through the same upgrade path and
dir2 corruption, but went through today's xfs_fsr without any problems.
Any clues as to what's causing this?
Cheers!
--> Jijo
--
Federico Vicente C. Sevilla III
Information Technology Consultant
Q Software Research Corporation
Website: http://jijo.free.net.ph
reply other threads:[~2006-07-30 3:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060730033802.GA3647@free.net.ph \
--to=jijo@free.net.ph \
--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