From: Eric Sandeen <sandeen@sgi.com>
To: Jirka Kosina <jikos@jikos.cz>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-xfs@oss.sgi.com
Subject: Re: XFS over 7.7TB LVM partition through NFS
Date: 07 Jan 2004 12:57:48 -0600 [thread overview]
Message-ID: <1073501867.23356.5.camel@stout.americas.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401071824120.31032@twin.jikos.cz>
Just to get this out of the way, I assume CONFIG_LBD is turned on?
I think so, otherwise it should not mount.
Also, is below an oops, or an xfs corruption message, or...? What came
before the call trace.
fsck won't do anything, fsck.xfs is a no-op.
You could run xfs_repair over the fs to see what it finds.
Also please include xfs_info output for the filesystem, and whether you
expect that any clients are writing files > 4G...
And, that stack looks awfully long if it's real, turning on the stack
overflow check in the kernel might be interesting.
-Eric
On Wed, 2004-01-07 at 11:36, Jirka Kosina wrote:
> Hi,
>
> I am experiencing problems with LVM2 XFS partition in 2.6.0 being accessed
> over NFS. After exporting the filesystem clients start writing files to
> this partition over NFS, and after a short while we get this call trace,
> repeating indefinitely on the screen and the machine stops responding
> (keyboard, network):
--
Eric Sandeen [C]XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@sgi.com SGI, Inc. 651-683-3102
next prev parent reply other threads:[~2004-01-07 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 17:36 Jirka Kosina
2004-01-07 18:00 ` Mike Fedyk
2004-01-07 18:09 ` Jirka Kosina
2004-01-07 18:20 ` Mike Fedyk
2004-01-07 18:35 ` Jirka Kosina
2004-01-07 18:57 ` Eric Sandeen [this message]
2004-01-07 23:42 ` Jirka Kosina
2004-01-07 18:35 Thomas Seifert
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=1073501867.23356.5.camel@stout.americas.sgi.com \
--to=sandeen@sgi.com \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-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
all inboxes | Powered by JetHome®