Mailinglist Archive: opensuse-factory (279 mails)
| < Previous | Next > |
Re: [opensuse-factory] kpartx -d / activate_device_mapper -d
- From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
- Date: Tue, 3 Mar 2009 03:25:54 +0100 (CET)
- Message-id: <alpine.LSU.2.00.0903030322550.800@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday, 2009-03-02 at 17:14 -0500, Felix Miata wrote:
I have no idea, but you could test renaming those modules, so that they can not be loaded. The blacklist does not work if another module explicitly wants to load a blacklisted module.
At least you should get an error, and that error might point to what wants to load them :-?
Another idea. How about checking your fstab does refer to /dev/sdX?
- -- Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkmslTgACgkQtTMYHG2NR9VOcACghTrFu49tFgjXY1j7dd3VnU7S
8jYAn3Wo5OedX4fngRQqANgBcCo2OV3g
=rJOn
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
Hash: SHA1
On Monday, 2009-03-02 at 17:14 -0500, Felix Miata wrote:
During 11.1 devel via https://bugzilla.novell.com/show_bug.cgi?id=397816 I
setup device mapper on one system in order to access all actual partitions
while using ata_piix driver. Now on that system I have a 2.6.29 kernel, so no
longer need dm_linear. So far, I've had no luck reversing the process.
Neither subject command seems to produce any impact. I ran both kpartx -d
/dev/sda and activate_device_mapper -d /dev/sda before running mkinitrd, and
still the resulting initrd features dm_linear and kpartx.
/etc/udev/rules.d/dm_linear.rules did get a fresh write, while
/etc/udev/rules.d/70-kpartx.rules did not. I blacklisted dm_linear & kpartx
in /etc/modprobe.conf.local too, but that didn't help either. Short of a
fresh install, how do I eliminate them, and go back to mounting directly to
/dev/sda* devices instead of /dev/dm-* devices?
Ping.
I have no idea, but you could test renaming those modules, so that they can not be loaded. The blacklist does not work if another module explicitly wants to load a blacklisted module.
At least you should get an error, and that error might point to what wants to load them :-?
Another idea. How about checking your fstab does refer to /dev/sdX?
- -- Cheers,
Carlos E. R.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
iEYEARECAAYFAkmslTgACgkQtTMYHG2NR9VOcACghTrFu49tFgjXY1j7dd3VnU7S
8jYAn3Wo5OedX4fngRQqANgBcCo2OV3g
=rJOn
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |