Re: RAID1 on sparc64
On Fri, 21 Dec 2001 02:04, Tim Kent wrote: > # fdisk /dev/sdb > Command (m for help): t > Partition number (1-8): 1 > Hex code (type L to list codes): fd > Changed system type of partition 1 to fd (Unknown) I noticed that the 0xfd partition type is defined in the fdisk source in the file i386_sys_types.c, I guess it doesn't apply to SPARC. After more searching - in the 2.4.16 kernel source the relevant kernel code is in genhd.h which appears to be i386-only. The function to autodetect devices that are parts of a RAID is md_autodetect_dev() which is only called from msdos.c and md.c. I think that the call from md.c is for verifying a device that the RAID sub-system already has decided to use. So it seems that software RAID is really only fully functional on Intel! >From briefly examining the code it appears that it wouldn't be THAT difficult to pick a suitable partition identifying mechanism (if there is one) and having a md_autodetect_dev() call after it's recognised, if I owned a SPARC I'd probably give it a go myself. However at the moment I have no access to SPARC hardware, so I've CC'd Neil Brown, hopefully he can add it to a future release. > # mkraid /dev/md0 > handling MD device /dev/md0 > analyzing super-block > disk 0: /dev/sdb1, 2356000kB, raid superblock at 2355904kB > disk 1: /dev/sda1, failed > /dev/md0: Invalid argument > > I have tried running mkraid with the filesystem type set to 83 but this > gives the same error. This is my /etc/raidtab: > > raiddev /dev/md0 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > chunk-size 4 > persistent-superblock 1 > device /dev/sdb1 > raid-disk 0 > device /dev/sda1 > failed-disk 1 > > raiddev /dev/md1 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > chunk-size 4 > persistent-superblock 1 > device /dev/sdb2 > raid-disk 0 > device /dev/sda2 > failed-disk 1 -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page
Re: RAID1 on sparc64
[Please use < 80 chars lines] On Fri, Dec 21, 2001 at 11:04:18 +1000, Tim Kent wrote: > I have installed Debian 2.2 on a Sun Enterprise 420R. Everything seems to > be working alright except software RAID, which is working fine on our x86 > machines. The patch itself installs cleanly as does the kernel build, it > is just the 'fdisk' and 'mkraid' tools that give me issues: Which mkraid? The "raidtools" or the "raidtools2" one? > # fdisk /dev/sdb Erm, mkraid complains about a partition on sda, not sdb. Does sda have a sane partition table? > # mkraid /dev/md0 > handling MD device /dev/md0 > analyzing super-block > disk 0: /dev/sdb1, 2356000kB, raid superblock at 2355904kB > disk 1: /dev/sda1, failed > /dev/md0: Invalid argument If sda has a sane partition table it's probably best to find out where that "Invalid argument" comes from; please provide the relevant part of the log produced by "strace -f -o /tmp/strace.log mkraid /dev/md0". HTH, Ray -- Signs of world domination: "Tonight on Celebrity Deathmatch: Tux takes on the BSD daemon"
Re: RAID1 on sparc64
On Fri, 21 Dec 2001 02:04, Tim Kent wrote: > # fdisk /dev/sdb > Command (m for help): t > Partition number (1-8): 1 > Hex code (type L to list codes): fd > Changed system type of partition 1 to fd (Unknown) I noticed that the 0xfd partition type is defined in the fdisk source in the file i386_sys_types.c, I guess it doesn't apply to SPARC. After more searching - in the 2.4.16 kernel source the relevant kernel code is in genhd.h which appears to be i386-only. The function to autodetect devices that are parts of a RAID is md_autodetect_dev() which is only called from msdos.c and md.c. I think that the call from md.c is for verifying a device that the RAID sub-system already has decided to use. So it seems that software RAID is really only fully functional on Intel! >From briefly examining the code it appears that it wouldn't be THAT difficult to pick a suitable partition identifying mechanism (if there is one) and having a md_autodetect_dev() call after it's recognised, if I owned a SPARC I'd probably give it a go myself. However at the moment I have no access to SPARC hardware, so I've CC'd Neil Brown, hopefully he can add it to a future release. > # mkraid /dev/md0 > handling MD device /dev/md0 > analyzing super-block > disk 0: /dev/sdb1, 2356000kB, raid superblock at 2355904kB > disk 1: /dev/sda1, failed > /dev/md0: Invalid argument > > I have tried running mkraid with the filesystem type set to 83 but this > gives the same error. This is my /etc/raidtab: > > raiddev /dev/md0 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > chunk-size 4 > persistent-superblock 1 > device /dev/sdb1 > raid-disk 0 > device /dev/sda1 > failed-disk 1 > > raiddev /dev/md1 > raid-level 1 > nr-raid-disks 2 > nr-spare-disks 0 > chunk-size 4 > persistent-superblock 1 > device /dev/sdb2 > raid-disk 0 > device /dev/sda2 > failed-disk 1 -- http://www.coker.com.au/bonnie++/ Bonnie++ hard drive benchmark http://www.coker.com.au/postal/ Postal SMTP/POP benchmark http://www.coker.com.au/projects.html Projects I am working on http://www.coker.com.au/~russell/ My home page -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RAID1 on sparc64
[Please use < 80 chars lines] On Fri, Dec 21, 2001 at 11:04:18 +1000, Tim Kent wrote: > I have installed Debian 2.2 on a Sun Enterprise 420R. Everything seems to > be working alright except software RAID, which is working fine on our x86 > machines. The patch itself installs cleanly as does the kernel build, it > is just the 'fdisk' and 'mkraid' tools that give me issues: Which mkraid? The "raidtools" or the "raidtools2" one? > # fdisk /dev/sdb Erm, mkraid complains about a partition on sda, not sdb. Does sda have a sane partition table? > # mkraid /dev/md0 > handling MD device /dev/md0 > analyzing super-block > disk 0: /dev/sdb1, 2356000kB, raid superblock at 2355904kB > disk 1: /dev/sda1, failed > /dev/md0: Invalid argument If sda has a sane partition table it's probably best to find out where that "Invalid argument" comes from; please provide the relevant part of the log produced by "strace -f -o /tmp/strace.log mkraid /dev/md0". HTH, Ray -- Signs of world domination: "Tonight on Celebrity Deathmatch: Tux takes on the BSD daemon" -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RAID1 on sparc64
Hello, I have installed Debian 2.2 on a Sun Enterprise 420R. Everything seems to be working alright except software RAID, which is working fine on our x86 machines. The patch itself installs cleanly as does the kernel build, it is just the 'fdisk' and 'mkraid' tools that give me issues: # fdisk /dev/sdb Command (m for help): t Partition number (1-8): 1 Hex code (type L to list codes): fd Changed system type of partition 1 to fd (Unknown) # mkraid /dev/md0 handling MD device /dev/md0 analyzing super-block disk 0: /dev/sdb1, 2356000kB, raid superblock at 2355904kB disk 1: /dev/sda1, failed /dev/md0: Invalid argument I have tried running mkraid with the filesystem type set to 83 but this gives the same error. This is my /etc/raidtab: raiddev /dev/md0 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/sdb1 raid-disk 0 device /dev/sda1 failed-disk 1 raiddev /dev/md1 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/sdb2 raid-disk 0 device /dev/sda2 failed-disk 1 Regards, Tim
RAID1 on sparc64
Hello, I have installed Debian 2.2 on a Sun Enterprise 420R. Everything seems to be working alright except software RAID, which is working fine on our x86 machines. The patch itself installs cleanly as does the kernel build, it is just the 'fdisk' and 'mkraid' tools that give me issues: # fdisk /dev/sdb Command (m for help): t Partition number (1-8): 1 Hex code (type L to list codes): fd Changed system type of partition 1 to fd (Unknown) # mkraid /dev/md0 handling MD device /dev/md0 analyzing super-block disk 0: /dev/sdb1, 2356000kB, raid superblock at 2355904kB disk 1: /dev/sda1, failed /dev/md0: Invalid argument I have tried running mkraid with the filesystem type set to 83 but this gives the same error. This is my /etc/raidtab: raiddev /dev/md0 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/sdb1 raid-disk 0 device /dev/sda1 failed-disk 1 raiddev /dev/md1 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/sdb2 raid-disk 0 device /dev/sda2 failed-disk 1 Regards, Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
