From: Christoph Hellwig <hch@infradead.org>
To: Mario Becroft <mb@gem.win.co.nz>
Cc: xfs@oss.sgi.com
Subject: Re: XFS internal error when NFS client accesses nonexistent inode
Date: Thu, 1 Jan 2009 14:00:39 -0500 [thread overview]
Message-ID: <20090101190039.GA29959@infradead.org> (raw)
In-Reply-To: <20090101171409.GA18020@infradead.org>
Btw, you update /proc/sys/fs/xfs/error_level manually? The corruption
test only triggers from a avalue of 5, but 3 is the default.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-01 19:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-31 14:09 XFS internal error when NFS client accesses nonexistent inode Mario Becroft
2009-01-01 17:14 ` Christoph Hellwig
2009-01-01 17:37 ` Christoph Hellwig
2009-01-01 19:00 ` Christoph Hellwig [this message]
2009-01-01 23:15 ` Mario Becroft
2009-01-01 23:20 ` Christoph Hellwig
2009-01-01 17:17 ` Feature requests, was " Christoph Hellwig
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=20090101190039.GA29959@infradead.org \
--to=hch@infradead.org \
--cc=mb@gem.win.co.nz \
--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