All of lore.kernel.org
 help / color / mirror / Atom feed
From: Flemming Frandsen <ff@partyticket.net>
To: linux-raid@vger.kernel.org
Subject: Non-equal sized partitions vs RAID 1
Date: Mon, 01 Jul 2002 13:29:46 +0200	[thread overview]
Message-ID: <3D203D2A.5030307@partyticket.net> (raw)

I have two disks in my box, both are MAXTOR 6L080L4 (80GB IDE) and 
physically the same disks, both have 3 partitions, one for /boot one for 
swap and one huge one for the rest for the mirrored data.

The mirror works as expected, but somewhere something went slightly 
wrong because one disks geometry is:
physical     155114/16/63
logical      155114/16/63

The other disk is:
physical     155114/16/63
logical      9732/255/63

Now, this has the annoying sideeffect of making it impossible for me to 
partition them exactly the same way, so I ended up creating the mirror 
on disk 1 (which has a slightly smaller partition for mirroring than 
disk 2) and then adding disk 2 later.

This will get me in trouble (I tested it) when disk 1 fails and I need 
to replace it, because then I have to make that partition slightly 
larger than the disk 2 partition so it can be added to the mirror.

Now for the questions:
* Is there a way to change the logical geometry of disk 2, so I can 
partition correctly (well if there is then this post is OT)?

* Is there a way to force the array to keep being the same size, even 
after the smaller partition has failed?

* Why does the BIOS think that it's cool to translate similar disks 
differently, are BIOS writers crackheads or was I just unlucky?


             reply	other threads:[~2002-07-01 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-01 11:29 Flemming Frandsen [this message]
2002-07-01 11:54 ` Non-equal sized partitions vs RAID 1 Danilo Godec

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=3D203D2A.5030307@partyticket.net \
    --to=ff@partyticket.net \
    --cc=linux-raid@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.