** Branch linked: lp:ubuntu/karmic/cryptsetup
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Any update on the sed issue? 2:1.0.6-7ubuntu6 still contains it.
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Probably udev vol_id interface does not change that often for us to try
to work around it in advance. Unnecessary calls from startup scripts is
a plague that slows whole system boot process. Checking shell error
codes would be the fastest and cleanest of all, but unfortunately vol_id
shares error
Would you be so kind to please elaborate on why we need sed here at all?
Further looking at
http://git.kernel.org/?p=linux/hotplug/udev.git;a=blob;f=extras/volume_id/vol_id.c;h=3e44c3b069794b81a1e61338c98eef0fa7671bf3;hb=HEAD#l254
shows vol_id always return a static string in this case, as well
Hi Andrei-
Good catch.
I have confirmed that, in fact:
unknown=`/lib/udev/vol_id -t /dev/null 21`
returns a static string.
This is far simpler/cleaner. That super-escaped sed is truly nasty.
Let me prepare and test another upload...
:-Dustin
--
Encrypted SWAP partition not
The sed part isn't necessary. I only put it in for the sake of
robustness against future updates/regressions to vol_id. In the past,
'vol_id -t /dev/null' used to report /dev/null: unknown volume type.
Now it does not mention the device that was probed, just the result
unknown or non-unique
Also, when I checked the vol_id source, error code 4 was not restricted
to the unknown device type case. I can't remember of the top of my
head what the other cases were that also returned error 4, but as of a
month ago, there were some.
--
Encrypted SWAP partition not created/mounted
I'm getting the same issue.
I'll take a look at it.
:-Dustin
** Tags added: regression
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: cryptsetup (Ubuntu)
Importance: Undecided = Medium
Assignee: (unassigned) = Dustin Kirkland (kirkland)
Status: Confirmed = In Progress
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because
Tested the patch, works here. Examined, looks good. I'm sponsoring.
In the future, please subscribe ubuntu-main-sponsors to the bug if
there's a patch and you're requesting sponsorship/upload.
Thanks!
:-Dustin
--
Encrypted SWAP partition not created/mounted
This bug was fixed in the package cryptsetup - 2:1.0.6-7ubuntu3
---
cryptsetup (2:1.0.6-7ubuntu3) jaunty; urgency=low
[ https://launchpad.net/~svenkata ]
* debian/checks/un_vol_id: dynamically build the unknown volume type
string, to allow for encrypted swap, LP: #316607
--
Hello, maintainer...
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
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
Same problem here. Seems like a pretty big issue.
** Changed in: cryptsetup (Ubuntu)
Status: New = Confirmed
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The patch works for non SWAP/TMP partitions also. I had the same problem
with /dev/sda4 and this patch worked.
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This patch fixes the problem with swap and tmp option.
Your help is much appreciated Shiv. Thank you very much indeed!
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Many thanks for your help Shiv!
I've applied the patch to vol_id and un_vol_id in /lib/cryptsetup/checks/.
Now, the automated creation of the swap device works again.
Looking at the scripts, your explanation seems absolutely plausible to
me.
I've even cross-checked the detection by trying
I have the same problem with swap and cryptsetup.
Furthermore it's the same problem with the tmp option. Thus I guess
it's related.
r...@hubble:/home# /etc/init.d/cryptdisks start
* Starting remaining crypto disks... * tmp (starting)
* tmp: the precheck for '/dev/mapper/sil_ajabbgcfcdah5'
It seems this is due to a change in vol_id (udev package). vol_id
(udev: 124-12) used to say /dev/mapper/swap: unknown volume type when
it failed to find a known filesystem on /dev/mapper/swap. After my
latest update, vol_id (udev: 136-4) says unknown or non-unique volume
type (--probe-all lists
Content of my /etc/ctypttab:
# target name source device key file options
SWAP /dev/sde8 /dev/urandom swap
--
Encrypted SWAP partition not created/mounted
https://bugs.launchpad.net/bugs/316607
You received this bug notification because you are a member of Ubuntu
Bugs, which is
19 matches
Mail list logo
