on 10-21-2010 9:13 AM fred smith spake the following:
On Thu, Oct 21, 2010 at 08:59:13AM -0700, Nataraj wrote:
fred smith wrote:
On Tue, Oct 19, 2010 at 07:34:19PM -0700, Nataraj wrote:
I've seen this kind of thing happen when the autodetection stuff
misbehaves. I'm not sure why it does
fred smith wrote:
On Tue, Oct 19, 2010 at 07:34:19PM -0700, Nataraj wrote:
I've seen this kind of thing happen when the autodetection stuff
misbehaves. I'm not sure why it does this or how to prevent it. Anyway,
to recover, I would use something like:
mdadm --stop /dev/md125
mdadm
On Thu, Oct 21, 2010 at 08:59:13AM -0700, Nataraj wrote:
fred smith wrote:
On Tue, Oct 19, 2010 at 07:34:19PM -0700, Nataraj wrote:
I've seen this kind of thing happen when the autodetection stuff
misbehaves. I'm not sure why it does this or how to prevent it. Anyway,
to recover,
fred smith wrote:
Thanks for the additional information.
I'll try backing up everything this weekend then will take a stab at it.
someone said earlier that the differing raid superblocks were probably
the cause of the misassignment in the first place. but I have no clue
how the superblocks
Nataraj wrote:
fred smith wrote:
Thanks for the additional information.
I'll try backing up everything this weekend then will take a stab at it.
someone said earlier that the differing raid superblocks were probably
the cause of the misassignment in the first place. but I have no clue
Nataraj wrote:
Nataraj wrote:
fred smith wrote:
Thanks for the additional information.
I'll try backing up everything this weekend then will take a stab at it.
someone said earlier that the differing raid superblocks were probably
the cause of the misassignment in the first
On Tue, Oct 19, 2010 at 07:34:19PM -0700, Nataraj wrote:
fred smith wrote:helppain/backups/disks/
hi all!
back in Aug several of you assisted me in solving a problem where one
of my drives had dropped out of (or been kicked out of) the raid1 array.
something vaguely similar appears to
fred smith wrote:
On Tue, Oct 19, 2010 at 07:34:19PM -0700, Nataraj wrote:
fred smith wrote:helppain/backups/disks/
snip
Well, I've already tried to use --fail and --remove on md125 and md126
but I'm told the members are still active.
mdadm /dev/md126 --fail
On Wed, Oct 20, 2010 at 4:34 AM, Nataraj incoming-cen...@rjl.com wrote:
When I create my Raid arrays, I always use the option --bitmap=internal.
With this option set, a bitmap is used to keep track of which pages on
the drive are out of date and then you only resync pages which need
updating
Rudi Ahlers wrote:
On Wed, Oct 20, 2010 at 4:34 AM, Nataraj incoming-cen...@rjl.com wrote:
When I create my Raid arrays, I always use the option --bitmap=internal.
With this option set, a bitmap is used to keep track of which pages on
the drive are out of date and then you only resync pages
hi all!
back in Aug several of you assisted me in solving a problem where one
of my drives had dropped out of (or been kicked out of) the raid1 array.
something vaguely similar appears to have happened just a few mins ago,
upon rebooting after a small update. I received four emails like this,
fred smith wrote:
hi all!
back in Aug several of you assisted me in solving a problem where one
of my drives had dropped out of (or been kicked out of) the raid1 array.
something vaguely similar appears to have happened just a few mins ago,
upon rebooting after a small update. I received four
On Tue, Oct 19, 2010 at 7:59 PM, fred smith
fre...@fcshome.stoneham.ma.us wrote:
back in Aug several of you assisted me in solving a problem where one
of my drives had dropped out of (or been kicked out of) the raid1 array.
something vaguely similar appears to have happened just a few mins
fred smith wrote:helppain/backups/disks/
hi all!
back in Aug several of you assisted me in solving a problem where one
of my drives had dropped out of (or been kicked out of) the raid1 array.
something vaguely similar appears to have happened just a few mins ago,
upon rebooting after a
Nataraj wrote:
I've seen this kind of thing happen when the autodetection stuff
misbehaves. I'm not sure why it does this or how to prevent it. Anyway,
to recover, I would use something like:
mdadm --stop /dev/md125
mdadm --stop /dev/md126
If for some reason the above commands fail,
15 matches
Mail list logo
