Thanks Neil. This took care of my issue. I was doing a full set of
tests to make sure before I replied. Thanks for all your hard work.
Don
On 5/31/07, Neil Brown <[EMAIL PROTECTED]> wrote:
On Wednesday May 30, [EMAIL PROTECTED] wrote:
> Neil, I sent the scripts to you. Any update on this issue?
On Wednesday May 30, [EMAIL PROTECTED] wrote:
> Neil, I sent the scripts to you. Any update on this issue?
Sorry, I got distracted.
Your scripts are way more complicated than needed. Most of the logic
in there is already in mdadm.
mdadm --assemble /dev/md_d0 --run --uuid=$BOOTUUID /dev/sd[ab
Neil, I sent the scripts to you. Any update on this issue?
Thanks
Don
On 5/21/07, Neil Brown <[EMAIL PROTECTED]> wrote:
On Monday May 21, [EMAIL PROTECTED] wrote:
> I was going to get back with you concerning the low resync rates. The
> data corruption happens like this.
> 1. Start with fully
On Monday May 21, [EMAIL PROTECTED] wrote:
> I was going to get back with you concerning the low resync rates. The
> data corruption happens like this.
> 1. Start with fully active array. Everything is fine.
> 2. I remove a drive. Everything is fine. I then will power off the machine.
> 3. I pow
On 5/21/07, Neil Brown <[EMAIL PROTECTED]> wrote:
On Monday May 21, [EMAIL PROTECTED] wrote:
> On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
> >
> > I am still trying to get where I had the low recover rate with the
> > bitmap turned on. I will get back with you
> > Don
> >
> Any new updates
On Monday May 21, [EMAIL PROTECTED] wrote:
> On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
> >
> > I am still trying to get where I had the low recover rate with the
> > bitmap turned on. I will get back with you
> > Don
> >
> Any new updates Neil?
> Any new things to try to get you additional
On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
> On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
> > On 5/16/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> > > On Wednesday May 16, [EMAIL PROTECTED] wrote:
> > > ...
> > > >
> > > > The problem a
On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
> On 5/16/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> > On Wednesday May 16, [EMAIL PROTECTED] wrote:
> > ...
> > >
> > > The problem arises when I do a drive removal such as sda and then I
> > > r
On 5/16/07, Don Dupuis <[EMAIL PROTECTED]> wrote:
On 5/16/07, Neil Brown <[EMAIL PROTECTED]> wrote:
> On Wednesday May 16, [EMAIL PROTECTED] wrote:
> ...
> >
> > The problem arises when I do a drive removal such as sda and then I
> > remove power from the system. Most of the time I will have a co
On 5/16/07, Neil Brown <[EMAIL PROTECTED]> wrote:
On Wednesday May 16, [EMAIL PROTECTED] wrote:
...
>
> The problem arises when I do a drive removal such as sda and then I
> remove power from the system. Most of the time I will have a corrupted
> partition on the md device. Other corruption will
On Wednesday May 16, [EMAIL PROTECTED] wrote:
...
>
> The problem arises when I do a drive removal such as sda and then I
> remove power from the system. Most of the time I will have a corrupted
> partition on the md device. Other corruption will be my root partition
> which is an ext3 filesystem.
I have a system with 4 disks in a raid10 configuration. Here is the
output of mdadm:
bash-3.1# mdadm -D /dev/md_d0
/dev/md_d0:
Version : 00.90.03
Creation Time : Wed May 16 10:28:44 2007
Raid Level : raid10
Array Size : 3646464 (3.48 GiB 3.73 GB)
Used Dev Size : 2734848 (2.61 GiB
12 matches
Mail list logo
