[Bug 716659] [NEW] Root filesystem goes "Read only" after installing multipath-tools on Lucid

[Joseph Salisbury]

Public bug reported:

Binary package hint: multipath-tools

Installing either multipath-tools-boot or multipath-tools causes the
root partition to go 'Read onlyl'.  System is then unable to reboot.
The only way to recover system is to boot in rescue mode and un-install
multipath-tools.

The install of multipath-tools caused a segmentation fault.  The
following was done with the PPA at: http://ppa.launchpad.net/serge-
hallyn/multipath-backport/ubuntu/.  However, this same issue happens
with the multipath-tools package that ships with Lucid.

pravin at ubuntu:~$ sudo apt-get install multipath-tools-boot
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  kpartx libaio1 multipath-tools
The following NEW packages will be installed:
  kpartx libaio1 multipath-tools multipath-tools-boot
0 upgraded, 4 newly installed, 0 to remove and 80 not upgraded.
Need to get 251kB of archives.
After this operation, 1,065kB of additional disk space will be used.
Do you want to continue [Y/n]? Y
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/main libaio1
0.3.107-3ubuntu2 [9,608B]
Get:2 http://ppa.launchpad.net/serge-hallyn/multipath-backport/ubuntu/
lucid/main kpartx 0.4.8-14ubuntu7 [29.1kB]
Get:3 http://ppa.launchpad.net/serge-hallyn/multipath-backport/ubuntu/
lucid/main multipath-tools 0.4.8-14ubuntu7 [198kB]
Get:4 http://ppa.launchpad.net/serge-hallyn/multipath-backport/ubuntu/
lucid/main multipath-tools-boot 0.4.8-14ubuntu7 [13.8kB]
Fetched 251kB in 1s (135kB/s)
Preconfiguring packages ...
Selecting previously deselected package libaio1.
(Reading database ... 41797 files and directories currently installed.)
Unpacking libaio1 (from .../libaio1_0.3.107-3ubuntu2_amd64.deb) ...
Selecting previously deselected package kpartx.
Unpacking kpartx (from .../kpartx_0.4.8-14ubuntu7_amd64.deb) ...
Selecting previously deselected package multipath-tools.
Unpacking multipath-tools (from
.../multipath-tools_0.4.8-14ubuntu7_amd64.deb) ...
Selecting previously deselected package multipath-tools-boot.
Unpacking multipath-tools-boot (from
.../multipath-tools-boot_0.4.8-14ubuntu7_all.deb) ...
Processing triggers for man-db ...
Processing triggers for ureadahead ...
Setting up libaio1 (0.3.107-3ubuntu2) ...

Setting up kpartx (0.4.8-14ubuntu7) ...

Setting up multipath-tools (0.4.8-14ubuntu7) ...
 * Starting multipath daemon multipathd

                 [ OK ]

Setting up multipath-tools-boot (0.4.8-14ubuntu7) ...
debconf: DbDriver "templatedb": could not write
/var/cache/debconf/templates.dat-new: Read-only file system
dpkg: error processing multipath-tools-boot (--configure):
 subprocess installed post-installation script returned error exit status 1
touch: cannot touch `/var/lib/update-notifier/dpkg-run-stamp': Read-only
file system
sh: cannot create /var/lib/update-notifier/updates-available: Read-only file system
Segmentation fault

Hardware details:

OS: Lucid boots from boot LUN on SAN.
SAN:EMC Clariion
Hardware : UCS blade server from Cisco. 

Attached is the multipath.conf file we are using.

I will attach the output from apport-bug shortly.
I will also attach the following:
$ uname -a > uname-a.log
$ cat /proc/version_signature > version.log
$ dmesg > dmesg.log
$ sudo lspci -vvnn > lspci-vvnn.log

Just let me know if any other data is required.

** Affects: multipath-tools (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: multipath-tools multipath-tools-boot

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in ubuntu.
https://bugs.launchpad.net/bugs/716659

Title:
  Root filesystem goes "Read only" after installing multipath-tools on
  Lucid