Anssi Hannula wrote:
Neil Brown wrote:
On Monday April 24, [EMAIL PROTECTED] wrote:
# mdadm --grow /dev/md_d1 --raid-devices=3 --backup-file backupfile
mdadm: Need to backup 128K of critical section..
mdadm: /dev/md_d1: Cannot get array details from sysfs
Strace shows that it's trying to
Arthur Britto wrote:
On Sun, 2006-04-23 at 17:17 -0700, Tim Bostrom wrote:
I bought two extra 250GB drives - I'll try using dd_rescue as
recommended and see if I can get a good copy of hdf online.
You might want to use dd_rhelp:
http://www.kalysto.org/utilities/dd_rhelp/index.en.html
Having
On Mon, Apr 24, 2006 at 07:45:27AM +1000, Neil Brown wrote:
your array isn't degraded. In this case it is (I think) very unusual
and may not be the cause of your corruption, but you should avoid
using the flag anyway.
thanks a lot for your time and your attention, Neil. Your support it's fast
On Sun, 5 Feb 2006 09:07:29 +1100 Lewis Shobbrook wrote:
Basically it just states waiting X seconds
Please post in public rather than to me privately.
If this debate is related to a bug already filed against the Debian
package of yaird then cc that bugreport: bug number@bugs.debian.org -
and
On Mon, 24 Apr 2006 17:13:42 +0200 Jonas Smedegaard wrote:
On Sun, 5 Feb 2006 09:07:29 +1100 Lewis Shobbrook wrote:
Basically it just states waiting X seconds
Please post in public rather than to me privately.
Uh, how embarrassing: I thought I was looking in my inbox, but instead
was
On 23 Apr 2006, Mark Hahn stipulated:
I've seen a lot of cheap disks say (generally deep in the data sheet
that's only available online after much searching and that nobody ever
reads) that they are only reliable if used for a maximum of twelve hours
a day, or 90 hours a week, or something of
I have used Acronis to create quick images of critical servers that
were using either hardware RAID or that had a single drive. It works
great and is probably one of the best imaging tools that I have seen
up until i tried to restore an image of md partitions on a RHEL 3 box.
I have two 250GB SATA
Hello,
Reduce the raid6_end_write_request() spinlock window.
Signed-off-by: Coywolf Qi Hunt [EMAIL PROTECTED]
---
diff --git a/drivers/md/raid6main.c b/drivers/md/raid6main.c
index bc69355..820536e 100644
--- a/drivers/md/raid6main.c
+++ b/drivers/md/raid6main.c
@@ -468,7 +468,6 @@ static int
Hello,
Fix raid6_unplug_device() to not disturb raid6d unnecessarily.
Signed-off-by: Coywolf Qi Hunt [EMAIL PROTECTED]
---
diff --git a/drivers/md/raid6main.c b/drivers/md/raid6main.c
index 820536e..d3deedb 100644
--- a/drivers/md/raid6main.c
+++ b/drivers/md/raid6main.c
@@ -1644,8 +1644,8 @@
On Tuesday April 25, [EMAIL PROTECTED] wrote:
Hello,
Reduce the raid6_end_write_request() spinlock window.
Andrew: please don't include these in -mm. This one and the
corresponding raid5 are wrong, and I'm not sure yet the unplug_device
changes.
In this case, the call to md_error, which in
10 matches
Mail list logo