Hi,
(I just subscribed, sorry if this is a dupe. I did try to match the
subject from the archives, but couldn't find any...)
I ran into trouble after upgrading a Debian Sarge system from 2.6.11 to
2.6.15. To be more precise, it turned out that md/mdadm seems to not
function properly during
Martin Stender wrote:
Hi there!
I have two identical disks sitting on a Promise dual channel IDE
controller. I guess both disks are primary's then.
One of the disks have failed, so I bought a new disk, took out the
failed disk, and put in the new one.
That might seem a little naive, and
On Sun, 9 Apr 2006, Marc L. de Bruin wrote:
...
Okay, just pressing Control-D continues the boot process and AFAIK the root
filesystemen actually isn't corrupt. Running e2fsck returns no errors and
booting 2.6.11 works just fine, but I have no clue why it picked the wrong
partitions to build
On Sun, Apr 09, 2006 at 02:35:53PM +0200, Marc L. de Bruin wrote:
Hi,
(I just subscribed, sorry if this is a dupe. I did try to match the
subject from the archives, but couldn't find any...)
I ran into trouble after upgrading a Debian Sarge system from 2.6.11 to
2.6.15. To be more precise,
Brad Campbell wrote:
Martin Stender wrote:
Hi there!
I have two identical disks sitting on a Promise dual channel IDE
controller. I guess both disks are primary's then.
One of the disks have failed, so I bought a new disk, took out the
failed disk, and put in the new one.
That might
I'm sorry - I replied to Brad's email a few hours ago, but I was a
bit too fast, and didn't notice I was replying to his personal account.
Here's my reply - as you can see, all is fine now! Thank you both!
(doing a '#cat /proc/mdstat', show that everything went well)
Martin
reply
Hello
is there a way to batch explicitely write requests raid5 issues?
sort of like TCP_CORK?
for example, there is a raid5 built from 3 disks with chunk=64K.
one types dd if=/dev/zero of=/dev/md0 bs=128k count=1
OK, so this is an aligned, whole-stripe write.
and 128K
bio gets into the raid5.
On 4/8/06, Mike Garey [EMAIL PROTECTED] wrote:
I have one last question though.. When I update /boot/grub/menu.lst
while booted from /dev/md0 with both disks available, does this file
get written to the MBR on both disks, or do I have to do this
manually?
Grub's configuration lives on both
On Saturday April 8, [EMAIL PROTECTED] wrote:
Good day all,
is there a way to batch explicitely write requests raid5 issues?
for example, there is a raid5 built from 3 disks with chunk=64K.
one types dd if=/dev/zero of=/dev/md0 bs=128k count=1 and 128K
bio gets into the raid5. raid5
