linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: md@Linux.IT (Marco d'Itri)
To: linux-hotplug@vger.kernel.org
Subject: vol_id and RAID1 members
Date: Tue, 24 Jan 2006 22:30:36 +0000	[thread overview]
Message-ID: <20060124223036.GA16374@wonderland.linux.it> (raw)

Today one of the disks in a mirrored RAID array failed, and I noticed
that the /dev/disk/by-label/ link had changed from md2 to hda6, the
failed device.
By looking at /dev/.udev/db/ I determined that vol_id returned
ID_FS_LABEL_SAFE=home for both md2 and hda6, because hda6 is not part of
the RAID array anymore and obviously both devices have identical file
system superblocks.

Having the by-label link change after a reboot is a big problem which
could easily cause data loss, but I am not sure about how to fix it.
Should vol_id be modified to look for the RAID superblock and if one is
present ignore the file system superblock?

-- 
ciao,
Marco


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x103432&bid#0486&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

             reply	other threads:[~2006-01-24 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-24 22:30 Marco d'Itri [this message]
2006-01-24 23:55 ` vol_id and RAID1 members Kay Sievers
2006-01-27 13:06 ` Marco d'Itri
2006-01-27 16:02 ` Kay Sievers
2006-01-27 16:35 ` Marco d'Itri
2006-01-27 16:48 ` Kay Sievers
2006-01-27 16:56 ` Marco d'Itri

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=20060124223036.GA16374@wonderland.linux.it \
    --to=md@linux.it \
    --cc=linux-hotplug@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 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).