linux-kernel - SV: PROBLEM: raid5 just dies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <6FDE26082D451C41BE1A3742966200B3B51C67@DR2EX01.hosting.itg>
Date:	Mon, 30 Oct 2006 23:07:44 +0100
From:	"Andreas Paulsson" <andreas.paulsson@...arden.se>
To:	"Neil Brown" <neilb@...e.de>
Cc:	<linux-kernel@...r.kernel.org>
Subject: SV: PROBLEM: raid5 just dies

>Exactly how are aes-loop and raid5 connected together?

We use 5x300gb drives in a raid5 array, which is then used as a physical
disk in an lvm volume, with one logical volume. This logical volume is
then encrypted with "losetup -e aes /dev/loop1 /dev/vg0/lv0", and then
formatted with ReiserFS.

>Is the loop above the raid5 or below?

It's below the raid5, since the raid5 is created straight onto the
drives.

>A precise description of how things are arranged would help.

Does the above look good enough?

>A copy of /proc/mdstat would be good to.

Personalities : [raid1] [raid6] [raid5] [raid4]
md1 : active raid1 hdn1[1] hdf1[0]
      195358336 blocks [2/2] [UU]

md0 : active raid5 hdd1[1] hdc1[0] hdh1[4] hdg1[3] hde1[2]
      1250274304 blocks level 5, 64k chunk, algorithm 2 [5/5] [UUUUU]

unused devices: <none>

>Thanks,
>NeilBrown


/Andreas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/