Re: mdadm > 2.2 ver1 superblock regression?

2006-04-06 Thread Mike Snitzer
On 4/7/06, Neil Brown <[EMAIL PROTECTED]> wrote: > On Friday April 7, [EMAIL PROTECTED] wrote: > > > > Seeing this hasn't made it into a released kernel yet, I might just > > change it. But I'll have to make sure that old mdadm's don't mess > > things up ... I wonder how I will do that :-( > > > >

ANNOUNCE: mdadm 2.4.1 - A tool for managing Soft RAID under Linux

2006-04-06 Thread Neil Brown
I am pleased to announce the availability of mdadm version 2.4.1 It is available at the usual places: http://www.cse.unsw.edu.au/~neilb/source/mdadm/ and http://www.{countrycode}.kernel.org/pub/linux/utils/raid/mdadm/ mdadm is a tool for creating, managing and monitoring device arrays u

Re: mdadm > 2.2 ver1 superblock regression?

2006-04-06 Thread Neil Brown
On Friday April 7, [EMAIL PROTECTED] wrote: > > Seeing this hasn't made it into a released kernel yet, I might just > change it. But I'll have to make sure that old mdadm's don't mess > things up ... I wonder how I will do that :-( > > Thanks for the report. Yes, try 2.4.1 (just released). Tha

[PATCH] md: Make sure 64bit fields in version-1 metadata are 64-bit aligned.

2006-04-06 Thread NeilBrown
This patch should go in 2.6.17-rc2 if at all possible. If the problem gets left much longer, a more ugly solution might be needed. ### Comments for Changeset reshape_position is a 64bit field that was not 64bit aligned. So swap with new_level. NOTE: this is a user-visible change. However: -

Re: mdadm > 2.2 ver1 superblock regression?

2006-04-06 Thread Neil Brown
On Thursday April 6, [EMAIL PROTECTED] wrote: > When I try to create a RAID1 array with ver 1.0 superblock using mdadm > > 2.2 I'm getting: > WARNING - superblock isn't sized correctly > > Looking at the code (and adding a bit more debugging) it is clear that > all 3 checks fail in super1.c's calc

RE: accessing mirrired lvm on shared storage

2006-04-06 Thread Stern, Rick (Serviceguard Linux)
Matthias, Your best bet is to not activate the md mirrors until you need to. There is a theoretical case where one system (A) can be writing data while the other (B) is doing a remirror. B reads data in prep for a write, A writes to that same block, then B writes the old data. LVM does not re

mdadm > 2.2 ver1 superblock regression?

2006-04-06 Thread Mike Snitzer
When I try to create a RAID1 array with ver 1.0 superblock using mdadm > 2.2 I'm getting: WARNING - superblock isn't sized correctly Looking at the code (and adding a bit more debugging) it is clear that all 3 checks fail in super1.c's calc_sb_1_csum()'s "make sure I can count..." test. Is this a

Re: Partitioning md devices versus partitioining underlying devices

2006-04-06 Thread Bill Davidsen
On Thu, 6 Apr 2006, andy liebman wrote: > Hi, > > I have a fundamental question about WHERE it is best to do partititioning. > > Here's a concrete example. I have two 3ware RAID-5 arrays, each made up > of 12 500 GB drives. When presented to Linux, these are /dev/sda and > /dev/sdb -- each 5.5

Partitioning md devices versus partitioining underlying devices

2006-04-06 Thread andy liebman
Hi, I have a fundamental question about WHERE it is best to do partititioning. Here's a concrete example. I have two 3ware RAID-5 arrays, each made up of 12 500 GB drives. When presented to Linux, these are /dev/sda and /dev/sdb -- each 5.5 TB in size. I want to stripe the two arrays togethe