Raphael Hertzog wrote:
On Fri, 07 Dec 2007, Patrick Caulfield wrote:
dnprogs (2.39.2) unstable; urgency=low
.
* Fix package building with new dpkg-shlibdeps
Closes: #453786
A changelog must explain the change, ie how you fixed the problem. In
the future try to not forget
Klaus Ethgen wrote:
Package: lvm10
Version: 1:1.0.8-12
Severity: critical
The lvm10 package is not in stable any more so all systems with kernel
2.4 and lvm will be broken!
Debian's 2.4 kernels include the device mapper patches. That will enable lvm2 to
work.
Although I thought that 2.4
That's fair.
I'll make the library packages a Recommends and the progs package a
depends...there really is no point in installing the progs if you're not
going to use them and I really want to ease DECnet installation as much
as possible - it's complicated enough as it is!
Patrick
--
To
Package: ftp.debian.org
Severity: normal
lvm10 doesn't build on unstable anymore and is superceded upstream by lvm2
see bug report 394212.
LVM2 is compatible with lvm1 metadata and supported upstream.
-- System Information:
Debian Release: 3.1
Architecture: sparc (sparc64)
Shell: /bin/sh
lvm10 doesn't work with 2.6 kernels and is unsupported upstream.
I recommend we remove this package for etch.
lvm2 works with 2.4 kernels, and is compatible with lvm10 metadata formats.
and (importantly) is well supported upstream
--
patrick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Jesse Molina wrote:
Package: lvm10
Version: 1:1.0.8-12
Severity: normal
Hi
When passing options -f or --file to vgcfgbackup, I get an error;
vgcfgbackup: invalid option -- f
The man page says that this is a valid option. Not sure if the man page is
out of date, or there is
dnprogs isn't affected by this bug as it doesn't call any routines inside
uulib that use this function.
The only call we make into the library is
UUEncodeToStream();
where the output 'file' is always either a pipe or a socket to a mail delivery
program.
patrick
--
To UNSUBSCRIBE, email to
I am reliably informed by Alasdair that the md_component_detection is
considerably better than it was. In fact it now uses the same detection
algorithm that MD itself uses.
So I think this should be set back on by default now.
--
patrick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
Package: lvm2
Version: 2.01.14-1
Severity: important
Tags: patch
HPPA kernels don't support O_DIRECT, as LVM2 uses O_DIRECT to read/write
metadata this option has to be disabled in ./configure.
It looks to me like a simple typo in debian rules:
-ifneq (,$(findstring $(DEB_HOST_ARCH), arm hpp
Holger Dietze wrote:
Package: lvm10
Version: 1:1.0.8-8
Severity: normal
File: /lib/lvm-10/pvmove
I have a long-running pvmove which I decided to abort (and resume
later). According to manpage:
pvmove may be safely interrupted by SIGINT while moving next free allocated
logical
Michael Setzer wrote:
Patrick,
I'm not pretty sure if I got you right.
After upgrading lvm-common to 1.5.19 the error is still there and my system
is still unbootable (same error message as described already).
It certainly fixed the problem for the original reporter. Once I'd see
the
Michael Setzer wrote:
Patrick,
I'm not pretty sure if I got you right.
After upgrading lvm-common to 1.5.19 the error is still there and my system
is still unbootable (same error message as described already).
What I've done now to upgrade to 1.5.19 is:
- booted with the
Thanks. Can you try the updated package on http://people.debian.org/~patrick/
please?
--
patrick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Christian Weeks wrote:
Yup. That worked a treat.
Thanks!
Great, I'll upload that one then.
--
patrick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Christian Weeks wrote:
Package: lvm-common
Version: 1.5.18
Severity: critical
Justification: breaks the whole system
I ran an upgrade this morning and picked up this package, among others,
including a new kernel image. This generated a new initrd which rendered
my Root on LVM system
Christian Weeks wrote:
Hmm, I've regenerated a working one now... When I was examining it, it
did have vgchange contained within it, and also another vgchange under
/lib/lvm-200/ (or something similar)... I figured that one of the
scripts was somehow choking when it tried to execute the
On Thu, Apr 07, 2005 at 02:49:39PM +0100, Ian Jackson wrote:
Patrick Caulfield writes (Re: Bug#303423: LVM has annoying 110% restriction
on snapshot LV size):
There's no point in creating a snapshot any bigger! The COW
mechanism copies blocks from the original device into the snapshot
On Wed, Apr 06, 2005 at 04:52:24PM +0100, Ian Jackson wrote:
Package: lvm10
Version: 1.0.4-5woody2 (source)
I have a backup system that makes snapshots of the filesystems when
backing them up. In order to minimise the risk of snapshots
overflowing, I arranged for the snapshot to use all of
On Sun, Mar 20, 2005 at 12:37:09AM +0100, Christian Jaeger wrote:
PS. I've noticed that the loop devices are not released.
mount -o loop $from $to
# this allocates a loop device, as can be seen in ps auxww
# (under kernel 2.4.x, as [loop0] or similar kernel threads)
# or in /proc/mounts
On Sun, Mar 20, 2005 at 06:55:27PM +0100, Christian Jaeger wrote:
Actually, I've just read the manpage for umount and have realised
there is a -d option exactly for the purpose of releasing the loop
device.
So, additionally to applying my patch, the umount statements in
On Fri, Feb 04, 2005 at 09:06:34PM -0500, Andrew Schulman wrote:
I'm trying to set up LVM for the first time.??I have the?dm-mod kernel
module loaded.??No?udev?or?devfs?here. The?following commands all succeed:
pvcreate /dev/hda1
vgcreate vg /dev/hda1
vgchange -ay vg
Now I want to
On Wed, Feb 02, 2005 at 12:23:08AM +0100, Frans Pop wrote:
Hello Patrick,
On Monday 31 January 2005 16:40, you wrote:
Secondly try using vgcfgrestore to restore the metadata onto the disks,
you only need to do this if 1) above fails
I've got my system back! :-D
Your suggestions and
On Wed, Feb 02, 2005 at 02:01:24PM +0100, Goswin von Brederlow wrote:
Patrick Caulfield [EMAIL PROTECTED] writes:
Ok, so only man pvmove left.
Yep,
--
patrick
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Wed, Feb 02, 2005 at 03:06:18PM +0100, Helge Kreutzmann wrote:
If e2fsadm does not support LVM2, and 2.6 only supports LVM2, would it
not be possible for e2fsadm to check for 2.6 and refuse to run? Giving
me the help screen of a different command (lvmextend) is not quite
helpfull right
:-)
CVSROOT:/cvs/lvm2
Module name:LVM2
Changes by: [EMAIL PROTECTED] 2005-02-02 14:31:49
Modified files:
. : WHATS_NEW
tools : commands.h
Log message:
Remove unused -f from pvmove
Patches:
Package: libsysfs1
Version: 1.2.0-1
Severity: normal
Please can you move libsysfs into /lib ?
The multipath tools rely on this library for device identification and they
really need to be started before /usr is mounted if it is on a different
partition.
-- System Information:
Debian Release:
On Tue, Feb 01, 2005 at 05:06:42PM +0100, Goswin Brederlow wrote:
Package: lvm-common
Version: 1.5.17
Severity: minor
File: pvmove
Hi,
the manpage of pvmove doesn't list all options, namely -f, of pvmove
and does not describe al options it mentions, namely -v.
On that note: The
Two things to try:
firstly, enable md_component_autodetection in /etc/lvm/lvm.conf - it look slike
the system has found BOTH the MD and it's components, that explains the
duplicate PV entries. If this doesn't work then add filters to lvm.conf to
exclude the SCSI disks (or just include the MDs).
On Mon, Jan 24, 2005 at 11:38:53PM +, Alasdair G Kergon wrote:
Check you don't have md_component_detection disabled
in /etc/lvm/lvm.conf.
Otherwise try adding filters.
yes, md_component_detection is disabled by default in Debian because the
original implementation was buggy and caused
On Wed, Jan 12, 2005 at 01:57:05PM +0100, Wesley W. Terpstra wrote:
This is documented in the cryptsetup package.
I don't think dmsetup needs to document these features since they are not
very useful without the hash functions, etc.
I would close this bug if I was maintainer. :-)
Agreed.
On Tue, Jan 11, 2005 at 11:28:27AM -0500, Christian Hudon wrote:
Package: lvm2
Version: 2.00.24-1
I guess 256GB was a nice large number the for default max vg size when
lvm1 was started, but now that you can buy a single hard drive that is
twice this size, it seems to me to be a bit on
It might be that you are using LVM1 format metadata - which still has this
restriction.
vgconvert will upgrade that metadata to LVM2 and remove the limit.
(BTW the default of 4MB PE size is years old on LVM1 (25/10/2002),
and has never been a limitation in LVM2)
--
patrick
--
To
On Tue, Jan 11, 2005 at 12:05:08PM -0500, Christian Hudon wrote:
Hmm. If that's really the case, then the manpage for vgcreate is in need
of some serious updating. Some extracts:
-s, --physicalextentsize PhysicalExtentSize[kKmMgGtT]
Sets the physical extent size on
33 matches
Mail list logo
