Mike Accetta wrote:
I gathered the impression somewhere, perhaps incorrectly, that the active
flag was a function of the boot block, not the BIOS. We use Grub in the
MBR and don't even have an active flag set in the partition table. The system
still boots.
The active flag is indeed an MBR
On Mon, Mar 05, 2007 at 06:32:32PM -0500, Mike Accetta wrote:
Yes, we actually have a separate (smallish) boot partition at the front of
the array. This does reduce the at-risk window substantially. I'll have to
ponder whether it reduces it close enough to negligible to then ignore, but
Gabor Gombas wrote:
On Fri, Mar 02, 2007 at 09:04:40AM -0500, Mike Accetta wrote:
Thoughts or other suggestions anyone?
This is a case where a very small /boot partition is still a very good
idea... 50-100MB is a good choice (some initramfs generators require
quite a bit of space under /boot
Bill Davidsen wrote:
Gabor Gombas wrote:
On Fri, Mar 02, 2007 at 09:04:40AM -0500, Mike Accetta wrote:
Thoughts or other suggestions anyone?
This is a case where a very small /boot partition is still a very good
idea... 50-100MB is a good choice (some initramfs generators require
H. Peter Anvin wrote:
Mike Accetta wrote:
I've been considering trying something like having the re-sync algorithm
on a whole disk array defer the copy for sector 0 to the very end of the
re-sync operation. Assuming the BIOS makes at least a minimal
consistency
check on sector 0 before
Mike Accetta wrote:
I wonder if having the MBR typically outside of the array and the relative
newness of partitioned arrays are related? When I was considering how to
architect the RAID1 layout it seemed like a partitioned array on the
entire disk worked most naturally.
It's one way to do
Mike Accetta wrote:
I've been considering trying something like having the re-sync algorithm
on a whole disk array defer the copy for sector 0 to the very end of the
re-sync operation. Assuming the BIOS makes at least a minimal consistency
check on sector 0 before electing to boot from the
On Fri, 2 Mar 2007, Mike Accetta wrote:
We are using a RAID1 setup with two SATA disks on x86, using the whole
disks as the array components. I'm pondering the following scenario.
We will boot from whichever drive the BIOS has first in its boot list
(the other drive will be second). In the
On Fri, Mar 02, 2007 at 09:04:40AM -0500, Mike Accetta wrote:
Thoughts or other suggestions anyone?
This is a case where a very small /boot partition is still a very good
idea... 50-100MB is a good choice (some initramfs generators require
quite a bit of space under /boot while generating the
On Fri, Mar 02, 2007 at 10:40:32AM -0500, Justin Piszcz wrote:
AFAIK mdadm/kernel raid can handle this, I had a number of occaisons when
my UPS shut my machine down when I was rebuilding a RAID5 array, when the
box came back up, the rebuild picked up where it left off.
_If_ the resync got
Gabor Gombas wrote:
On Fri, Mar 02, 2007 at 09:04:40AM -0500, Mike Accetta wrote:
Thoughts or other suggestions anyone?
This is a case where a very small /boot partition is still a very good
idea... 50-100MB is a good choice (some initramfs generators require
quite a bit of space
11 matches
Mail list logo