headers
dean gaudet | 1 Nov 2005 01:37

Re: s/w raid and bios renumbering HDs


On Mon, 31 Oct 2005, Hari Bhaskaran wrote:

> So that "DEVICE paritions" line was really supposed to be there? Hehe... I
> thought it was just a
> help message and replaced it with "DEVICE /dev/hda1 /dev/hdc1" :)

you can use "DEVICE /dev/hda1 /dev/hdc1" ... but then mdadm scans will 
only consider those two partitions... if you use "DEVICE partitions" it'll 
look at all detected partitions for the components.  it makes it easy when 
you move disks around to new controllers and their location changes, 
things will continue to jfw.

> If I ever end up in a situation with a non-root raid down (say I did --stop),
> how do I start it back up? (--run seems
> to give me some errors). Anyways, more "rtfm" to do.

you want --assemble ...

> > the root is the only one which you need to be careful with -- when debian
> > installs your kernel it constructs an initrd which lists the minimum places
> > it will search for the root raid components... for example on one of my
> > boxes:
> > 
> > # mkdir /mnt/cramfs
> > # mount -o ro,loop /boot/initrd.img-2.6.13-1-686-smp /mnt/cramfs
> > # cat /mnt/cramfs/script
> > ROOT=/dev/md3
> > mdadm -A /dev/md3 -R -u 2b3a5b77:c7b4ab81:a2b8322a:db5c4e88 /dev/sdb4
> > /dev/sda4
(Continue reading)

Permalink | Reply | 0 comments |
headers
news | 1 Nov 2005 04:37

Immediate Radar Alert

The Solvis Group Strategic Alliance Agreement With SSL Expected 
to Provide $25 Million in Additional Revenues in 90 Days 

Immediate Radar Alert
The Solvis Group Inc. **SLVG**
The Solvis Group is a subsidiary of Dalrada Financial Corporation 

0.07 <-- ridiculous in our opinion 
Ride this wave starting Now 

Why you ask?  Let's start right here. Recent news releases...
Talk about flying under the radar?  Isn't that what we look for? 

Recent News Headlines!  No dreaming here! 
The Solvis Group Strategic Alliance Agreement With SSL Expected 
to Provide $25 Million in Additional Revenues in 90 Days 
The agreement calls for SSL to refer a minimum of $25 million in business 
to The Solvis Group within the next 90 days. The alliance has already generated 
more than $7.5 million in new business, on an annualized basis. 

The Solvis Group, Formerly Quik Pix Inc., Announces Sale of Subsidiary 
to Global Food Technologies James Bouskos, Chairman and CEO of Global Food Technologies 
said that "our company is pleased to report that our transaction with The Solvis Group 
for the acquisition of Boulevard Acquisition Corporation, the publicly-reporting shell 
and wholly owned subsidiary of The Solvis Group, has closed. 

The Solvis Group Launches 'Benefits Bank' Program to Bring Employees at All Compensation 
Levels Key Benefits  "The Benefits Bank represents a comprehensive response 
by The Solvis Group to address the needs of employees at all compensation levels 
to participate in benefits generally available only to large corporations,"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ming Zhang | 1 Nov 2005 17:02
Picon
Favicon

raid0 fail to detect drive failure

Hi folks

I have a raid0 on top of 2 sata disk sda and sdb. after i hot unplug
sda, the raid0 still shows online and active. run dd to write to it will
fail and dmesg shows scsi io error. but /proc/mdstat shows everything is
ok.

checked 2.4.27 and 2.6.11.2, both show same problem.

mdadm is 1.8

any hint?

Ming

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 2 comments |
headers
Meik Nienaber | 1 Nov 2005 17:13

raid5 two disk failure

Hi,

The story:

- raid5 set with four disks
- after power outage two disks were marked faulty
- reassembled the set with 3 disks (1,2,3)
- added the forth disk
- reconstruction of the set failed because of an uncorrectable sector of disk 3
- tried to reassemble the set with disk 1,2,4. Not possible because disk 4 is in
spare mode.

Any opportunities to get the set back with disks 1,2,4? Thanks in advance for 
your help.

mdadm v1.9.0
linux 2.6.12.3

Cheers
Meik

-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 1 comment |
headers
E-gold | 2 Nov 2005 05:02
Favicon

E-gold security connect

--------------------------------------------------
 * * * Read/Save/Print this email message * * *
--------------------------------------------------

Dear e-gold payment system user,

The recent cases of fraud, unauthorized withdrawal of cash from our clients' accounts and recurred
attempts of hackers to access our server forced us to implement a new security system. The special program
will ensure safe connection of your computer to our server by means of a unique encoded key, specially
generated for each account. Only the combination of your login, password and the key will allow you to
access the system. The program is enclosed to the message and doesn't need any installation. By one click
you will be connected to the server and the program will generate the key. After that you will enter your
account from Internet Explorer, which is absolutely safe. You will be signed out of the program
automatically after closing the window. See the detailed operational instruction enclosed to the
program. 

We have to warn you, that if you want to be the user of our system in future, you'll have to accept our rules and
to use this program. Otherwise please call the numbers below to withdraw your funds. For the detailed
information please enter our site or use our hot line to contact us by phone.

Our Contacts:

Phone (Worldwide)  	+1 321-957-1200
FAX (Worldwide) 	+1 321-952-0790

---------------------------------------------
 Thank you for using e-gold!
---------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
info | 2 Nov 2005 05:43

DS4000 Storage Server (Engenio based) Management Protocol Analyzer

Dswrench.com announces a new debugging tool for the "DS4000 storage server (Engenio based disk storage
array)." We are proud to introduce the DS4000 Management Protocol Analyzer, or DSMPA. DSMPA is freeware
built by engineers for engineers, so we encourage you to use often and spread the word!

What it does:
DSPMA captures management network traffic between SANtricity or other management software and disk
storage arrays. It assembles network packets into DS4000 management objects. The captured objects can
be viewed graphically and played back. It is a powerful tool for DS4000 storage server support center,
storage administrators, storage management software developers and quality assurance engineers. 

To view sample shots of DSMPA capabilities, click the following links:
-To access the User guide, please click http://www.dswrench.com/documents/dsmpa.pdf.
-To access the DSMPA main screen, please click
http://www.dswrench.com/documents/CaptureAndView.html

-DSMPA can save a communication session to html file. To view a sample session output, please click http://www.dswrench.com/documents/session_sample.html.
-DSMPA also captures SANtricity generated network traffic. This page
(http://www.dswrench.com/documents/snmp_sample.html) shows captured SNMP trap fired by the
SANtricity management software.

How to get it:
DSMPA is now available for free download from http://www.dswrench.com

For more information, please visit http://www.dswrench.com. 

Thank you for taking a few minutes to improve the operation of your DS4000 storage server. Please visit
dswrench.com often for updates and new software. Use often and spread the word!

Best Regards,
The Dswrench.com Team
(Continue reading)

Permalink | Reply | 0 comments |
headers
Michael Tokarev | 2 Nov 2005 10:08
Picon

Re: raid0 fail to detect drive failure

Ming Zhang wrote:
> Hi folks
> 
> I have a raid0 on top of 2 sata disk sda and sdb. after i hot unplug
> sda, the raid0 still shows online and active. run dd to write to it will
> fail and dmesg shows scsi io error. but /proc/mdstat shows everything is
> ok.

Since raid0 isn't relly raid (as Redundrand) and can't really do
anything with IO errors on component devices, this behaviour
(returning IO errors to the application) is the only sane way
to go.  It should not fail just like when your disk drive has
a bad sector on it, the whole partition (or whole disk) with
that bad sector isn't "marked as failed".  So what you see is
exactly correct behaviour, in my opinion anyway.

/mjt
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 1 comment |
headers
NeilBrown | 2 Nov 2005 11:14
X-Face
Picon
Gravatar

[PATCH md 001 of 10] Make sure /block link in /sys/.../md/ goes to correct devices.


If a block_device is a partition, then it's kobject is
  bdev->bd_part->kobj
otherwise (if it is a full device), the kobject is 
  bdev->bd_disk->kobj

As md wants back-links to the correct object (whether partition or
not), we need to respect this difference...
(Thus current code shows a link to the whole device, whether we are
using a partition or not, which is wrong).

Signed-off-by: Neil Brown <neilb <at> suse.de>

### Diffstat output
 ./drivers/md/md.c |    7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff ./drivers/md/md.c~current~ ./drivers/md/md.c
--- ./drivers/md/md.c~current~	2005-11-02 17:32:28.000000000 +1100
+++ ./drivers/md/md.c	2005-11-02 17:32:41.000000000 +1100
 <at>  <at>  -1182,6 +1182,7  <at>  <at>  static int bind_rdev_to_array(mdk_rdev_t
 {
 	mdk_rdev_t *same_pdev;
 	char b[BDEVNAME_SIZE], b2[BDEVNAME_SIZE];
+	struct kobject *ko;

 	if (rdev->mddev) {
 		MD_BUG();
 <at>  <at>  -1221,7 +1222,11  <at>  <at>  static int bind_rdev_to_array(mdk_rdev_t
 	rdev->kobj.parent = &mddev->kobj;
(Continue reading)

Permalink | Reply | 1 comment |
headers
NeilBrown | 2 Nov 2005 11:15
X-Face
Picon
Gravatar

[PATCH md 009 of 10] Improve 'scan_mode' and rename it to 'sync_action'


The current sync_action for an array can be one of 

   idle  - nothing happening
   resync - reduncancy being recalcualted
   recover - missing device being recoverred to spare
   check   - user initiated check of redundancy
   repair  - like resync but user-initiated and ignores 
             bitmap optimisation.

Each of these strings can also be written to the 'sync_action'
file to cause that action to happen (if appropriate).

While 'sync' is not technically correct, as a recovery is *not* a 
'sync', I think it is the most servicable word here.  Also
'action' is a strong word than 'mode'.

Signed-off-by: Neil Brown <neilb <at> suse.de>

### Diffstat output
 ./drivers/md/md.c |   48 +++++++++++++++++++++++++++++-------------------
 1 file changed, 29 insertions(+), 19 deletions(-)

diff ./drivers/md/md.c~current~ ./drivers/md/md.c
--- ./drivers/md/md.c~current~	2005-11-02 17:33:34.000000000 +1100
+++ ./drivers/md/md.c	2005-11-02 17:33:35.000000000 +1100
 <at>  <at>  -1746,9 +1746,9  <at>  <at>  raid_disks_show(mddev_t *mddev, char *pa
 static struct md_sysfs_entry md_raid_disks = __ATTR_RO(raid_disks);

 static ssize_t
(Continue reading)

Permalink | Reply | 1 comment |
headers
NeilBrown | 2 Nov 2005 11:15
X-Face
Picon
Gravatar

[PATCH md 003 of 10] Make sure a user-request sync of raid5 ignores intent bitmap


A sync of raid5 usually ignore blocks which the bitmap says are in-sync.
But a user-request check or repair should not ignore these.

Signed-off-by: Neil Brown <neilb <at> suse.de>

### Diffstat output
 ./drivers/md/raid5.c |    1 +
 1 file changed, 1 insertion(+)

diff ./drivers/md/raid5.c~current~ ./drivers/md/raid5.c
--- ./drivers/md/raid5.c~current~	2005-11-02 17:32:28.000000000 +1100
+++ ./drivers/md/raid5.c	2005-11-02 17:32:57.000000000 +1100
 <at>  <at>  -1649,6 +1649,7  <at>  <at>  static sector_t sync_request(mddev_t *md
 		return rv;
 	}
 	if (!bitmap_start_sync(mddev->bitmap, sector_nr, &sync_blocks, 1) &&
+	    !test_bit(MD_RECOVERY_REQUESTED, &mddev->recovery) &&
 	    !conf->fullsync && sync_blocks >= STRIPE_SECTORS) {
 		/* we can skip this block, and probably more */
 		sync_blocks /= STRIPE_SECTORS;
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |

Gmane