Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Matt Heaton" <admin@0catch.com>
Cc: <nfs@lists.sourceforge.net>
Subject: Re: Kernel bug problem.
Date: 07 Oct 2003 01:46:33 -0400	[thread overview]
Message-ID: <shsbrsty4zq.fsf@charged.uio.no> (raw)
In-Reply-To: <04c801c38c91$d020c160$6401a8c0@Matt>

>>>>> " " =3D=3D Matt Heaton <admin@0catch.com> writes:

     > Oct=A0 4 06:29:18 catchusers2 kernel: kernel BUG at
     > ll_rw_blk.c:1192!

     > I am wondering=A0if this is NFS related?=A0

No. NFS is not a block device. That looks more like it might be
another XFS bug...

Cheers
  Trond


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

      reply	other threads:[~2003-10-07  5:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-07  5:13 Kernel bug problem Matt Heaton
2003-10-07  5:46 ` Trond Myklebust [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=shsbrsty4zq.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=admin@0catch.com \
    --cc=nfs@lists.sourceforge.net \
    /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