mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Thomas Seifert" <thomas-lists@myphorum.com>
To: "Mike Fedyk" <mfedyk@matchmail.com>, "Jirka Kosina" <jikos@jikos.cz>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: XFS over 7.7TB LVM partition through NFS
Date: Wed, 07 Jan 2004 18:35:05 +0000	[thread overview]
Message-ID: <20040107.8Z4.43021900@db.myphorum.de> (raw)

fsck? shouldn't it read
xfs_repair
???


thomas

Mike Fedyk (mfedyk@matchmail.com) schrieb:
>
> On Wed, Jan 07, 2004 at 07:09:00PM +0100, Jirka Kosina wrote:
> > On Wed, 7 Jan 2004, Jirka Kosina wrote:
> >
> > > 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):
> >
> > I am sorry, I have mis-pasted the log, it was not complete - there are two
> > extra lines before the Call Trace ... these two:
> >
> > Jan  8 01:38:35 storage2 kernel: 0x0: 94 38 73 54 cc 8c c9 be 0c 3e 6b 30
> > 4c 9f 54 c5
> > Jan  8 01:38:35 storage2 kernel: Filesystem "dm-0": XFS internal error
> > xfs_alloc_read_agf at line 2208 of file fs/xfs/xfs_alloc.c.  Caller 0xc01fab06
>
> Try a fsck on your xfs partitions.
>
>
>


             reply	other threads:[~2004-01-07 18:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 18:35 Thomas Seifert [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2004-01-07 23:42   ` Jirka Kosina

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=20040107.8Z4.43021900@db.myphorum.de \
    --to=thomas-lists@myphorum.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=mfedyk@matchmail.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

Powered by JetHome