From: "Sander Steffann" <s.steffann@computel.nl>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM2, NFS and random device (major:minor) numbers
Date: Fri, 14 Apr 2006 22:54:14 +0200 [thread overview]
Message-ID: <000801c66005$979d28c0$64c8a8c0@balefirehome> (raw)
In-Reply-To: Pine.LNX.4.62.0604131143270.21727@gate.nmr.mgh.harvard.edu
Hi Paul,
> NFS depends on what the server says the underlying device id is of the
> exported volume and if that changes, then NFS mounts are going to change
> out from under themselves. And everytime I add a volume and reboot the
> device ids change.
Unfortunate, but true. One of the side-effects of having dynamic volumes.
Also note that you would get similar trouble if, for example, you added a
SCSI device with a lower SCSI-id than an existing SCSI device. /dev/sdb1
would become /dev/sdc1, etc.
> I finally come upon this old post to this list:
> http://www.redhat.com/archives/linux-lvm/2005-May/msg00029.html
The part that can solve everything for you is:
>> These days, that's configurable.
>> See 'man exports' fsid=num.
With an explicit fsid=n for every export, you tell the NFS server to ignore
the device-id, and use the specified fsid instead. That way you get
consistent NFS exports, without being dependent on the underlying
device-ids.
I have had the same trouble as you have, and this solution works great.
Sander.
next prev parent reply other threads:[~2006-04-14 20:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 14:08 [linux-lvm] LVM2, NFS and random device (major:minor) numbers Paul Raines
2006-04-14 14:50 ` Alasdair G Kergon
2006-04-14 21:22 ` Paul Raines
2006-04-14 21:32 ` Alasdair G Kergon
2006-04-14 20:54 ` Sander Steffann [this message]
2006-04-14 21:36 ` Paul Raines
2006-04-19 15:44 ` [linux-lvm] " Paul Raines
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='000801c66005$979d28c0$64c8a8c0@balefirehome' \
--to=s.steffann@computel.nl \
--cc=linux-lvm@redhat.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;
as well as URLs for NNTP newsgroup(s).