http://blog.gmane.org/gmane.linux.ataraid hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.linux.ataraid/2862 <pre> I'm trying to rebuild a raid 1 (dmraid+isw) unsuccessfully. I replaced the failed disk with a new one and the BIOS added it automatically to the raid. Running kernel 2.6.18-194.17.4.el5. # dmraid -r /dev/sda: isw, "isw_babcjifefe", GROUP, ok, 1953525165 sectors, data&lt; at &gt; 0 /dev/sdb: isw, "isw_babcjifefe", GROUP, ok, 1953525165 sectors, data&lt; at &gt; 0 # dmraid -s *** Group superset isw_babcjifefe --&gt; Subset name : isw_babcjifefe_Raid0 size : 1953519616 stride : 128 type : mirror status : nosync subsets: 0 devs : 2 spares : 0 When i try to start the raid i receive the next errors # dmraid -f isw -S -M /dev/sdb ERROR: isw: SPARE disk must use all space on the disk # dmraid -tay isw_babcjifefe_Raid0: 0 1953519616 mirror core 3 131072 sync block_on_error 2 /dev/sda 0 /dev/sdb 0 # dmraid -ay RAID set "isw_babcjifefe_Raid0" was not activated ERROR: device "isw_babcjifefe_Raid0" could not be found # dmraid -f isw -S -M /dev/sdb ERROR: isw: SPARE disk must use all space on the disk # </pre> Dead Gardens 2013-04-25T04:52:01 http://comments.gmane.org/gmane.linux.ataraid/2856 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It appears that PDC arrays &gt; 2 TB pretend they have &gt; 512 byte sector sizes. I'm trying to figure out how to patch dmraid to support this but I'm not sure how to tell device-mapper to use a different sector size. Is this possible? -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQoUsoAAoJEJrBOlT6nu75n9kIAIS8hdtJHFk5sOPBBcOZ+Htq rUOOBxHW3cCjHyAqXgAlazRDLeP2qSGODjy4e54ovKxGbN1QZ5yJhX/iPNpGVUFb bypZzYj5wjGBHmhmKD+5UKjBxHdrjOkluNCREdGDDoE9aRIyR+1JPjWEzJJDLvaO fnNoiHg3hQi+RgaOj2oHM2eGexYAFAsKI0qswRXbTnAfrcMCfmm2pf49b76zdZ7y Z6c+xVl43PhDfZiy/EiWqYkrNtagvin7CNjahW5zptmNdf1H7JAzpuXbf3uZ6g5F 9MkDn5BFdJOBwEL/WTi9ZBgbIn4aIf8CwsBrsQ9DC4FFoZ3hnZTW2lT6/2UpHMk= =pXpo -----END PGP SIGNATURE----- </pre> Phillip Susi 2012-11-12T19:16:56 http://comments.gmane.org/gmane.linux.ataraid/2850 <pre>Hi, I have a question about algorithm used in dmraid to retrieve the serial number from the scsi device: lib/device/scsi.c: 77 /* 78 * Retrieve SCSI serial number. 79 */ 80 #define MAX_RESPONSE_LEN 255 81 int 82 get_scsi_serial(struct lib_context *lc, int fd, struct dev_info *di, 83 enum ioctl_type type) 84 { 85 int ret = 0; 86 size_t actual_len; 87 unsigned char *response; 88 /* 89 * Define ioctl function and offset into response buffer of serial 90 * string length field (serial string follows length field immediately) 91 */ 92 struct { 93 int (*ioctl_func) (int, unsigned char *, size_t); 94 unsigned int start; 95 } param[] = { 96 { sg_inquiry, 3}, 97 { old_inquiry, 11}, 98 }, *p = (SG == type) ? param : param + 1; 99 100 if (!(response = dbg_malloc(MAX_RESPONSE_LEN))) 101 return 0; 102 10</pre> Petr Uzel 2012-11-02T10:25:15 http://comments.gmane.org/gmane.linux.ataraid/2835 <pre> Dear dmraid developers, Sometime in this mail-list it was said that the program dmraid was in maintaining mode and not further developed anymore. In the meantime the dm-developement team has put out new dm-target, which can be used by the tool. I would like to fork the latest RC and put on github, to continue developing the tool. I will give it a slightly new name, so people will not confuse it with the original. My plan is to add the support for new dm-targets and also implement more partition tables, starting with GPT. I am not really good at generating new names, but here are some ideas. dmraid-fbmw (forked by Mark-Willem) dmraid-fu (follow-up) dmraid-ext (extended version) So my question which name you think is a good one for the forked? And who can I connect if I have some questions about the tool. Greetings, Mark-Willem Jansen _______________________________________________ Ataraid-list mailing list Ataraid-list&lt; at &gt;redhat.com https://www.redhat.com/mailman/listinfo/ataraid-list</pre> Mark-Willem Jansen 2012-07-18T08:20:10 http://comments.gmane.org/gmane.linux.ataraid/2834 <pre> Dear md/dm developers, As I already pointed out on the ataraid-list, I have made a small patch for dmraid, so it will use the dm-raid target in state of the dm-raid45 target to handle raid4 and riad5 setups. This patch is added to this e-mail. To put it in context I use dmraid to detect my fakeraid, which is shared with a Windows OS. There were some things I could not figure out and would like to ask three questions regarding the arguments passed to the module. - First a more general question does it look okay to you what I have implemented? - Second what to do with the offset variable that is given by the metadata on the disk? On the other dmraid related modules the disk information is passed like [dev][offset]. With the dm-raid module it changed to [meta-dev][data-dev]. In the patch I ignore the meta-dev and just pass "- path_to_dev" to the module. This will work as the offset given by the metadata on my disks are equal to zero, the same value that is automatically set by the module. What does one hav</pre> Mark-Willem Jansen 2012-05-03T21:12:18 http://comments.gmane.org/gmane.linux.ataraid/2833 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A user recently filed this bug report against ubuntu 12.04: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/992975 I believe this is the result of my patch fixing the testing support, and testing being enabled by default. With testing enabled, it looks like dmraid is finding the physical disks both on the normal scsi devnode, and again on the dm devnode created by multipath-tools. Why does multipath-tools create a dm mapping for each physical disk by default? It seems like this is likely to cause other problems as well. I suppose that configuring dmraid with --disable-testing would resolve this issue ( and it probably should be disabled by default if it doesn't play well with multipath-tools ), but I'd like to understand multipath-tools better first and try to find a better solution. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPoKb4AAoJEJrBOlT6nu75NG</pre> Phillip Susi 2012-05-02T03:16:08 http://comments.gmane.org/gmane.linux.ataraid/2818 <pre> Dear dmraid developer(s)/maintainer(s), Since a few weeks I am trying to get my new rig up and running under linux. I run a dual-boot system with Windows 7 and Debian/wheezy. I have installed the OS files on a small SSD and have setup a RAID-5 for the rest of the files. It is a FakeRAID/SATA-RAID which is controlled by the AMD SB950 chip. Unfortunately dmraid does not seem to support this chip in combination with a RAID-5 setup. I would like to implement this, but to do that I need some help and information. The plan is as follows - Get dmraid working with the dm-raid module. Dmraid needs a dm-target that support RAID-5. In the past there was a patch for the prior 3.x linux-kernel which added the dm-raid45 module. Now a days there is a module called dm-raid which will provide the same aliases(dm-raid4, dm-raid5) as the dm-raid45 module. How does on check if dmraid can be made compatible with this new module? My first idea was to look at the symbols dm-raid and dm-raid45 export to the user space and which </pre> Mark-Willem Jansen 2012-03-23T16:52:20 http://comments.gmane.org/gmane.linux.ataraid/2817 <pre>Inglés : Many already we have contributed to the first project of free software dedicated to self-management in this campaign of collective financing, it collaborates and it spreads!/ Beginning campaign collective financing http://www.goteo.org/project/rebelaos-publicacion-por-la-autogestion?lang=en Login to enter with user of social networks and for would register in Goteo : http://www.goteo.org/user/login?lang=en Rebelaos! Publication by self-management A massive publication that floods the public transport, the work centers, the parks, the consumption centers, by means of distribution of 500,000 gratuitous units, acting simultaneously in all sides and nowhere. We announce the main tool of a vestibule Web for the management of self-sustaining resources by means of Drupal, in addition in the publication there will be an article dedicated to free software, hardware, It is being prepared in inglès, the machinery You can see more details in the index of the publication https://n-1.cc/pg/file/re</pre> Orquidea Salt mas 2012-03-02T18:59:01 http://comments.gmane.org/gmane.linux.ataraid/2813 <pre>_______________________________________________ Ataraid-list mailing list Ataraid-list&lt; at &gt;redhat.com https://www.redhat.com/mailman/listinfo/ataraid-list</pre> Phillip Susi 2012-01-10T22:55:57 http://comments.gmane.org/gmane.linux.ataraid/2811 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have been trying to get dmraid to alter the UUID of the devices it creates so that the rest of the system can use that information to differentiate between the different types of devices. My goal is to make sure that things like kpartx are not run each individual half of a raid10. I thought I could patch dmraid_uuid() to use "DMRAIDI-" as the prefix instead of "DMRAID-" for internal devices, but I have not been able to find a way to tell whether a given raid_set is itself a subset of another set. I thought that doing a find_set to see if this set's name can be found in the top level would do it, but find_set always fails to find the set, even when it is the top of the stack. Any suggestions? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPC7pnAAoJEJrBOlT6nu75L0QIAJ2uULZRZl1sW7xrYoYo7Lyn noHL/yojjyXXjQGF9ruU13wTm3ViPZitdrz+axvEfgNoe0NybjfZkg6j3hb1aHpn wVyWLLGgA</pre> Phillip Susi 2012-01-10T04:11:19 http://comments.gmane.org/gmane.linux.ataraid/2811 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have been trying to get dmraid to alter the UUID of the devices it creates so that the rest of the system can use that information to differentiate between the different types of devices. My goal is to make sure that things like kpartx are not run each individual half of a raid10. I thought I could patch dmraid_uuid() to use "DMRAIDI-" as the prefix instead of "DMRAID-" for internal devices, but I have not been able to find a way to tell whether a given raid_set is itself a subset of another set. I thought that doing a find_set to see if this set's name can be found in the top level would do it, but find_set always fails to find the set, even when it is the top of the stack. Any suggestions? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPC7pnAAoJEJrBOlT6nu75L0QIAJ2uULZRZl1sW7xrYoYo7Lyn noHL/yojjyXXjQGF9ruU13wTm3ViPZitdrz+axvEfgNoe0NybjfZkg6j3hb1aHpn wVyWLLGgA</pre> Phillip Susi 2012-01-10T04:11:19 http://comments.gmane.org/gmane.linux.ataraid/2796 <pre>The following patches have been carried by Ubuntu ( and some by debian as well ) for some time, and I feel they are appropriate for upstream merging. </pre> Phillip Susi 2011-12-06T18:39:23 http://comments.gmane.org/gmane.linux.ataraid/2793 <pre>Hi, I don't know if this is the correct place to send this, please send me information on where I should post of this is not the right place. dmraid version 1.0.0.rc16 (2009.09.16) shared RAID 0, Asus M2V motherboard, via 8237, 2 * hitachi 250Gb HD ubuntu 11.04 and fedora 15 running 'dmraid - ay' gives the following output. ERROR: via: invalid checksum on /dev/sdb ERROR: via: invalid checksum on /dev/sda no raid disks windows via v-raid tool shows no errors, array boots works fine in windows 7. Have rebuilt array several times to ensure metadata should not be corrupt. attached is dd of /dev/sda with metadata. Sorry, dumped 3000 sectors so a bit more than you need ;) Any assistance greatly appreciated, even if this is just my setup that is weird, I am happy to patch around it to get it working. I looked at the via.h and could not work out where to start :( As I said at start, if this is not the correct place then please inform me where is, and please accept my apologies. Regards David Thailand ____</pre> Bad Bod 2011-12-05T13:38:08 http://comments.gmane.org/gmane.linux.ataraid/2791 <pre>-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It has been a year since the last release, and I posted a series of patches back in march and they have been ignored and very little has been said on the mailing list since then ( nothing in the last 3 months ). Is this project still alive? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk7Zc0sACgkQJ4UciIs+XuJrSACgpgXPOWZinPLJEYI+Q0zYEAby IHQAnj+gUSwsyVVIMUg3uLQ97CpEK0Vr =E4fj -----END PGP SIGNATURE----- </pre> Phillip Susi 2011-12-03T00:54:42 http://comments.gmane.org/gmane.linux.ataraid/2787 <pre>Hello list, I recently acquired a system with an Intel 82801 SATA RAID controller. I'm using dmraid to manage an RAID1 1TB volume. I created 3 partitions on this RAID1 array, one of them being 875GB. When the system boots only the first two partitions appear in /dev/mapper/isw_xxx_p[1-2]. And, of course the volume group and logical volumes in the 3rd partition are nowhere to be found. After running 'partprobe' the 3rd partition appears, along with my logical volumes. If I remove the large 3rd partition and replace it with something in the neighborhood of a 300GB partition, it works just fine upon boot. I haven't figured out how large I can go before I hit this problem. This is a fully updated kubuntu 11.04 machine running 2.6.38-10-generic. dmraid version: 1.0.0.rc16 dmraid library version: 1.0.0.rc16 device-mapper version: 4.19.1 I poked around on the interwebs but couldn't find any info. Any help is greatly appreciated! -- Eric Schoeller University of Colorado Boulder Office of Information T</pre> Eric Schoeller 2011-07-21T02:00:57 http://comments.gmane.org/gmane.linux.ataraid/2785 <pre>I'm trying to help a user with a problem with their isw set. After upgrading to Ubuntu 11.04 ( 1.0.0.rc16 ) it seems that their partition extends beyond the end of the raid array. I'm looking at how isw computes the array length and it seems to be wrong. It looks like _cal_array_size() computes the length of the ( raid1 ) array by finding the smallest component disk and subtracting some reserved blocks. This does not seem to be correct. Relevant fields from the user's metadata: 0x0e8 disk[0].totalBlocks: 1953523055 0x118 disk[1].totalBlocks: 1953525168 0x148 isw_dev[0].SizeLow: 1953519616 0x1ac isw_dev[0].vol.map[0].blocks_per_member: 1953519880 0x1b0 isw_dev[0].vol.map[0].num_data_stripes: 7630936 0x1b4 isw_dev[0].vol.map[0].blocks_per_strip: 128 Further, it looks like create_rd() sets the size of each component disk to the same thing anyhow: if ((r-&gt;sectors = dev-&gt;vol.map[0].blocks_per_member - RAID_DS_JOURNAL)) This seems to have given the user a block device with a total size of 19535198</pre> Phillip Susi 2011-07-13T15:07:56 http://comments.gmane.org/gmane.linux.ataraid/2781 <pre>Hi, in Linux 2.6.38 the dmraid 4/5/6 module is included, so an external patch is no longer needed. I've compiled it directly into the kernel, so it should be available. Now I have a machine with Intel-fakeraid in raid5 configuration. When running "dmraid -ay" I get: ERROR: device-mapper target type "raid45" not in kernel This is with dmraid rc13, but with rc16 it's similar. Has the name of the module changed and if yes, what's the new name? Is there a tool to find out which modules are available? Or a sysfs entry? I'd like to patch dmraid rc13 so that it works with the new kernel, that would be enough for me, because it's on a specialized boot image. Hope I could make the problem understandable. Thanks, hjb </pre> Hans-Joachim Baader 2011-06-28T10:28:18 http://comments.gmane.org/gmane.linux.ataraid/2773 <pre>Hello list members: Please help me troubleshoot this problem I have with my Silicon Image RAID-1 set. I have two identical (same model) 500 GB Samsung hard disks and a Silicon Image SiI 3512 PCI SATA raid card. I have created a RAID-1 array in the card's BIOS. Unfortunately my OS can not recognize the raid set. # dmraid -s no raid disks # dmraid -r no raid disks Some information that might help: HPA is disabled on both of the Samsung hard disks, /dev/sdb and /dev/sdc: hdparm -N /dev/sdb /dev/sdb: max sectors = 976773168/976773168, HPA is disabled hdparm -N /dev/sdc /dev/sdc: max sectors = 976773168/976773168, HPA is disabled dmesg does not mention hpa or "host protected area" either. dmraid -s -dddd -vvvv gives: # dmraid -s -dddd -vvvv WARN: locking /var/lock/dmraid/.lock NOTICE: /dev/sdc: asr discovering NOTICE: /dev/sdc: ddf1 discovering NOTICE: /dev/sdc: hpt37x discovering NOTICE: /dev/sdc: hpt45x discovering NOTICE: /dev/sdc: isw discovering NOTICE: /dev/sdc: jmicron d</pre> Istvan Gabor 2011-06-05T10:38:34 http://comments.gmane.org/gmane.linux.ataraid/2761 <pre>Hello, I was doing a bit of experimenting with dmraid. What I have done is to create a raid0+1 array, and then physically pull one of the disks out. I then use the command "dmraid -n" to look at the metadata on the member disks. I notice that the member disk listed by the output that has the specific serial number of the disk that I pulled, whose status I expect to be different from the other disks listed, still has the same status as the other still physically plugged in. (i.e disk[0].status: 0x53a is shown for all of the disks, even the one that I pulled out). Is this normal? The following is the output of "dmraid -V": dmraid version: 1.0.0.rc16 (2009.09.16) shared dmraid library version: 1.0.0.rc16 (2009.09.16) device-mapper version: 4.13.0 Thanks for clarifying, Sandra _______________________________________________ Ataraid-list mailing list Ataraid-list&lt; at &gt;redhat.com https://www.redhat.com/mailman/listinfo/ataraid-list</pre> Sandra Escandor 2011-04-28T13:30:07 http://comments.gmane.org/gmane.linux.ataraid/2759 <pre>Hello list members: I am new on this list, but I have been using dmraid succesfully with my MB's nvidia nvraid. Very recently I acquired a SiI 3512 PCI SATA raid card. I created a RAID1 array on the card's BIOS using two hard disks of the same type (and size). The RAID array is recognized by the card's BIOS at boot. Unfortunately the raid array is not detected by my openSUSE 11.2 system: linux:~ # dmraid -s no raid disks linux:~ # dmraid -r no raid disks linux:~ # dmraid --version dmraid version: 1.0.0.rc16-3 (2010.01.12) dmraid library version: 1.0.0.rc16-3 (2010.01.12) device-mapper version: 4.15.0 linux:~ # linux:~ # ls -l /dev/mapper total 0 crw-rw---- 1 root root 10, 60 Apr 24 20:17 control linux:~ # These modules, including sata_sil modules are loaded (lsmod): dm_mod 84900 0 sata_sil 10088 0 My dmraid version is: linux:~ # dmraid --version dmraid version: 1.0.0.rc16-3 (2010.01.12) dmraid library version: 1.0.0.rc16-3 (2010.01.12) device-mapper version: 4</pre> Istvan Gabor 2011-04-27T20:34:42 http://comments.gmane.org/gmane.linux.ataraid/2755 <pre>Hello all, I know that the man page for dmraid doesn't mention this, but I just wanted to make sure: is it true to say that raid status from dmraid is not written into either procfs or sysfs, much like the way mdraid does it? Thanks for your clarification, Sandra _______________________________________________ Ataraid-list mailing list Ataraid-list&lt; at &gt;redhat.com https://www.redhat.com/mailman/listinfo/ataraid-list</pre> Sandra Escandor 2011-04-25T12:57:50 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.ataraid