All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aditya Kulkarni <aditya.r.kulkarni@gmail.com>
To: linux-lvm@redhat.com
Subject: [linux-lvm] LVM minor number allocation policy
Date: Tue, 10 May 2005 12:23:02 +0530	[thread overview]
Message-ID: <e4fec31a05050923534f3bdaea@mail.gmail.com> (raw)

Hi all,

Here are a few questions that I had related to minor numbers of
logical volumes (LVs). First the questions, and then I will explain
the reason why I ask these questions -

[1] Suppose I create two LVs named vol1 and vol2. They have the
following (major, minor) no.s. vol1 = (major=X, minor=0) and vol2 =
(major=X, minor=1). Now I reboot the system. Is it guaranteed that
vol1 and vol2 will retain their minor no.s?

[2] Are there some options while creating LVs that we can use so that
LVs are created with a particular minor number?

[3] Suppose it is not guaranteed that LVs retain their minor numbers
across system reboots. When the system is coming up, what policy it
uses to assign minor numbers to LVs. For example, it could be based on
any one of the following -
    1. sort order of names of LVs.
    2. Timestamp of creation of LVs.
    3. Random

Why I ask these:
The issue of minor number remaining same is relevant to services being
"highly available". In my case, it happens to be the NFS exported file
system. The NFS file handle includes, among other things, the minor
no. of the device on which the exported file system resides. In case
the minor no. of LV is different on the failed-over-to system, we get
the problem of stale file handles.

Hence, I wanted to know how minor numbers are treated by LVM.

-- 
Best Wishes,
Aditya Kulkarni

             reply	other threads:[~2005-05-10  6:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-10  6:53 Aditya Kulkarni [this message]
2005-05-10 12:50 ` [linux-lvm] LVM minor number allocation policy Alasdair G Kergon

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=e4fec31a05050923534f3bdaea@mail.gmail.com \
    --to=aditya.r.kulkarni@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.