From: Rick Moritz <rahvin@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt / Software Raid5 issues on Ubuntu Lucid 64bit
Date: Fri, 3 Sep 2010 15:36:27 +0200 [thread overview]
Message-ID: <Mahogany-0.67.1-6944-20100903-153627.00@Ming.Ricknet.net> (raw)
In-Reply-To: <4C80F69E.8000500@gmail.com>
Had those self-same issues (well, crypted RAID-array io-locking on me during samba-operations on it), and moving to kernel 2.6.34 fixed it for me.
Never figured out what was really causing those problems.
On Fri, 03 Sep 2010 15:22:38 +0200 BOBA FETT <boba23@gmail.com> wrote:
> Hey folks,
>
> I am switching from loop-aes to dm_crypt. I am trying to use it on a
> fresh Ubuntu 64bit server installation with my 6x750gb Software raid5
> array.
> Array is clean and freshly created, I encrypted it using
>
> cryptsetup -y -c aes -h ripemd160 -s 256 create STUFF /dev/md0
>
> Format went fine, but when I try to copy back large amount of data to
> the encrypted array (about 900gig) my copy thread always hangs itself at
> some point during the process. I can't access the array anymore, though
> the raid itself is fine, no drives are kicked out or anything.
> Reboot gives me back access and the array is still ok.
> When the problem occures I see the following trace in log:
>
> Aug 29 02:54:24 liberty24 kernel: [221558.020638] Pid: 400, comm:
> md0_raid5 Not tainted 2.6.32-24-server #41-Ubuntu Unknow
> Aug 29 02:54:24 liberty24 kernel: [221558.020638] RIP:
> 0010:[<ffffffff814353b8>] [<ffffffff814353b8>] clone_endio+0x38/0xe0
> Aug 29 02:54:24 liberty24 kernel: [221558.020638] RSP:
> 0018:ffff880069531c40 EFLAGS: 00010246
> Aug 29 02:54:24 liberty24 kernel: [221558.020638] RAX: ffffffffa023f760
> RBX: 0000000000000000 RCX: 0100000000000081
> Aug 29 02:54:24 liberty24 kernel: [221558.020638] RDX: 0000000000000017
> RSI: 0000000000000000 RDI: ffffc9001247e040
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] RBP: ffff880069531c70
> R08: 0000000000000000 R09: 010000000000282c
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] R10: 0000000000000000
> R11: 0000000000000001 R12: ffff88000ca0ed80
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] R13: ffff88000df85ed0
> R14: ffff8800695ca600 R15: ffbf8800116cb348
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] FS:
> 00007fb75e7f4700(0000) GS:ffff880001c40000(0000) knlGS:0000000000000000
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] CS: 0010 DS: 0018 ES:
> 0018 CR0: 000000008005003b
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] CR2: 00007f2d10190000
> CR3: 0000000053ae8000 CR4: 00000000000006e0
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] DR0: 0000000000000000
> DR1: 0000000000000000 DR2: 0000000000000000
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] DR3: 0000000000000000
> DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] Process md0_raid5
> (pid: 400, threadinfo ffff880069530000, task ffff88006a08dbc0)
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] ffff88001be85ed8
> 0000000000000000 0000000000000000 ffff88000ca0ed80
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] <0> ffff8800695ca600
> ffff88001be85ed8 ffff880069531c80 ffffffff8117159d
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] <0> ffff880069531cb0
> ffffffffa023d8c9 ffff880069531ca0 ffff88004d8312b0
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff8117159d>]
> bio_endio+0x1d/0x40
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffffa023d8c9>]
> crypt_dec_pending+0x69/0x90 [dm_crypt]
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffffa023daa8>]
> crypt_endio+0x68/0x150 [dm_crypt]
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff8117159d>]
> bio_endio+0x1d/0x40
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffffa0200add>]
> handle_stripe5+0x46d/0x9a0 [raid456]
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffffa0201028>]
> handle_stripe+0x18/0x30 [raid456]
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffffa0201432>]
> raid5d+0x202/0x320 [raid456]
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff814298dc>]
> md_thread+0x5c/0x130
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff81085090>]
> ? autoremove_wake_function+0x0/0x40
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff81429880>]
> ? md_thread+0x0/0x130
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff81084d16>]
> kthread+0x96/0xa0
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff810141ea>]
> child_rip+0xa/0x20
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff81084c80>]
> ? kthread+0x0/0xa0
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] [<ffffffff810141e0>]
> ? child_rip+0x0/0x20
> Aug 29 02:54:24 liberty24 kernel: [221558.035928] RSP <ffff880069531c40>
> Aug 29 02:54:24 liberty24 kernel: [221558.133125] ---[ end trace
> 29f7fd9a7bbb5a00 ]---
>
> Using the array uncrypted, data copy to it works just fine, copied over
> the full 900 GB now 6 times without a hickup.
>
> Can anybody help me with this?
>
> thanks
>
> Thorsten
next prev parent reply other threads:[~2010-09-03 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 13:22 [dm-crypt] dm-crypt / Software Raid5 issues on Ubuntu Lucid 64bit BOBA FETT
2010-09-03 13:36 ` Rick Moritz [this message]
2010-09-03 13:52 ` BOBA FETT
-- strict thread matches above, loose matches on Subject: below --
2010-09-03 13:21 Thorsten Peter
2010-09-03 13:57 ` Milan Broz
2010-09-03 14:10 ` Thorsten Peter
2010-09-03 14:12 ` Thorsten Peter
2010-09-03 18:14 ` Arno Wagner
2010-09-04 11:14 ` Thorsten Peter
2010-09-05 12:34 ` BOBA FETT
2010-09-05 12:56 ` Arno Wagner
2010-09-05 16:42 ` Milan Broz
2010-09-06 3:40 ` Arno Wagner
2010-09-06 6:25 ` Heinz Diehl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Mahogany-0.67.1-6944-20100903-153627.00@Ming.Ricknet.net \
--to=rahvin@gmail.com \
--cc=dm-crypt@saout.de \
--cc=rick.moritz@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.