RE: Re: Problems with loop-aes?

To: "Adam Porter" <adam@alphapapa.net>
Cc: <debian-user@lists.debian.org>
Subject: RE: Re: Problems with loop-aes?
From: "Jan Johansson" <j2@mupp.net>
Date: Thu, 9 Mar 2006 20:50:26 +0100
Message-id: <[🔎] 9CB5A76200029E439A44D2E52901D6A47A52@waldorf.Muppnet.local>
>Are you losetup'ing and *then* running dd to create the file?  From
reading
>your post, I get that impression.  If you are, you should create the
file
>with dd, and *then* losetup it.


I am following:
http://deb.riseup.net/storage/encryption/loop-aes/


Here is a longer post I did  on linux-crypto

>What you said was inconsistent. loop3/md4 vs. loop1/md2

I will do that. Just as a "sort out" 3/4 were the examples on the page.
1/2 was what I actually used. 

I start by rebooting my system to be sure.

cookiemonster:~/VMware# reboot
[removed useless info about system shutting down]

We log in, and I recreated the array (after zeroing superblocks)
mdadm --create /dev/md2 --chunk=64 --level=raid1 --raid-devices=2
/dev/hde1 /dev/hdf1


cookiemonster:~# mdadm --detail /dev/md2
/dev/md2:
        Version : 00.90.01
  Creation Time : Thu Mar  9 20:25:02 2006
     Raid Level : raid1
     Array Size : 80418112 (76.69 GiB 82.35 GB)
    Device Size : 80418112 (76.69 GiB 82.35 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 2
    Persistence : Superblock is persistent

    Update Time : Thu Mar  9 20:25:02 2006
          State : clean, resyncing
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

 Rebuild Status : 2% complete

           UUID : 5e24575f:df3b5a81:f2a68636:ff7f6e2b
         Events : 0.415

    Number   Major   Minor   RaidDevice State
       0      33        1        0      active sync
/dev/.static/dev/hde1
       1      33       65        1      active sync
/dev/.static/dev/hdf1
cookiemonster:~#

We have plenty of memory
cookiemonster:~# free
             total       used       free     shared    buffers
cached
Mem:       3116936     170160    2946776          0       6296
73592
-/+ buffers/cache:      90272    3026664
Swap:      1951888          0    1951888
cookiemonster:~#
cookiemonster:~# modprobe loop
cookiemonster:~# head -c 15 /dev/urandom | uuencode -m - | head -n 2 |
tail -n 1 | losetup -p 0 -e AES256  /dev/loop1 /dev/md2

So far, all is well, log shows:
Mar  9 20:29:24 cookiemonster kernel: loop: loaded (max 8 devices)
Mar  9 20:29:24 cookiemonster udev[4958]: creating device node
'/dev/loop0'
Mar  9 20:29:24 cookiemonster udev[4965]: creating device node
'/dev/loop1'
Mar  9 20:29:24 cookiemonster udev[4972]: creating device node
'/dev/loop2'
Mar  9 20:29:24 cookiemonster udev[5007]: creating device node
'/dev/loop3'
Mar  9 20:29:24 cookiemonster udev[5008]: creating device node
'/dev/loop4'
Mar  9 20:29:24 cookiemonster udev[5009]: creating device node
'/dev/loop5'
Mar  9 20:29:24 cookiemonster udev[5010]: creating device node
'/dev/loop6'
Mar  9 20:29:24 cookiemonster udev[5011]: creating device node
'/dev/loop7'

cookiemonster:~# dd if=/dev/zero of=/dev/loop3 bs=4k conv=notrunc
2>/dev/null
cookiemonster:~# losetup -d /dev/loop1
cookiemonster:~# losetup -F /dev/loop1
Password:
cookiemonster:~# mkfs.ext3 /dev/loop1

And THEN I get the below (but mind you, the FS create continues, until
"Writing inode tables: Done" and then the terminal freezes. But
processes starts to dies with OOM ( still have plenty RAM left).
cookiemonster:~# free
             total       used       free     shared    buffers
cached
Mem:       3116936     983468    2133468          0     819064
45896
-/+ buffers/cache:     118508    2998428
Swap:      1951888          0    1951888
cookiemonster:~#

Mar  9 20:32:46 cookiemonster kernel: Out of Memory: Killed process 4256
(mysqld).
Mar  9 20:32:46 cookiemonster mysqld_safe[5080]: Number of processes
running now: 0
Mar  9 20:32:46 cookiemonster mysqld_safe[5082]: restarted
Mar  9 20:32:48 cookiemonster mysqld[5085]: 060309 20:32:48  InnoDB:
Database was not shut down normally!
Mar  9 20:32:48 cookiemonster mysqld[5085]: InnoDB: Starting crash
recovery.
Mar  9 20:32:48 cookiemonster mysqld[5085]: InnoDB: Reading tablespace
information from the .ibd files...
Mar  9 20:32:48 cookiemonster mysqld[5085]: InnoDB: Restoring possible
half-written data pages from the doublewrite
Mar  9 20:32:48 cookiemonster mysqld[5085]: InnoDB: buffer...
Mar  9 20:32:49 cookiemonster mysqld[5085]: 060309 20:32:49  InnoDB:
Starting log scan based on checkpoint at
Mar  9 20:32:49 cookiemonster mysqld[5085]: InnoDB: log sequence number
0 45824.
Mar  9 20:32:49 cookiemonster mysqld[5085]: InnoDB: Doing recovery:
scanned up to log sequence number 0 45824
Mar  9 20:32:49 cookiemonster mysqld[5085]: InnoDB: Last MySQL binlog
file position 0 79, file name /var/log/mysql/mysql-bin.000051
Mar  9 20:32:49 cookiemonster mysqld[5085]: 060309 20:32:49  InnoDB:
Flushing modified pages from the buffer pool...
Mar  9 20:32:50 cookiemonster mysqld[5085]: 060309 20:32:50  InnoDB:
Started; log sequence number 0 45824
Mar  9 20:32:51 cookiemonster mysqld[5085]: /usr/sbin/mysqld: ready for
connections.
Mar  9 20:32:51 cookiemonster mysqld[5085]: Version:
'4.1.11-Debian_4sarge2-log'  socket: '/var/run/mysqld/mysqld.sock'
port: 3306  Source distribution


==> /var/log/messages <==
Mar  9 20:31:58 cookiemonster kernel: swapper: page allocation failure.
order:0, mode:0x20
Mar  9 20:31:59 cookiemonster kernel:  [__alloc_pages+760/880]
__alloc_pages+0x2f8/0x370
Mar  9 20:31:59 cookiemonster kernel:  [__get_free_pages+37/64]
__get_free_pages+0x25/0x40
Mar  9 20:31:59 cookiemonster kernel:  [kmem_getpages+34/192]
kmem_getpages+0x22/0xc0
Mar  9 20:31:59 cookiemonster kernel:  [cache_grow+186/384]
cache_grow+0xba/0x180
Mar  9 20:31:59 cookiemonster kernel:  [cache_alloc_refill+362/544]
cache_alloc_refill+0x16a/0x220
Mar  9 20:31:59 cookiemonster kernel:
[__crc_xfrm_state_alloc+4160046/4557196] do_rw_taskfile+0x1c1/0x290
[ide_core]
Mar  9 20:31:59 cookiemonster kernel:  [kmem_cache_alloc+62/64]
kmem_cache_alloc+0x3e/0x40
Mar  9 20:31:59 cookiemonster kernel:  [send_signal+174/368]
send_signal+0xae/0x170
Mar  9 20:31:59 cookiemonster kernel:  [__group_send_sig_info+142/224]
__group_send_sig_info+0x8e/0xe0
Mar  9 20:31:59 cookiemonster kernel:  [group_send_sig_info+138/176]
group_send_sig_info+0x8a/0xb0
Mar  9 20:31:59 cookiemonster kernel:  [it_real_fn+0/96]
it_real_fn+0x0/0x60
Mar  9 20:31:59 cookiemonster kernel:  [send_group_sig_info+49/96]
send_group_sig_info+0x31/0x60
Mar  9 20:31:59 cookiemonster kernel:  [it_real_fn+36/96]
it_real_fn+0x24/0x60
Mar  9 20:31:59 cookiemonster kernel:  [run_timer_softirq+203/448]
run_timer_softirq+0xcb/0x1c0
Mar  9 20:31:59 cookiemonster kernel:  [do_timer+224/240]
do_timer+0xe0/0xf0
Mar  9 20:31:59 cookiemonster kernel:  [__do_softirq+123/128]
__do_softirq+0x7b/0x80
Mar  9 20:31:59 cookiemonster kernel:  [do_softirq+39/48]
do_softirq+0x27/0x30
Mar  9 20:31:59 cookiemonster kernel:  [do_IRQ+251/304]
do_IRQ+0xfb/0x130
Mar  9 20:31:59 cookiemonster kernel:  [common_interrupt+24/32]
common_interrupt+0x18/0x20
Mar  9 20:31:59 cookiemonster kernel:  [pvc_info+123/256]
pvc_info+0x7b/0x100
Mar  9 20:31:59 cookiemonster kernel:  [default_idle+35/64]
default_idle+0x23/0x40
Mar  9 20:31:59 cookiemonster kernel:  [cpu_idle+52/64]
cpu_idle+0x34/0x40
Mar  9 20:31:59 cookiemonster kernel:  [start_kernel+424/496]
start_kernel+0x1a8/0x1f0
Mar  9 20:31:59 cookiemonster kernel:  [unknown_bootoption+0/352]
unknown_bootoption+0x0/0x160

==> /var/log/syslog <==
Mar  9 20:31:58 cookiemonster kernel: swapper: page allocation failure.
order:0, mode:0x20
Mar  9 20:31:59 cookiemonster kernel:  [__alloc_pages+760/880]
__alloc_pages+0x2f8/0x370
Mar  9 20:31:59 cookiemonster kernel:  [__get_free_pages+37/64]
__get_free_pages+0x25/0x40
Mar  9 20:31:59 cookiemonster kernel:  [kmem_getpages+34/192]
kmem_getpages+0x22/0xc0
Mar  9 20:31:59 cookiemonster kernel:  [cache_grow+186/384]
cache_grow+0xba/0x180
Mar  9 20:31:59 cookiemonster kernel:  [cache_alloc_refill+362/544]
cache_alloc_refill+0x16a/0x220
Mar  9 20:31:59 cookiemonster kernel:
[__crc_xfrm_state_alloc+4160046/4557196] do_rw_taskfile+0x1c1/0x290
[ide_core]
Mar  9 20:31:59 cookiemonster kernel:  [kmem_cache_alloc+62/64]
kmem_cache_alloc+0x3e/0x40
Mar  9 20:31:59 cookiemonster kernel:  [send_signal+174/368]
send_signal+0xae/0x170
Mar  9 20:31:59 cookiemonster kernel:  [__group_send_sig_info+142/224]
__group_send_sig_info+0x8e/0xe0
Mar  9 20:31:59 cookiemonster kernel:  [group_send_sig_info+138/176]
group_send_sig_info+0x8a/0xb0
Mar  9 20:31:59 cookiemonster kernel:  [it_real_fn+0/96]
it_real_fn+0x0/0x60
Mar  9 20:31:59 cookiemonster kernel:  [send_group_sig_info+49/96]
send_group_sig_info+0x31/0x60
Mar  9 20:31:59 cookiemonster kernel:  [it_real_fn+36/96]
it_real_fn+0x24/0x60
Mar  9 20:31:59 cookiemonster kernel:  [run_timer_softirq+203/448]
run_timer_softirq+0xcb/0x1c0
Mar  9 20:31:59 cookiemonster kernel:  [do_timer+224/240]
do_timer+0xe0/0xf0
Mar  9 20:31:59 cookiemonster kernel:  [__do_softirq+123/128]
__do_softirq+0x7b/0x80
Mar  9 20:31:59 cookiemonster kernel:  [do_softirq+39/48]
do_softirq+0x27/0x30
Mar  9 20:31:59 cookiemonster kernel:  [do_IRQ+251/304]
do_IRQ+0xfb/0x130
Mar  9 20:31:59 cookiemonster kernel:  [common_interrupt+24/32]
common_interrupt+0x18/0x20
Mar  9 20:31:59 cookiemonster kernel:  [pvc_info+123/256]
pvc_info+0x7b/0x100
Mar  9 20:31:59 cookiemonster kernel:  [default_idle+35/64]
default_idle+0x23/0x40
Mar  9 20:31:59 cookiemonster kernel:  [cpu_idle+52/64]
cpu_idle+0x34/0x40
Mar  9 20:31:59 cookiemonster kernel:  [start_kernel+424/496]
start_kernel+0x1a8/0x1f0
Mar  9 20:31:59 cookiemonster kernel:  [unknown_bootoption+0/352]
unknown_bootoption+0x0/0x160
Reply to:
Follow-Ups:
- RE: Re: Problems with loop-aes?
  - From: Adam Porter <adam@alphapapa.net>
Prev by Date: Re: hotplug script before udev
Next by Date: Re: appletalk
Previous by thread: Re: Problems with loop-aes?
Next by thread: RE: Re: Problems with loop-aes?
Index(es):
- Date
- Thread