Hello, Dan.
On Fri, Feb 03, 2006 at 04:58:02PM -0700, Dan Williams ([EMAIL PROTECTED])
wrote:
Thanks for the feedback, I will implement these changes. Also, now
that you have given me some hints as to the acrypto vocabulary, I can
start looking into integration and cross pollenation efforts.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This thread is all very relevant.
But please cc [EMAIL PROTECTED] rather than me
privately.
Regards,
- Jonas
- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
- Enden er nær:
Ahh, i almost forget!
The mdadm is sometimes drop cannot allocate memory and next try
segfault
when i try -G --bitmap=internal on 2TB arrays!
And after segfault, the full raid is stops...
Cheers,
Janos
I think i found the bug, its me. :-)
Today it happens again, and i see, i have
--cut--
I plan to resize (grow) one raid4 array.
1. stop the array.
2. resize the partition on all disks to fit the maximum size.
The approach is currently not supported. It would need a change to
mdadm to find the old superblock and relocate it to the new end of the
On Saturday 04 February 2006 11:22 am, you wrote:
On Sat, 4 Feb 2006, Lewis Shobbrook wrote:
Is there any way to avoid this requirement for input, so that the system
skips the missing drive as the raid/initrd system did previously?
what boot errors are you getting before it drops you to the
If you remove the '-Werror' it'll compile and work, but you still can't
convert a raid 0 to a raid 5. You're raid level understanding is off as
well, raid 5 is a parity block rotating around all drives, you were
thinking of raid 4 which has a single parity disk. Migrating raid 0 to
raid 4 (and
