-
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
On Wednesday August 9, [EMAIL PROTECTED] wrote:
> >> Why we're updating it BACKWARD in the first place?
> >
> >To avoid writing to spares when it isn't needed - some people want
> >their spare drives to go to sleep.
>
> That sounds a little dangerous. What if it decrements below 0?
It cannot.
md
No, it wasn't *less* reliable than a single drive; you benefited as soon as a
James Peverill wrote:
>
> In this case the raid WAS the backup... however it seems it turned out
> to be less reliable than the single disks it was supporting. In the
> future I think I'll make sure my disks have varyin
James Peverill wrote:
> I'll try the force assemble but it sounds like I'm screwed. It
> sounds like what happened was that two of my drives developed bad
> sectors in different places that weren't found until I accessed
> certain areas (in the case of the first failure) and did the drive
> r
In this case the raid WAS the backup... however it seems it turned out
to be less reliable than the single disks it was supporting. In the
future I think I'll make sure my disks have varying ages so they don't
fail all at once.
James
RAID is no excuse for backups.
PS:
-
To unsubscribe f
failure). In the future, is there a way to help prevent this?
sure; periodic scans (perhaps smartctl) of your disks would prevent it.
I suspect that throttling the rebuild rate is also often a good idea
if there's any question about disk reliability.
RAID is no excuse for backups.
I wish pe
2006/8/9, James Peverill <[EMAIL PROTECTED]>:
failure). In the future, is there a way to help prevent this?
RAID is no excuse for backups.
smartd may warn you in advance.
Best
Martin
PS: http://en.wikipedia.org/wiki/Top-posting#Top-posting
-
To unsubscribe from this list: send the line "u
I'll try the force assemble but it sounds like I'm screwed. It sounds
like what happened was that two of my drives developed bad sectors in
different places that weren't found until I accessed certain areas (in
the case of the first failure) and did the drive rebuild (for the second
failure)
On Wed, Aug 09, 2006 at 01:55:56PM +0400, Serge Torop wrote:
I need to install softw. RAID1 to working RedHat EL4.
I used "rescue mode" for creating RAID arrays.
...
resize2fs /dev/md2 and see a error messge:
resize2fs 1.39
/resize2fs: relocation error: - /resize2fs: undefined symbol: ext2fs_
Hello, all.
I need to install softw. RAID1 to working RedHat EL4.
I used "rescue mode" for creating RAID arrays.
what do I do?:
1. install my own initrd for normal booting
2. change the disk partition type to "Linux Auroraid"
on /dev/hda, dev/hdc
3. create RAID1, by using "mkraid --really-fo
Michael Tokarev wrote:
Why we're updating it BACKWARD in the first place?
Don't know this one...
Also, why, when we adding something to the array, the event counter is
checked -- should it resync regardless?
If you remove a drive and then add it back with
no changes in the meantime, then yo
11 matches
Mail list logo
