mullaly wrote:
[]
All works well until a system reboot. md2 appears to be brought up before
md0 and md1 which causes the raid to start without two of its drives.
Is there anyway to fix this?
How about listing the arrays in proper order in mdadm.conf ?
/mjt
-
To unsubscribe from this list:
Hello Neil,
Thanks for the confirmations!
It's all very clear now. Case closed.
Best,
Seb.
On Sat, 21 Jul 2007, Neil Brown wrote:
| On Saturday July 21, [EMAIL PROTECTED] wrote:
|
| Hi Neil,
|
|
| | Could you tell me if such a mechanism exists in mdadm?
| | Or should I accept the
Quick question-- under Kernel 2.4 without 2TB support enabled, the only
other option is to use auto-carving to get the maximum amount of space
easily, however, after doing this (2TB, 2TB, 1.8TB) for a 10 x 750GB
array, only the first partition remains afer reboot.
Before reboot:
/dev/sdb1
On Sat, 21 Jul 2007, Justin Piszcz wrote:
Quick question-- under Kernel 2.4 without 2TB support enabled, the only other
option is to use auto-carving to get the maximum amount of space easily,
however, after doing this (2TB, 2TB, 1.8TB) for a 10 x 750GB array, only the
first partition
On Sat, 21 Jul 2007, Justin Piszcz wrote:
On Sat, 21 Jul 2007, Justin Piszcz wrote:
Quick question-- under Kernel 2.4 without 2TB support enabled, the only
other option is to use auto-carving to get the maximum amount of space
easily, however, after doing this (2TB, 2TB, 1.8TB) for a 10
On 6/1/06, NeilBrown [EMAIL PROTECTED] wrote:
When an array has a bitmap, a device can be removed and re-added
and only blocks changes since the removal (as recorded in the bitmap)
will be resynced.
Neil,
Does the same apply when a bitmap-enabled raid1's member goes faulty?
Meaning even if a
On Fri, Jul 20, 2007 at 08:35:45AM +0100, Anton Altaparmakov wrote:
On 20 Jul 2007, at 06:13, Al Boldi wrote:
As always, a good friend of mine managed to scratch my partion
table by
cat'ing /dev/full into /dev/sda. I was able to push him out of the
way, but
at least the first 100MB are
On Fri, 20 Jul 2007 12:59:41 +1000
Neil Brown [EMAIL PROTECTED] wrote:
So reiserfs thinks the devices is 64K larger than it really is. I
wonder how that happened.
resize_reiserfs -s -64K /dev/md1
Neil, I discovered how the 64k larger issue happened...
It was my fault.. I
Hello Andrew ,
On Tue, 17 Jul 2007, Andrew Burgess wrote:
The 'MCE's have been ongoing for sometime . I have replaced every item
in the system except the chassis scsi backplane power supply(750Watts) .
Everything . MB,cpu,memory,scsi controllers, ...
These
I'm making raid 5 consisting of 4 disks, 500 GB each, with one spare
standby. In future to be expanded with extra disks. Server will be running
with ups, and with extra machine doing daily rsync backup of the system and
stuff deemed important. On top of the raid, there will probably be simple
Theodore Tso wrote:
On Sat, Jul 21, 2007 at 07:54:14PM +0200, Rene Herman wrote:
sfdisk -d already works most of the time. Not as a verbatim tool (I
actually semi-frequently use a sfdisk -d /dev/hda | sfdisk invocation
as a way to _rewrite_ the CHS fields to other values after changing
11 matches
Mail list logo