linux-kernel - Re: lvm backwards compatability

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070109151539.GW21980@agk.surrey.redhat.com>
Date:	Tue, 9 Jan 2007 15:15:39 +0000
From:	Alasdair G Kergon <agk@...hat.com>
To:	Dave Jones <davej@...hat.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: lvm backwards compatability

On Mon, Jan 08, 2007 at 06:01:11PM -0500, Dave Jones wrote:
> Did backwards compatability with old LVM metadata break intentionally
> in 2.6.19 ?  I have a volume that mounts just fine in 2.6.18,
> but moving to 2.6.19 gets me this..
 
No - and at first sight that's not a kernel device-mapper problem.

Please grab some diagnostics:
  run the lvmdump script (present in the newest packages) or from here:

  http://sources.redhat.com/cgi-bin/cvsweb.cgi/~checkout~/LVM2/scripts/lvm_dump.sh?content-type=text/plain&cvsroot=lvm2

with the -a and -m flags.

[NB If you use dm-crypt and have userspace device-mapper < 1.02.13 you
need to remove the encryption keys from the 'dmsetup' output by hand.]

Alasdair
-- 
agk@...hat.com
-
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/