Re: Problems with mounting filesystems from /dev/hdb (kernel 2.6.18.1)

[Oliver Brakmann]

[ sorry if the CC line isn't intact. I'm reading via Gmane, and though
  they keep the CC line, the To: line just gets turned into the
  newsgroups: line, so I almost never see all recipients :-/ ]

Hi,

On Wed, 2006-11-08 22:09, Jano wrote...
> +Adding 1028120k swap on /dev/hda7.  Priority:-1 extents:1 across:1028120k
> +EXT3 FS on hda3, internal journal

This is S20checkroot.sh running...

> +md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
> +md: bitmap version 4.39

This is S25mdadm-raid.

> +device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@xxxxxxxxxx
> +device-mapper: table: 253:0: linear: dm-linear: Device lookup failed
> +device-mapper: ioctl: error adding target to table

At this point, it looks like something already grabbed hold of /dev/hdb.
Both evms and lvm get started here, right after S25mdadm-raid.

This is just a hunch, but you might try disabling either of the two.
Also, it might help if you'd post the output of 'fdisk -l /dev/hdb' to
see what's on it.  The output of 'pvs' might help, too.

I have no clue why this error only shows up with the vanilla kernel and
not with the Ubuntu one, though :-/

Bye,
Oliver
-- 
It's practically impossible to look at a   /\   #198843 @ http://counter.li.org
penguin and feel angry.     -- Joe Moore   \/

NP: Apoptygma Berzerk - Until the end of the world
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/