From: patl@curl.com (Patrick J. LoPresti)
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] Help: 2.2.18 NFS is corrupting our files
Date: 22 Jan 2001 14:41:16 -0500 [thread overview]
Message-ID: <s5g66j7tlwj.fsf@egghead.curl.com> (raw)
In-Reply-To: <s5gvgr71xao.fsf@egghead.curl.com> <shsbsszqus5.fsf@charged.uio.no>
In-Reply-To: Trond Myklebust's message of "22 Jan 2001 19:57:46 +0100"
Trond Myklebust <trond.myklebust@fys.uio.no> writes:
> What filesystem are you exporting?
Just ext2; all of our file systems are ext2.
The disks here are a mixture of IDE, SCSI (aic7xxx and sym53c8xx), and
Mylex DAC960 RAID. In this case, the machine running 2.2.18 has
aic7xxx SCSI. I suspect I could reproduce the problem on other
configurations; let me know if that would be useful.
- Pat
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-22 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5gvgr71xao.fsf@egghead.curl.com>
2001-01-22 18:57 ` [NFS] Help: 2.2.18 NFS is corrupting our files Trond Myklebust
2001-01-22 19:41 ` Patrick J. LoPresti [this message]
2001-01-23 9:07 ` Neil Brown
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=s5g66j7tlwj.fsf@egghead.curl.com \
--to=patl@curl.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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