Just built a new FC6 machine, with 5x 320Gb drives and 1x 300Gb drive. Made a 300Gb partition on all the drives /dev/hd{c,d,e} and /dev/sd{a,b,c}... Trying to create an array gave me an error, since it thought there was already an array on some of the disks (and there was an old one).

I decided to clear off the superblock on the drives with mdadm --zero-superblock on all the drives. It worked fine on all drives, except for /dev/sd{b,c)1, which returns an error "mdadm: Couldn't open /dev/sdb1 for write - not zeroing". There doesn't seem to be a problem with the drive, as I've run a non destructive badblocks on it, and also done a dd if=/dev/zero of=/dev/sdb1 on it, and Ive written out 300Gb onto the partition.

When I try and create an array using these 2 partitions, I get an error

mdadm: Cannot open /dev/sdb1: Device or resource busy
mdadm: Cannot open /dev/sdc1: Device or resource busy

and it aborts. I've double checked that the drives aren't mounted anywhere. There's nothing in /var/log/messages either...

Any suggestions where to check next?



Graham



___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
-
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

On Sun, 25 Feb 2007, jahammonds prost wrote:

> Just built a new FC6 machine, with 5x 320Gb drives and 1x 300Gb drive. Made a 300Gb partition on all the drives /dev/hd{c,d,e} and /dev/sd{a,b,c}... Trying to create an array gave me an error, since it thought there was already an array on some of the disks (and there was an old one).
>
> I decided to clear off the superblock on the drives with mdadm --zero-superblock on all the drives. It worked fine on all drives, except for /dev/sd{b,c)1, which returns an error "mdadm: Couldn't open /dev/sdb1 for write - not zeroing". There doesn't seem to be a problem with the drive, as I've run a non destructive badblocks on it, and also done a dd if=/dev/zero of=/dev/sdb1 on it, and Ive written out 300Gb onto the partition.
>
> When I try and create an array using these 2 partitions, I get an error
>
> mdadm: Cannot open /dev/sdb1: Device or resource busy
> mdadm: Cannot open /dev/sdc1: Device or resource busy
>
> and it aborts. I've double checked that the drives aren't mounted anywhere. There's nothing in /var/log/messages either...
>
> Any suggestions where to check next?
>
>
>
> Graham
>
>
>
> ___________________________________________________________
> To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
> -
> 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
>

Do you have an active md array?

mdadm -S /dev/md0
mdadm -S /dev/md1
mdadm -S /dev/md2

... etc

lsof | egrep '(sdb|sdc)'

Something thinks its in use, that is why you cannot format it/make it part
of a new array, a reboot would also fix the problem.

Justin.
-
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

> Do you have an active md array?
>
> mdadm -S /dev/md0

Nothing was showing up in /proc/mdstat, but when I try and stop md0, I get this

# mdadm -S /dev/md0
mdadm: stopped /dev/md0

> lsof | egrep '(sdb|sdc)'

I had tried that before, and nothing is showing. A reboot didn't help, but something is definately keeping it open. I tried an mkfs

]# mkfs.ext3 /dev/sdb1
mke2fs 1.39 (29-May-2006)
/dev/sdb1 is apparently in use by the system; will not make a filesystem here!


Any ideas how to find out what has it open? I can happily write all over the disk with dd... I can create and delete the partition, and it's all good... I will try deleting the sd{b,c}1 partitions, reboot, and see what happens.


Graham




----- Original Message ----
From: Justin Piszcz <jpiszcz [at] lucidpixels.com>
To: jahammonds prost <gmitch64 [at] yahoo.com>
Cc: linux-raid [at] vger.kernel.org
Sent: Sunday, 25 February, 2007 5:35:33 PM
Subject: Re: trouble creating array


On Sun, 25 Feb 2007, jahammonds prost wrote:

> Just built a new FC6 machine, with 5x 320Gb drives and 1x 300Gb drive. Made a 300Gb partition on all the drives /dev/hd{c,d,e} and /dev/sd{a,b,c}... Trying to create an array gave me an error, since it thought there was already an array on some of the disks (and there was an old one).
>
> I decided to clear off the superblock on the drives with mdadm --zero-superblock on all the drives. It worked fine on all drives, except for /dev/sd{b,c)1, which returns an error "mdadm: Couldn't open /dev/sdb1 for write - not zeroing". There doesn't seem to be a problem with the drive, as I've run a non destructive badblocks on it, and also done a dd if=/dev/zero of=/dev/sdb1 on it, and Ive written out 300Gb onto the partition.
>
> When I try and create an array using these 2 partitions, I get an error
>
> mdadm: Cannot open /dev/sdb1: Device or resource busy
> mdadm: Cannot open /dev/sdc1: Device or resource busy
>
> and it aborts. I've double checked that the drives aren't mounted anywhere. There's nothing in /var/log/messages either...
>
> Any suggestions where to check next?
>
>
>
> Graham
>
>
>
> ___________________________________________________________
> To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
> -
> 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
>

Do you have an active md array?

mdadm -S /dev/md0
mdadm -S /dev/md1
mdadm -S /dev/md2

... etc

lsof | egrep '(sdb|sdc)'

Something thinks its in use, that is why you cannot format it/make it part
of a new array, a reboot would also fix the problem.

Justin.



___________________________________________________________
To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com
-
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

> Any ideas how to find out what has it open? I can happily write all over

I think I've heard of other cases like this where it's lvm that's
glommed onto the partition. I don't use lvm, but perhaps 'lvdisplay'?
-
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

I hadn't thought of that, but it doesn't seem to be it...

# pvs
PV VG Fmt Attr PSize PFree
/dev/hda2 VolGroup00 lvm2 a- 18.97G 32.00M

=46C6 created that for my / and /boot and swap... Thanks for the sugges=
tion tho - something I had not considered.


Graham


----- Original Message ----
=46rom: Mark Hahn <hahn [at] mcmaster.ca>
To: jahammonds prost <gmitch64 [at] yahoo.com>
Cc: linux-raid [at] vger.kernel.org
Sent: Sunday, 25 February, 2007 10:01:06 PM
Subject: Re: trouble creating array


> Any ideas how to find out what has it open? I can happily write all o=
ver

I think I've heard of other cases like this where it's lvm that's
glommed onto the partition. I don't use lvm, but perhaps 'lvdisplay'?


=09
___________________________________________________________= 20
All New Yahoo! Mail =96 Tired of unwanted email come-ons? Let our SpamG=
uard protect you. http://uk.docs.yahoo.com/nowyoucan.html
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" i=
n
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

On Sunday February 25, gmitch64 [at] yahoo.com wrote:
>
>
> Any ideas how to find out what has it open? I can happily write all over the disk with dd... I can create and delete the partition, and it's all good... I will try deleting the sd{b,c}1 partitions, reboot, and see what happens.
>

ls -l /sys/block/*/holders/* ??

NeilBrown
-
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

Ah ha....

# ls -l /sys/block/*/holders/*
lrwxrwxrwx 1 root root 0 Feb 26 06:28 /sys/block/sdb/holders/dm-0 -> ../../../block/dm-0
lrwxrwxrwx 1 root root 0 Feb 26 06:28 /sys/block/sdc/holders/dm-0 -> ../../../block/dm-0

which I am assuming is dmraid? I did a quick check, and

# dmraid -r
No RAID disks

Doesn't look like there is anything defined. I know that both sdb and sdc (as well as sda) are connected to SATA cards which support RAID under windows... However, I know there is no arrays defined on them on the cards (at least not by me)... I will bounce the server again and check.


Graham



----- Original Message ----
From: Neil Brown <neilb [at] suse.de>
To: jahammonds prost <gmitch64 [at] yahoo.com>
Cc: Justin Piszcz <jpiszcz [at] lucidpixels.com>; linux-raid [at] vger.kernel.org
Sent: Sunday, 25 February, 2007 11:40:26 PM
Subject: Re: trouble creating array


On Sunday February 25, gmitch64 [at] yahoo.com wrote:
>
>
> Any ideas how to find out what has it open? I can happily write all over the disk with dd... I can create and delete the partition, and it's all good... I will try deleting the sd{b,c}1 partitions, reboot, and see what happens.
>

ls -l /sys/block/*/holders/* ??

NeilBrown



___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
-
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

Rebooted and checked that there were no arrays defined. I have 2 cards in the server - one is a VIA based card, with a single Maxtor, the other this a Promise based card, with 2 Maxtors by Seagate on it. I've been into the config utilites on both cards, and none of them have arrays defined on them.

----- Original Message ----
From: Neil Brown <neilb [at] suse.de>
To: jahammonds prost <gmitch64 [at] yahoo.com>
Cc: Justin Piszcz <jpiszcz [at] lucidpixels.com>; linux-raid [at] vger.kernel.org
Sent: Sunday, 25 February, 2007 11:40:26 PM
Subject: Re: trouble creating array


On Sunday February 25, gmitch64 [at] yahoo.com wrote:
>
>
> Any ideas how to find out what has it open? I can happily write all over the disk with dd... I can create and delete the partition, and it's all good... I will try deleting the sd{b,c}1 partitions, reboot, and see what happens.
>

ls -l /sys/block/*/holders/* ??

NeilBrown



___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
-
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

On Mon, Feb 26, 2007 at 03:40:32AM -0800, jahammonds prost wrote:
>Ah ha....
>
># ls -l /sys/block/*/holders/*
>lrwxrwxrwx 1 root root 0 Feb 26 06:28 /sys/block/sdb/holders/dm-0 -> ../../../block/dm-0
>lrwxrwxrwx 1 root root 0 Feb 26 06:28 /sys/block/sdc/holders/dm-0 -> ../../../block/dm-0
>
>which I am assuming is dmraid? I did a quick check, and

no, it is device-mapper

># dmraid -r
>No RAID disks
>
use "dmsetup ls"

L.

--
Luca Berra -- bluca [at] comedia.it
Communication Media & Services S.r.l.
/"\
\ / ASCII RIBBON CAMPAIGN
X AGAINST HTML MAIL
/ \
-
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

Hello,

Can someone point me to where I can search a linux-raid mailing list
archive?

I am looking for information about where things are going with DMRAID
features and any discussion on where things stand in regards to the
possibility of merging MD and DMRAID. My guess, from what I have found
in google, is that this was a heated discussion. Mainly I am looking at
what direction people think is correct for getting more functionality to
support "fakeraid" volumes.

I appreciate any information!

Thanks,

Jason
-
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

On 2/27/07, Gaston, Jason D <jason.d.gaston [at] intel.com> wrote:
> Hello,
>
> Can someone point me to where I can search a linux-raid mailing list
> archive?
>
I use:
http://marc.theaimsgroup.com/?l=linux-raid&r=1&w=2

> I am looking for information about where things are going with DMRAID
> features and any discussion on where things stand in regards to the
> possibility of merging MD and DMRAID. My guess, from what I have found
> in google, is that this was a heated discussion. Mainly I am looking at
> what direction people think is correct for getting more functionality to
> support "fakeraid" volumes.
>
Also interesting is the discussion around surrounding the proposed EMD solution.

> I appreciate any information!
>
> Thanks,
>
> Jason
> -

Regards,
Dan
-
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

Just an update for everyone on this (and for the archives), Did some digging, and had a look at the device mapper config

# dmsetup -C info

Name Maj Min Stat Open Targ Event UUID
mpath0 253 0 L--w 1 1 0
VolGroup00-LogVol01 253 3 L--w 1 1 0 LVM-2sahQifzg9s9k0xSkpnzpGCYd7JNVXzUof6XmQ0fhzJ6jIbQLciAbm6l JLwK0Aex
VolGroup00-LogVol00 253 2 L--w 1 1 0 LVM-2sahQifzg9s9k0xSkpnzpGCYd7JNVXzUt3sJ3nwvJF8cr6ebv5AdnY0j 4Ajl6U0I
mpath0p1 253 1 L--w 0 1 0


Those 2 multipath devices shouldn't have been there, and indeed mpath0p1 were my 2 recalcitrant disks.

# dmsetup -C remove mpath0p1
# dmsetup -C remove mpath0

And they were both gone (you need to start at the bottom of the tree when removing them).

A quick fdisk of my disks to create sdb1 and sdc1 partitions, and my array will be synched in 204 mins...:)

Thanks to everyones help for pointing me in the right direction.. It was a trip I would have preferred not to have made, but like all trips like that, it's been illuminating.

Thanks again.


Graham



----- Original Message ----
From: Neil Brown <neilb [at] suse.de>
To: jahammonds prost <gmitch64 [at] yahoo.com>
Cc: Justin Piszcz <jpiszcz [at] lucidpixels.com>; linux-raid [at] vger.kernel.org
Sent: Sunday, 25 February, 2007 11:40:26 PM
Subject: Re: trouble creating array


On Sunday February 25, gmitch64 [at] yahoo.com wrote:
>
>
> Any ideas how to find out what has it open? I can happily write all over the disk with dd... I can create and delete the partition, and it's all good... I will try deleting the sd{b,c}1 partitions, reboot, and see what happens.
>

ls -l /sys/block/*/holders/* ??

NeilBrown





___________________________________________________________
New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at the Yahoo! Mail Championships. Plus: play games and win prizes.
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk
-
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

So anyways, I created my RAID device, and waited about 4 hours for it to sync, and all was happy with the world, so I went to bed. This morning, I made an ext3 file system on it, set up some directories, set the acls, added to my smb.conf file, mapped a drive, and after about 4Gb copied onto it, I got an error. Checking in the logs, there was an error about trying to access past the physical extent.

I did a quick check of mdstat, and one of the array disks was down, and an dm device had shown up in the array configuration. A quick dmsetup -C info again shows that mpath0p1 has returned again.

Does anyone know why it keeps appearing, and more importantly, is there any way of persuading it not to...?

Thanks again for any help and pointers people can give...


Graham


----- Original Message ----
From: jahammonds prost <gmitch64 [at] yahoo.com>
To: Neil Brown <neilb [at] suse.de>
Cc: Justin Piszcz <jpiszcz [at] lucidpixels.com>; linux-raid [at] vger.kernel.org
Sent: Tuesday, 27 February, 2007 8:10:36 PM
Subject: Re: trouble creating array


Just an update for everyone on this (and for the archives), Did some digging, and had a look at the device mapper config

# dmsetup -C info

Name Maj Min Stat Open Targ Event UUID
mpath0 253 0 L--w 1 1 0
VolGroup00-LogVol01 253 3 L--w 1 1 0 LVM-2sahQifzg9s9k0xSkpnzpGCYd7JNVXzUof6XmQ0fhzJ6jIbQLciAbm6l JLwK0Aex
VolGroup00-LogVol00 253 2 L--w 1 1 0 LVM-2sahQifzg9s9k0xSkpnzpGCYd7JNVXzUt3sJ3nwvJF8cr6ebv5AdnY0j 4Ajl6U0I
mpath0p1 253 1 L--w 0 1 0


Those 2 multipath devices shouldn't have been there, and indeed mpath0p1 were my 2 recalcitrant disks.

# dmsetup -C remove mpath0p1
# dmsetup -C remove mpath0

And they were both gone (you need to start at the bottom of the tree when removing them).

A quick fdisk of my disks to create sdb1 and sdc1 partitions, and my array will be synched in 204 mins...:)

Thanks to everyones help for pointing me in the right direction.. It was a trip I would have preferred not to have made, but like all trips like that, it's been illuminating.

Thanks again.


Graham



----- Original Message ----
From: Neil Brown <neilb [at] suse.de>
To: jahammonds prost <gmitch64 [at] yahoo.com>
Cc: Justin Piszcz <jpiszcz [at] lucidpixels.com>; linux-raid [at] vger.kernel.org
Sent: Sunday, 25 February, 2007 11:40:26 PM
Subject: Re: trouble creating array


On Sunday February 25, gmitch64 [at] yahoo.com wrote:
>
>
> Any ideas how to find out what has it open? I can happily write all over the disk with dd... I can create and delete the partition, and it's all good... I will try deleting the sd{b,c}1 partitions, reboot, and see what happens.
>

ls -l /sys/block/*/holders/* ??

NeilBrown





___________________________________________________________
New Yahoo! Mail is the ultimate force in competitive emailing. Find out more at the Yahoo! Mail Championships. Plus: play games and win prizes.
http://uk.rd.yahoo.com/evt=44106/*http://mail.yahoo.net/uk
-
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



___________________________________________________________
Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html
-
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

Thanks for the archive link, very interesting discussions with EMD...

What was the final outcome with EMD? Is it still a valid project?

We would like to start helping with RAID feature enhancements, but we
need to maintain support vendor specific metadata. What is the best way
to approach this? Pick up EMD again, add to DMRAID, add to MD RAID or
something else? We want to do the right thing by the community. Can
anyone point me in the right direction with where to begin?

Thank you,

Jason



>-----Original Message-----
>From: dan.j.williams [at] gmail.com [mailto:dan.j.williams [at] gmail.com] On
Behalf
>Of Dan Williams
>Sent: Tuesday, February 27, 2007 2:54 PM
>To: Gaston, Jason D
>Cc: linux-raid [at] vger.kernel.org
>Subject: Re: DMRAID feature direction?
>
>On 2/27/07, Gaston, Jason D <jason.d.gaston [at] intel.com> wrote:
>> Hello,
>>
>> Can someone point me to where I can search a linux-raid mailing list
>> archive?
>>
>I use:
>http://marc.theaimsgroup.com/?l=linux-raid&r=1&w=2
>
>> I am looking for information about where things are going with DMRAID
>> features and any discussion on where things stand in regards to the
>> possibility of merging MD and DMRAID. My guess, from what I have
found
>> in google, is that this was a heated discussion. Mainly I am looking
at
>> what direction people think is correct for getting more functionality
to
>> support "fakeraid" volumes.
>>
>Also interesting is the discussion around surrounding the proposed EMD
>solution.
>
>> I appreciate any information!
>>
>> Thanks,
>>
>> Jason
>> -
>
>Regards,
>Dan
-
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

On Wednesday February 28, jason.d.gaston [at] intel.com wrote:
> Thanks for the archive link, very interesting discussions with EMD...
>
> What was the final outcome with EMD? Is it still a valid project?
>
> We would like to start helping with RAID feature enhancements, but we
> need to maintain support vendor specific metadata. What is the best way
> to approach this? Pick up EMD again, add to DMRAID, add to MD RAID or
> something else? We want to do the right thing by the community. Can
> anyone point me in the right direction with where to begin?

I'm keen on making md/raid work with vendor-specific metadata. I aim
to achieve that by making it possible to do all the metadata handling
in userspace, and then maybe support loadable modules in mdadm for
different specific metadata.

I've been aiming to get DDF supported, but things keep distracting me
:-(

I only vaguely remember the EMD effort. My memory is that a pile of
code appeared that did a variety of useful things, but there were lots
of aspects that I wasn't comfortable with. i.e. it needed a bit of
revision before it was suitable for mainline, but there was no
followup from the coders.

I would suggest that the "right thing by the community" is to present
some details on what specifically you want to achieve and start a
discussion on how best to achieve that. Then see where things lead.

For raid1/4/5/6, I would strongly recommend starting with the md
code-base. If it seems like a good idea to put a 'dm' interface on
top of that, then it could probably be arranged. If more
functionality is needed internally, or better interfaces needed to
achieve particular ends, then that is certainly possible to.

NeilBrown
-
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