On Mon, Sep 04, 2006 at 01:55:52PM -0400, Bill Davidsen wrote:
Doug Ledford wrote:
It's the mount program collecting possible LABEL= data on the partitions
listed in /proc/partitions, of which sde3 is outside the valid range for
the drive.
May I belatedly say that this is sort-of a kernel issue, since
/proc/partitions reflects invalid data? Perhaps a boot option like
nopart=sda,sdb or similar would be in order?
i would move partition detection code to user space completely, so it
could be ran selectively on the drives that do happen to have a patition
table.
a compromise could be having mdadm (or the script that starts mdadm at
boot time, issue an ioctl(fd,BLKPG,...) to make kernel forget about any
eventual partition table it might have misdetected
L.
--
Luca Berra -- [EMAIL PROTECTED]
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 [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
