From: "J. Bruce Fields" <bfields@fieldses.org>
To: Saurabh Sehgal <saurabh.r.s@gmail.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: Nfs Failover
Date: Wed, 10 Oct 2007 09:40:54 -0400 [thread overview]
Message-ID: <20071010134054.GA31732@fieldses.org> (raw)
In-Reply-To: <2a46ebd60710100638k5665f025vbadb8d7194262f1a@mail.gmail.com>
On Wed, Oct 10, 2007 at 09:38:18AM -0400, Saurabh Sehgal wrote:
> I will be sure to try that and see if I get the same problem ...
>
> I am exporting an ext3 filesystem ...
So you're using a shared block device?
> Does that change anything ?
It's just important to make sure you're exporting the *identical* ext3
filesystem from the two servers--copies made above the filesystem level
(using cp or rsync or whatever) aren't sufficient to ensure that
filehandles stay the same.
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-10-10 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 19:40 Nfs Failover Saurabh Sehgal
2007-10-09 19:51 ` J. Bruce Fields
2007-10-09 20:08 ` Jordi Prats
2007-10-10 13:38 ` Saurabh Sehgal
2007-10-10 13:40 ` J. Bruce Fields [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-11 3:02 nfs failover Eric Ford
2004-01-11 4:55 ` Brian Tinsley
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=20071010134054.GA31732@fieldses.org \
--to=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=saurabh.r.s@gmail.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