Hello all,
Surfing on the web I found a patch from Steinar H. Gunderson which
implements raid5 resize stuff.
(http://marc.theaimsgroup.com/?l=linux-raidm=112998877619952w=2).
It seems like it has been included in the 2.6.14 kernel
(http://www.linuxhq.com/kernel/v2.6/14/drivers/md/raid5.c), but I
Ok, thanks for your answer.
Then I suppose I will have to wait a bit.
If I can be of any help for testing and hacking purpose, please let me know.
I think I will really *need* this feature by the end of february,
2006. Do you think I have any chance to use it safely by that time ?
Best regards,
On Thursday December 1, [EMAIL PROTECTED] wrote:
Ok, thanks for your answer.
Then I suppose I will have to wait a bit.
If I can be of any help for testing and hacking purpose, please let me know.
I think I will really *need* this feature by the end of february,
2006. Do you think I have any
I have (had) a 4 disk RAID5 /dev/sd[abcd]1.
sda went bad (really, bad sectors) and is being replaced, hope
to get a replacement tomorrow.
While the array was degraded (but running) sdd failed (controller
trouble) and was marked as failed. The array went down (naturally).
I am rather sure that
Hello.
I have a degraded 4 disk raid 5 array consisting of:
/dev/sdd3
/dev/sdc3
/dev/sdb3
/dev/sda3
Recently on boot the system crashed mid-boot for another unrelated (I
think) config issue. I then booted with a live cd and when I tried to
re-build /dev/md0, /dev/sdb3 came up as faulty. Upon
On Tue, Nov 29, 2005 at 11:35:18AM -0800, Andrew Burgess wrote:
The time and speed display for resync is wrong, the recovery numbers are fine.
The resync is actually running at a few MB/sec.
md1 : active raid6 sdn1[8](S) sde1[9] sdq1[0] sdu1[6] sdo1[5] sdaa3[4] sdab1[2]
sds1[1]
1757815296
Eyal Lebedinsky wrote:
I have (had) a 4 disk RAID5 /dev/sd[abcd]1.
[trim]
By this evening this will become urgent, so if anyone can
reply then please do.
To bring it up in degraded mode, can I do a --create and tell
it to use sd[abc] and mark sdd as failed? I can then force
--run. An --assemble
Little off this topic, but how did you get the AMD64 x2 to run in single
processor mode? I was trying to figure this out months ago.
Just boot with maxcpus=1 or make a UP kernel.
I have it working now SMP by dumping 2.6.14 and using 2.6.13.4. Nothing
but trouble with .14 including hosing half
NeilBrown [EMAIL PROTECTED] wrote:
+DECLARE_WAIT_QUEUE_HEAD(md_event_waiters);
static scope?
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
NeilBrown [EMAIL PROTECTED] wrote:
- conf = kmalloc (sizeof (*conf) + mddev-raid_disks*sizeof(dev_info_t),
+conf = kzalloc (sizeof (*conf) + mddev-raid_disks*sizeof(dev_info_t),
-new = (mddev_t *) kmalloc(sizeof(*new), GFP_KERNEL);
+new = (mddev_t *) kzalloc(sizeof(*new),
Neil Brown wrote:
Q1) What is the correct command to bring these three up as
degraded?
mdadm --assemble --force /dev/mdX /dev/sd[abc]1
However this won't work with the superblocks you have. So
mdadm --create /dev/mdX -l5 -c256 -n4 missing /dev/sda /dev/sdb /dev/sdc
I do not see
NeilBrown [EMAIL PROTECTED] wrote:
+ paddr = kmap_atomic(page, KM_USER0);
+memset(paddr + offset, 0xff,
PAGE_SIZE - offset);
This page which is being altered is a user-visible one, no? A pagecache
Neil Brown wrote:
On Friday December 2, [EMAIL PROTECTED] wrote:
Neil Brown wrote:
Q1) What is the correct command to bring these three up as
degraded?
mdadm --assemble --force /dev/mdX /dev/sd[abc]1
However this won't work with the superblocks you have. So
mdadm --create /dev/mdX
I apologize for being so verbose in my last post...it was late. My
problem again, in a more succinct form:
After a system crash during bootup, I attempted:
mdadm --add /dev/md0 /dev/sdb3
This caused the following:
Number Major Minor RaidDevice State
0 8 510
On Friday December 2, [EMAIL PROTECTED] wrote:
Which generates errors when I try and copy off large amounts of data:
About ten of these:
ata1: translated ATA stat/err 0x25/00 to SCSI SK/ASC/ASCQ 0x4/00/00
ata1: status=0x25 { DeviceFault CorrectedError Error }
Thank you for the feedback Neil.
Although, your last comment did confuse me a little...run what in
parallel? Should I be running badblocks against the unassembled
components of the raid and then doing something like:
fsck -l /badblockfile_sda3.txt /dev/md0
fsck -l /badblockfile_sdb3.txt
On Friday December 2, [EMAIL PROTECTED] wrote:
Thank you for the feedback Neil.
Although, your last comment did confuse me a little...run what in
parallel? Should I be running badblocks against the unassembled
components of the raid and then doing something like:
fsck -l
17 matches
Mail list logo
