Bug#432150: [Pkg-cryptsetup-devel] Bug#432150: /sbin/cryptsetup: repair tools needed

2007-07-11 Thread Jonas Meurer
On 07/07/2007 [EMAIL PROTECTED] wrote:
 dm-crypt has data corruption issues, and this includes the luks
 header.  a tool to repair the luks header so that you can run fsck on
 the fs would be useful.  it might be that most of the data are ok.
 
 this could take the form of an fsck-like repair, or a similar
 partition's header to repair the header, or a luksRestore from a
 backed up luksDump.  i'm sure there are issues with each of these, but
 it seems likely that *something* can be done.  there was brief
 discussion on the dm-crypt mailing list about how to repair luks
 headers and that might be a place to start.

Could you point us to more documentation regarding the data corruption
issues? I found your report at the dm-crypt mailing list, but not any
suggestions about how to repair headers.

Maybe you even have some code to start from.

greetings,
 jonas


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#432150: [Pkg-cryptsetup-devel] Bug#432150: /sbin/cryptsetup: repair tools needed

2007-07-11 Thread t takahashi

i wish that i could help more.  i do still have the corrupted
partition (and the identical working one) and will try suggestions,
but will have to overwrite it soon.

the dm-crypt discussion was brief and afaik to the effect that the
header format is well documented, so if you have a similar header on
another partition, you repair the corrupted one by using dd for the
homologous parts.  e.g. 2007-06-08 07:41:52 GMT on the same url.

a web search reveals data corruption stories.  one person found that
strace enabled opening (didn't work for me).  there might be dm issues
in addition to dm-crypt or luks issues (brief scan of dm mailing list
subjects).  i am physically limited in computer use else i would give
you urls.

thanks.


--
Webmaster: do you believe that people will (a) switch browsers to view
your best viewed with page or (b) go to your competitor?


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#432150: /sbin/cryptsetup: repair tools needed

2007-07-07 Thread gambarimasu+reportbug
Package: cryptsetup
Version: 2:1.0.4+svn26-1
Severity: wishlist
File: /sbin/cryptsetup


dm-crypt has data corruption issues, and this includes the luks
header.  a tool to repair the luks header so that you can run fsck on
the fs would be useful.  it might be that most of the data are ok.

this could take the form of an fsck-like repair, or a similar
partition's header to repair the header, or a luksRestore from a
backed up luksDump.  i'm sure there are issues with each of these, but
it seems likely that *something* can be done.  there was brief
discussion on the dm-crypt mailing list about how to repair luks
headers and that might be a place to start.

data corruption reports can be found via google, and on the dm-crypt
mailing list.  many, including mine, are hard to reproduce.  fwiw,
here is mine: message 2007-07-01 02:59:28 GMT on
http://news.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt .

there is a well-known and probably fixed issue with 2.6.18 and raid 5,
and there are issues that do not involve that kernel and do not
involve raid 5.  i suspect that even 2.6.22rc7 is vulnerable.

thanks.

-- System Information:
Debian Release: 4.0
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18myver-2007-06-q
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages cryptsetup depends on:
ii  dmsetup  2:1.02.08-1 The Linux Kernel Device Mapper use
ii  libc62.3.6.ds1-13GNU C Library: Shared libraries
ii  libdevma 2:1.02.08-1 The Linux Kernel Device Mapper use
ii  libgcryp 1.2.3-2 LGPL Crypto library - runtime libr
ii  libgpg-e 1.4-1   library for common error values an
ii  libpopt0 1.10-3  lib for parsing cmdline parameters
ii  libuuid1 1.39+1.40-WIP-2006.11.14+dfsg-2 universally unique id library

cryptsetup recommends no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]