I can confirm that this bug affects me too in Ubuntu 8.10.
For me, the scenario is a little different (newly installed system where
the VG has many PV:s, of which only one's extents are in use). dmsetup
deps still only reports the PV whose extents are in use, and not all
PV:s that are required for
Found a workaround that helps in my specific case.
I use only one LV in the VG, so the way I can make sure "dmsetup deps"
will report that the LV depends on all PV:s, is by making the LV large
enough that it spreads out across the entire VG. Note! I do not need to
resize the file system, just exte
Thanks Alasdair for the clarifications. Your explanation is compatible
with the dmsetup(8) manpage:
deps [device_name]
Outputs a list of (major, minor) pairs for devices referenced by
the live table for the specified device.
I'm moving this bug now to initramfs-tools, beca
This bug is not the fault of the dmsetup tool. It belongs with
initramfs-tools.
** Changed in: devmapper (Ubuntu)
Status: Confirmed => Invalid
--
"dmsetup deps" does not accurately report LVM dependencies, can cause boot
failure
https://bugs.launchpad.net/bugs/282189
You received this bu
This bug is not the fault of the dmsetup tool. It belongs with
initramfs-tools, which should find a better way of determining all PV:s
required to start the VG where a particular LV resides.
** Changed in: initramfs-tools
Status: New => Confirmed
--
"dmsetup deps" does not accurately repo
** Description changed:
Scenario:
My root fs is on LVM which has some LVs (including root) over a single
VG over a single PV which is a physical partition.
I create an encrypted PV, and extend the VG with it. I do not, however,
migrate any part of the root fs to the new PV.
"
** Changed in: cryptsetup (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools
Status: Confirmed => Invalid
** Description changed:
Scenario:
My root fs is on LVM which has some LVs (including root) over a single
VG over a single PV which is a physical partitio
I agree. The workaround only works some of the times. Then, when it's
grey again, it stays grey until tilda is completely restarted.
Previously I added some details about when tilda works and breaks for me, as a
comment on a duplicate of this bug.
https://bugs.launchpad.net/ubuntu/+source/tilda/+
I have the same problem with tilda going blank after the having hid it
with the hot key and then trying to bring it back with the hot key. As
the submitter wrote, restarting the application may be necessary to see
the results of any changed settings in the Preferences dialogue.
Same version of til
Is this the same bug as
https://bugs.launchpad.net/ubuntu/+source/tilda/+bug/144175 ?
--
Tilda doesn't function correctly when altering preferences
https://bugs.launchpad.net/bugs/148694
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubunt
10 matches
Mail list logo
