linux-kernel - Re: I give up

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: <17946.29660.368403.553290@smtp.charter.net>
Date:	Mon, 9 Apr 2007 13:11:56 -0400
From:	"John Stoffel" <john@...ffel.org>
To:	Gene Heskett <gene.heskett@...il.com>
Cc:	linux-kernel@...r.kernel.org, Jeff Garzik <jeff@...zik.org>
Subject: Re: I give up

>>>>> "Gene" == Gene Heskett <gene.heskett@...il.com> writes:

Gene> On Monday 09 April 2007, Jeff Garzik wrote:
>> Gene Heskett wrote:
>>> Now the 64k$ question: While running with LVM2 managed disks, is it
>>> possible to run without dm_mod, the device-mapper?  If so, please tell
>>> me how to achieve this.
>> 
>> No; device mapper is the kernel portion of LVM2.
>> 
>> Jeff, who actively avoids LVM on home computers

Gene> Ya shoulda warned me.  :-)

Gene> It should have lots bigger warning labels, in bright red
Gene> self-illuminating signs, than it does.  It in fact seems to work
Gene> well, but it is a major breakage for some common apps, like
Gene> doing backups...

>From the GNU info doc on the tar program:

    Metadata stored in snapshot files include device numbers, which,
    obviously is supposed to be a non-volatile value. However, it turns
    out that NFS devices have undependable values when an automounter gets
    in the picture. This can lead to a great deal of spurious redumping in
    incremental dumps, so it is somewhat useless to compare two NFS
    devices numbers over time. The solution implemented currently is to
    considers all NFS devices as being equal when it comes to comparing
    directories; this is fairly gross, but there does not seem to be a
    better way to go.

This to me, seems to be another borkage of the tar program.  Can you
tell Amanda to use 'dump/restore' instead of tar instead?  Or heck,
just move to Bacula, it's smarter than amanda/tar and it supports
writing to DVDs, etc.  http://www.bacula.org

This tar borkness is pretty annoying, since Amanda (from the docs
page) only keeps indexes in terms of host/filesystem/path/date,
nothing about the major/minor (device) numbers.

It just re-inforces my desire to never use Amanda again.

John
john@...ffel.org
-
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/