[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2012-04-13 Thread Steve Langasek
*** This bug is a duplicate of bug 874774 *** https://bugs.launchpad.net/bugs/874774 ** This bug has been marked a duplicate of bug 874774 could not mount /dev/mapper/cryptswap1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-08-20 Thread Martin Pitt
** Changed in: udev (Ubuntu) Status: New = Invalid -- cryptsetup: c_swap_unformatted still exists after system boot https://bugs.launchpad.net/bugs/502665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-08-02 Thread Brian Murray
** Tags added: patch -- cryptsetup: c_swap_unformatted still exists after system boot https://bugs.launchpad.net/bugs/502665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-08-01 Thread Daniel Kauffman
This is a regression from bug 475936, see comment #30 there. Running the cryptdisks_start script: # cryptdisks_start CRYPT In turn runs: # dmsetup rename CRYPT_unformatted CRYPT as a result of which the CRYPT device is created but the CRYPT_unformatted device is not removed. I have filed bug

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-08-01 Thread Daniel Kauffman
The attached forces cryptdisks_start to wait until it is safe to rename the device. In my case, the delay is typically about one second. The attached is only a work-around, it seems to me that such logic would be better suited somewhere in dmsetup. See bug 612310 comment #2. ** Patch added:

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-07-20 Thread mejo
I guess this bug has been identified in buglog of bug 508848, right? thus i suggest to change status to 'invalid'. -- cryptsetup: c_swap_unformatted still exists after system boot https://bugs.launchpad.net/bugs/502665 You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-01-18 Thread Stefan Fleiter
Forgot to mention: I opened bug 508848 for mountall not mounting the decrypted partition. -- cryptsetup: c_swap_unformatted still exists after system boot https://bugs.launchpad.net/bugs/502665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-01-16 Thread Stefan Fleiter
** Bug watch added: code.google.com/p/cryptsetup/issues #38 http://code.google.com/p/cryptsetup/issues/detail?id=38 ** Also affects: cryptsetup via http://code.google.com/p/cryptsetup/issues/detail?id=38 Importance: Unknown Status: Unknown -- cryptsetup: c_swap_unformatted still

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-01-16 Thread Stefan Fleiter
I have this problem here with Lucid as of today, too. # ls /dev/mapper/ control home home_unformatted root var var_unformatted According to the cryptsetup bugreport this could be caused by udev or DeviceKit-disks. At the moment I assume that this causes mountall not to mount my home and

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-01-16 Thread Stefan Fleiter
** Also affects: udev (Ubuntu) Importance: Undecided Status: New -- cryptsetup: c_swap_unformatted still exists after system boot https://bugs.launchpad.net/bugs/502665 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 502665] Re: cryptsetup: c_swap_unformatted still exists after system boot

2010-01-16 Thread Steve Langasek
Stefan, At the moment I assume that this causes mountall not to mount my home and var partition which means I have to manually support every single boot process. No, this issue does not cause failures in mounting the decrypted partitions. If your partitions are not being mounted correctly on