From: David Chinner <dgc@sgi.com>
To: sudheer <ssudheer@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: xfs problem ?
Date: Tue, 18 Dec 2007 23:39:50 +1100 [thread overview]
Message-ID: <20071218123950.GM4396912@sgi.com> (raw)
In-Reply-To: <a727368a0712171751i3eb2633epaf31a6a48129c777@mail.gmail.com>
On Tue, Dec 18, 2007 at 07:21:21AM +0530, sudheer wrote:
> Sir ,
>
> When i run tail -f /var/log/messages
> --------------------------------------------------------------
> Dec 17 20:50:42 u15200848 kernel: [<c014bb20>] pdflush+0x0/0x50
> Dec 17 20:50:42 u15200848 kernel: [<c014ba2c>] __pdflush+0xbc/0x1b0
> Dec 17 20:50:42 u15200848 kernel: [<c014bb5d>] pdflush+0x3d/0x50
> Dec 17 20:50:42 u15200848 kernel: [<c014afb0>] wb_kupdate+0x0/0x140
> Dec 17 20:50:42 u15200848 kernel: [<c0134fba>] kthread+0xba/0xc0
> Dec 17 20:50:42 u15200848 kernel: [<c0134f00>] kthread+0x0/0xc0
> Dec 17 20:50:42 u15200848 kernel: [<c0101255>]
> kernel_thread_helper+0x5/0x10
> Dec 17 20:50:42 u15200848 kernel: 0x0: 58 41 47 46 00 00 00 01 00 00 00 0a
> 00 18 c5 15
> Dec 17 20:50:42 u15200848 kernel: Filesystem "hda7": XFS internal error
> xfs_alloc_read_agf at line 2173 of file fs/xfs/xfs_alloc.c. Caller
That indicates a corrupted AGF. The magic number looks good:
#define XFS_AGF_MAGIC 0x58414746
so that leaves:
agf_ok =
be32_to_cpu(agf->agf_magicnum) == XFS_AGF_MAGIC &&
XFS_AGF_GOOD_VERSION(be32_to_cpu(agf->agf_versionnum)) &&
be32_to_cpu(agf->agf_freeblks) <= be32_to_cpu(agf->agf_length) &&
be32_to_cpu(agf->agf_flfirst) < XFS_AGFL_SIZE(mp) &&
be32_to_cpu(agf->agf_fllast) < XFS_AGFL_SIZE(mp) &&
be32_to_cpu(agf->agf_flcount) <= XFS_AGFL_SIZE(mp);
Fromteh hex dump above I can see the version is also good, but nothing else.
You should run xfs_check on teh filesystem and report the output to us, then
run xfs_repair to correct the problem (also send us the output).
The output of the two programs might tell use what was wrong....
> Is this a problem with the xfs file system ? in the hda7 partition ?
Could be either - is you disk reporting errors? What does smart tell you?
> .How
> can i correct this on live server ?
unmount the filesystem, check it, repair it, mount it back up.
You can't fix it online.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
prev parent reply other threads:[~2007-12-18 12:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-18 1:51 xfs problem ? sudheer
2007-12-18 12:39 ` David Chinner [this message]
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=20071218123950.GM4396912@sgi.com \
--to=dgc@sgi.com \
--cc=ssudheer@gmail.com \
--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