I believe bug #874774 is the new version of this bug, which also affects
me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475936
Title:
race condition between encrypted device creation and
Hi,
I think this bug has not been fixed. I have the same problem as kapetr.
Encrypted swap is not mounted, but manual swapon activates swap.
kapetr, did you opened new bug? Which number is it?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@kapetr: Please open a new bug for your issue as this bug has been fixed
a long time ago. Thanks in advance!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/475936
Title:
race condition between
Hello,
I have in Ubuntu 10.10 problem with encrypted swap - maybe it has
something common with this bug.
At boot I get every time this info (even with splash on):
The disk drive for /dev/mapper/cryptswap1 is not ready yet or not
present Continue to wait; or Press S to skip mounting or M for
** Attachment added: monitor screenshot - cryptswap
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/475936/+attachment/1851280/+files/shot0002.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Mike: This bug is fixed. Please open a new bug (after checking that
your problem hasn't been reported) if you still have problems with swap
or /tmp.
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
The following script seems to fix the tmp issue. It is a workaround though and
not a fix. I've rebooted 5 times in a row and it is still mounting
/dev/mapper/crypttmp on /tmp without hanging up the system.
I changed the stock /etc/init/mountall.conf script by commenting out the emits
@Vreixo Formoso: This bug is fixed. Please open a new bug by running
ubuntu-bug cryptsetup from terminal if you still have problems with your
cryptsetup.
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
papukaija: it is not really fixed... I'm having this issue with a fresh
lucid install and completely updated system. Should I really open a new
(duplicate) bug? Or should I re-open the bug? Thanks
--
race condition between encrypted device creation and mountall probing with
random-encrypted
Ok, bug #571682 refers to the same problem and it is opened for lucid. I
will comment there. Thanks
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification
I am having the /tmp issue with a Lucid fresh install. Is this really
fixed?
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of
On Mon, 2010-05-03 at 13:55 +, Vreixo Formoso wrote:
I am having the /tmp issue with a Lucid fresh install. Is this really
fixed?
I've not tried Lucid yet, but it's managed to go away for quite some
time now on Karmic (for me, at least). This is a nasty race condition
that seems to come
I've been reading a bit and I understand that the problem is that: a) at
a given time during boot, the tmp encrypted partition gets decrypted
by whatever process that handles /etc/crypttab. b) then, given the tmp
option is specified in /etc/crypttab, mkfs.ext2 is executed on the given
decrypted
I am having the same issue after applying the last round of updates in
synaptic. Mine seems related to the CDROM drive. If it is closed during
boot, with or without a CD in it, I get the hang more often. If there is
a CD in the drive, the system always hangs on startup.
--
race condition between
I'd like to comment on this fix (e.g. cryptsetup -
2:1.0.6+20090405.svn49-1ubuntu7.2 w/watershed 4 and mountall 1.0):
I've been running with encrypted root/swap for a month, but then had
hardware problems forcing me to replace the system disk. All was well
for nearly a week 5+ days and 6+
Ken,
This error message probably indicates that the device name in /etc/fstab
(and possibly in /etc/crypttab) does not match the device name that's
being set up in the initramfs. Can you boot with init=/bin/sh, and
compare the contents of /etc/fstab with /dev/mapper/ ?
--
race condition
Yes, that was my intial assessment; however:
1. They do match up.
2. It sometimes works
This is why I suspect a race condition.
Regards,
== k ==
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
Well, this bug report was about a race condition specifically with
random-crypted tmp and swap partitions. If you are encountering a race
condition when mounting your root filesystem, it's an unrelated bug;
please file a separate report.
--
race condition between encrypted device creation and
This bug was fixed in the package cryptsetup -
2:1.0.6+20090405.svn49-1ubuntu7.2
---
cryptsetup (2:1.0.6+20090405.svn49-1ubuntu7.2) karmic-proposed; urgency=low
* Depend on watershed.
* cryptdisks.functions: do_tmp should mount under /var/run/cryptsetup for
changing the
David,
This shouldn't be possible. the cryptdisks upstart jobs won't run until
udev is started, and udev won't start until the virtual-filesystems
are mounted, and /var/run is configured as a virtual filesystem (a
tmpfs) standard in Ubuntu.
Do you have some other filesystem configured to mount
I'm having a problem with this as well. With Steve's fix, mkdir -p
/var/run/cryptsetup/... fails because / is mounted read-only at the
time. This then prevents cryptsetup from setting the correct mode
(1777). If I change /var/run/cryptsetup/... to /mnt in
cryptdisk.functions everything works fine.
I'll file a new bug report on this topic when I have a chance to be in
front of the machine and reboot it again to confirm this. Probably next
week. I feel this minor issue shouldn't prevent from committing the
current fix anyway.
--
race condition between encrypted device creation and mountall
Indeed, it was not supposed to stay. In my own testing, it did not. I
don't think this should block publishing of the SRU, but could you file
a new bug report about this (lower-priority) issue so we keep it on the
radar?
--
race condition between encrypted device creation and mountall probing
I've just noticed while doing something else ;-) with my system fully
booted for more than 24 hrs, that ls -l /dev/mapper was showing me,
among other things :
brw-rw 1 root disk 252, 16 2009-12-24 08:54 c_swap
brw-rw 1 root disk 252, 16 2009-12-24 08:54 c_swap_unformatted
I assume the
Rebooted once more, still get correctly encrypted /tmp, so I confirm the
fix works for me.
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are
** Tags added: verification-done
** Tags removed: verification-needed
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of Ubuntu
Accepted cryptsetup into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: cryptsetup (Ubuntu
Hi,
I've tested Version: 2:1.0.6+20090405.svn49-1ubuntu7.2 from karmic-
proposed, and I'm not sure whether the issue is completely fixed or not
:
At first reboot after having installed the package, I found myself in the
following situation :
System displayed :
* Starting init crypto disks...
On Wed, Dec 23, 2009 at 08:25:53PM -, Swâmi Petaramesh wrote:
Pressing [Ctrl]-[Alt]-[Del], I got :
init: network-interface (lo) pres-start process (1022) killed by TERM
signal
I'm afraid that's probably bug #497299, unrelated to cryptsetup.
I would say cryptsetup is working for you, but
Geeez, so many init bugs ! ;-)
Well, my system survived 2 more reboots with encrypted /tmp properly
mounted each time, so as far as I'm concerned the cryptsetup fix is good
:-)
Thanks for all your time and efforts Steve :-))
There's little chance I reboot it much more in the coming days : being
** Branch linked: lp:~ubuntu-core-dev/cryptsetup/karmic
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package cryptsetup - 2:1.1.0~rc2-1ubuntu8
---
cryptsetup (2:1.1.0~rc2-1ubuntu8) lucid; urgency=low
* cryptdisks.functions: do_tmp should mount under /var/run/cryptsetup for
changing the permissions of the filesystem root, not directly on /tmp,
cryptsetup 2:1.0.6+20090405.svn49-1ubuntu7.2 has been reuploaded to
karmic-proposed, with a more complete fix for this issue (the one just
uploaded to lucid). Awaiting SRU team processing.
** Tags removed: verification-failed
--
race condition between encrypted device creation and mountall
Marking this verification-failed based on further analysis in bug
#493480. We now have a *different* race condition between mountall and
cryptsetup, but we still have a race condition.
** Tags added: verification-failed
** Tags removed: verification-needed
--
race condition between encrypted
** Changed in: cryptsetup (Ubuntu Karmic)
Status: Fix Committed = In Progress
** Changed in: cryptsetup (Ubuntu Lucid)
Status: Fix Released = In Progress
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
Testing karmic-proposed cryptsetup (2:1.0.6+20090405.svn49-1ubuntu7.1) :
Still doesn't solve the issue with encrypted /tmp not mounting at boot.
(Encrypted swap with random key and encrypted /home with fixed key-file
do work, as previously).
So that's a proposed fix doesn't change or improve
I ran mountall with logging (per Steve's request on comment #15) by
calling mountall (in mountall.conf) with :
exec mountall --daemon -v $force_fsck $fsck_fix $tmptime
/dev/.mountall.log
The matter is that 1st time I rebooted with that I ended up with...
encrypted /tmp properly mounted !
Then
** Attachment added: mountall log with /tmp NOT mounting
http://launchpadlibrarian.net/37002956/.mountall-2.log
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug
Re-opened my bug #493480, de-duplicated from the present one and
affected to the mountall package per Steve suggestion in comment 12.
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You
Accepted cryptsetup into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: cryptsetup (Ubuntu
Swâmi,
Just confirmed that using the test case in lucid, the /tmp directory
fails to be mounted. However, this is because mountall treats the /tmp
directory specially. Varying the /etc/fstab line in either of two ways
is enough to fix this:
- set the 'pass' option to non-zero
- mount it
(If you believe the mountall behavior is wrong, please file a separate
bug report on the mountall package for this.)
** Description changed:
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected
** Description changed:
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my
Hi Steve,
I'll give it a shot tonight with a non-zero pass entry for /tmp.
However per your description I feel that the mountall behaviour is
definitely wrong, and I'm not sure whether another bug report should be
filed, or if this precise bugreport should be reaffected to mountall,
as this is
Hi,
Here, even with a non-zero fsck pass for /tmp, it doesn't mount
either.
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of
On Thu, Dec 17, 2009 at 06:43:40PM -, Swâmi Petaramesh wrote:
Here, even with a non-zero fsck pass for /tmp, it doesn't mount
either.
Please edit /etc/init/mountall.conf, appending '-v /dev/.mountall.log
21' to the invocation of mountall, reboot, and attach the resulting file
to this bug
I'm on travel and wont' be able to perform this test until next week.
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of Ubuntu
True, a mkfs is generally going to take longer than an mkswap and is
more likely to hit the race. Thanks, updating the testcase.
** Description changed:
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Other testcase comments : Steven you've left swap instead of tmp at
some place ;-)
Also, the system _will_ boot successfully but with a short (almost
invisible on a fast system) warning message that some fstab-defined
partitions couldn't be mounted _if_ the fstab entry for /tmp has 0 for
fsck
** Description changed:
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my
Steve, I'd like to test the fix, but can't currently get the fixed
package from the karmic-proposed repositories. Could you please give
me a download link, or would you mind emailing it to me at : s w a m i
(at) p e t a r a m e s h (dot) o r g ?
--
race condition between encrypted device
Hi again,
I've installed cryptsetup 2:1.1.0~rc2-1ubuntu5 (dated today, gotten from
archive.ubuntu.com pool), which necessitated as dependancy that I also
install libpopt0 from the same source.
After that, I rebooted my Karmic machine, but still, my encrypted /tmp
is NOT mounted after reboot.
I
I've checked the mountall code; the SIGUSR1 handler only rescans for
remote mount points. So no need for anyone to provide the debugging
information requested in the previous comment.
I think I've sussed out how to do this correctly using 'dmsetup rename';
will have a go at the code and will
** Also affects: cryptsetup (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: cryptsetup (Ubuntu Karmic)
Importance: Undecided = High
** Changed in: cryptsetup (Ubuntu Karmic)
Status: New = Triaged
** Changed in: cryptsetup (Ubuntu Karmic)
Milestone: None
** Branch linked: lp:~ubuntu-core-dev/cryptsetup/ubuntu
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This bug was fixed in the package cryptsetup - 2:1.1.0~rc2-1ubuntu4
---
cryptsetup (2:1.1.0~rc2-1ubuntu4) lucid; urgency=low
[ Steve Langasek ]
* debian/initramfs/cryptroot-script: if plymouth is present in the
initramfs, use this directly, bypassing the cryptsetup askpass
** Also affects: cryptsetup (Ubuntu Lucid)
Importance: High
Status: Fix Released
--
race condition between encrypted device creation and mountall probing with
random-encrypted devices (swap, tmp)
https://bugs.launchpad.net/bugs/475936
You received this bug notification because you are
** Description changed:
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my
** Description changed:
Binary package hint: mountall
I am using Ubuntu 9.10 with the latest packages applied (apt-get uprade)
Version of mountall: 1.0
Expected results: /dev/mapper/tmp should be mounted on /tmp
Unexpected results: /dev/mapper/tmp is not mounted on /tmp
In my
Testcase warning : I believe the testcase in wrong. In 2 Karmic systems
I have, encrypted swap usually works, but encrypted /tmp never works.
Bugfix testcase should be done against encrypted /tmp
--
race condition between encrypted device creation and mountall probing with
random-encrypted
60 matches
Mail list logo
