From: Zoran Cvetkovic <Zoran.Cvetkovic@zmensch.de>
To: xfs@oss.sgi.com
Subject: corrupt dinode but xfs_check and xfs_repair are bit detecting any problem and are fixing nothing.
Date: Fri, 07 Aug 2009 13:39:17 +0200 [thread overview]
Message-ID: <4A7C1265.5020909@zmensch.de> (raw)
Hi Fellows,
I am running a 2.6.26 kernel on debian lenny having a 6 TB data
partition under xfs, 2.6 TB are in use now.
xfs fs is exported via nfs from that box.
after 12 weeks of popper service suddenly nfs performance was a disaster
and the box was stuttering, system load was about 10.
There was no indication for a hardware problem. HW Raid status was *OK*
/var/log/messages lists several thousand lines like:
Aug 6 21:12:03 nfsserver kernel: [7660448.840139] Filesystem "sdb1":
corrupt dinode 4806258, (btree extents). Unmount and run xfs_repair.
(allways the same dinode #)
after stopping nfsd and unmounting the fs
both xfs_check and xfs_repaier did not detect any corruption!
back in service i got the same problem and log lines.
So what is wrong here?
There might be a fs issue and the fs utilitys are not able to detect it ?
I did a metadata dump of that fs and could post it, would this help to
determine what is going wrong here?
Regards,
Zoran Cvetkovic
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2009-08-07 11:38 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=4A7C1265.5020909@zmensch.de \
--to=zoran.cvetkovic@zmensch.de \
--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