All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: LKML <linux-kernel@vger.kernel.org>
Subject: disk Partition label changes and reflecting them in /dev/disks-by-label/
Date: Sun, 19 Jul 2009 08:01:22 -0700	[thread overview]
Message-ID: <4A633542.8030502@tlinx.org> (raw)

 

If I have a disk with no mounted partitions and I change the partition 
order,
the OS will re-read the new partition and life goes on.

However, if I create or change a new disk label, it seems label programs
(and users) should have an option to reread the labels after the 
modification.

Ideally any prog that changes a Label or UUID would trigger an update
of what's in /dev/disks to reflect the new 'reality'.

Currently, I go through through a seemingly bizarre ritual of invoking
unmounting all other partitions on the same disk, then becoming root,
running fdisk on the disk, then just exiting with "w".  This triggers
a reread of not only the partition table, but also the new labels. 

However, I find this far less than ideal.  Is there a better way, or could
there be a better way to update new Labels and UUID's that are actually
on a disk -- perhaps even as an ordinary user command (since it would be
a read-only operation on the disk that simply updates /dev/disk to reflect
what's really there -- Especially being able to change only the label (or
UUID), only on one partition w/o having to actually unmount other file 
systems
on the disk....?

Already implemented?  Or doable?  Or bad idea?

Thanks,
-linda


             reply	other threads:[~2009-07-19 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-19 15:01 Linda Walsh [this message]
2009-07-19 16:22 ` disk Partition label changes and reflecting them in /dev/disks-by-label/ Alan Jenkins
2009-07-19 18:19   ` Mark Lord

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=4A633542.8030502@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=linux-kernel@vger.kernel.org \
    /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.