* raid subsystem broken in 2.5.43... blockdev changes?
@ 2002-10-16 16:02 David Mansfield
2002-10-17 17:45 ` Alexander Viro
0 siblings, 1 reply; 2+ messages in thread
From: David Mansfield @ 2002-10-16 16:02 UTC (permalink / raw)
To: Alexander Viro, linux-kernel
Hi Al, list,
I think the latest blockdev (maybe the do_open) changes broke the raid
subsystem. In order to 'activate' a raid device, the userland tools open
the device node (e.g. /dev/md0) to perform ioctls against it, even though
that device isn't up and running yet. In 2.5.43 it returns ENXIO.
In 2.5.42 we used to get through to bdev->bd_op->open() without a
'gendisk' structure, but now we bail with ENXIO. Is this the pertinent
difference?
David
--
/==============================\
| David Mansfield |
| david@cobite.com |
\==============================/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: raid subsystem broken in 2.5.43... blockdev changes?
2002-10-16 16:02 raid subsystem broken in 2.5.43... blockdev changes? David Mansfield
@ 2002-10-17 17:45 ` Alexander Viro
0 siblings, 0 replies; 2+ messages in thread
From: Alexander Viro @ 2002-10-17 17:45 UTC (permalink / raw)
To: David Mansfield; +Cc: linux-kernel
On Wed, 16 Oct 2002, David Mansfield wrote:
>
> Hi Al, list,
>
> I think the latest blockdev (maybe the do_open) changes broke the raid
> subsystem. In order to 'activate' a raid device, the userland tools open
> the device node (e.g. /dev/md0) to perform ioctls against it, even though
> that device isn't up and running yet. In 2.5.43 it returns ENXIO.
I know, patches that handle that are coming to Linus in an hour.
... going net.dead for two days didn't help any ;-/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-10-17 17:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-10-16 16:02 raid subsystem broken in 2.5.43... blockdev changes? David Mansfield
2002-10-17 17:45 ` Alexander Viro
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®