Mitchell Laks wrote:
On Sunday 13 March 2005 10:49 am, David Greave wrote: Many Helpful remarks:
David I am grateful that you were there for me.
No probs - we've all been there!
My assessment (correct me if I am wrong) is that I have to rethink my
architecture. As I continue to work with
kernel version, mdadm version?
David
-
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
Mitchell Laks wrote:
Hi,
I have a remote system with a raid1 of a data disk. I got a call from the
person using the system that the application that writes to the data disk was
not working.
system drive is /dev/hda with separte partitions / , /var, /home, /tmp.
data drive is linux software
I had some more bright ideas and here is what happened:
I am unable to even do ls on the directory mounted on this raid device.
So, I said, maybe the problem is that I need to run fsck.ext3 on the drive
first. So I tried to umount it and i got the error message:
A1:~# umount /home/big0
umount:
One more bit of information:
this was a bit of info from
tail /var/log/kern.log
Mar 11 04:42:11 A1 kernel:
Mar 11 04:42:11 A1 kernel: hdg: drive not ready for command
Mar 11 04:42:11 A1 kernel: raid1: hdg1: rescheduling sector 215908496
Mar 11 04:42:11 A1 kernel: raid1: hdg1: redirecting
