public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: pg_xf2@xf2.for.sabi.co.UK (Peter Grandi)
To: Linux XFS <xfs@oss.sgi.com>
Subject: RE: Power loss causes bad magic number??
Date: Fri, 18 Jul 2008 19:19:26 +0100	[thread overview]
Message-ID: <18560.57006.898336.560030@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <F46A887185FC6044A7FAC577E31118AE021E0625@rsbne01.RSBNE.LOCAL>

[ ... ]

> [ ... ] ls of /dev/sd* and the devices have been remapped (any
> idea what would have caused that?), sdc is no longer sdc, it
> is now sda, the boot devices are now detected as sdb and sdc
> (2 mirrored physical disks, used to be sda and sdb).

A BIOS or OS upgrade or just about anything might change the
names of any device because there isn't any well defined
enumeration order for devices.

Therefore the only safe option is the same as used by XFS or MD:
to give a unique name/token, but to all storage volumes.

The most useful scheme would be to give unique names to container
volumes like hard drives and then position based letters/numbers
for partitions (because for partitions the ordering is well
defined), but no current GNU/Linux distro supports that.

Probably you should then investigate the 'LABEL=' and 'UUID='
options of '/etc/fstab'.

> How was the machine able to boot? [ ... ]

Depends a bit on which booter you have installed; for example
LILO nowadays uses MS-DOS volume IDs to identify hard drives.
GRUB does not, and therefore I have stopped using it, as the
frequent drive reordering that I suffer has made it almost
unusable.

Also, the BIOS (used for booting) and Linux can and will number
drives in a different order, so the BIOS boot drive may well be
not '/dev/sda' or '/dev/hda'.

  parent reply	other threads:[~2008-07-20 12:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-16  2:18 Power loss causes bad magic number?? Stephen Porter
2008-07-16  2:40 ` Eric Sandeen
2008-07-16  7:01   ` Stephen Porter
2008-07-16  7:35     ` Dave Chinner
2008-07-16  8:17       ` Stephen Porter
2008-07-16 16:00         ` Chris Wedgwood
2008-07-17 13:36         ` Russell Cattelan
2008-07-17 21:52           ` Stephen Porter
2008-07-18 11:17             ` Andi Kleen
2008-07-18 18:19         ` Peter Grandi [this message]
2009-02-07 20:46 ` kevin.dual
2009-02-07 21:10   ` Eric Sandeen
2009-02-07 21:54     ` Eric Sandeen
2009-02-08  6:10     ` Kevin Dual

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=18560.57006.898336.560030@tree.ty.sabi.co.uk \
    --to=pg_xf2@xf2.for.sabi.co.uk \
    --cc=xfs@oss.sgi.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