Bug 547119

Description of problem:

For example if you want to grow a filesystem on a LUKS volume on top of a LVM logical volume you have to resize the logical volume, then resize the LUKS container and then grow the filesystem.

The problem is in step 2 when using the "cryptsetup resize" command to resize the LUKS volume to the new volume size.

Version-Release number of selected component (if applicable):
cryptsetup-luks-1.1.0-0.1.fc12.i686
cryptsetup-luks-libs-1.1.0-0.1.fc12.i686

How reproducible:
Try to grow a filesystem on a LUKS volume without closing/reopening it

Steps to Reproduce:
1. Create a LV formated with LUKS or use an existing one
2. Grow the LV
3. run "cryptsetup resize name-of-luks-volume"
  
Actual results:

# cryptsetup resize system-smtest-clear
Device (null) doesn't exist or access denied.
Command failed: Device (null) doesn't exist or access denied.

The volume is not resized

# cryptsetup resize /dev/mapper/system-smtest-clear
gives the same result

Expected results:

No output and the LUKS volume resized

Additional info:

commands to reproduce with existing VG named system:
# lvcreate -L 1G -n smtest system
# cryptsetup luksFormat /dev/mapper/system-smtest
# cryptsetup luksOpen /dev/mapper/system-smtest system-smtest-clear
# lvresize -L +1G system/smtest
# cryptsetup resize system-smtest-clear
Device (null) doesn't exist or access denied.
Command failed: Device (null) doesn't exist or access denied.