Bug#918812: lvm2: "Failed to parse thin params" from vgchange et al on boot into latest kernel

2019-01-09 Thread Grant Taylor
Package: lvm2
Version: 2.02.168-2
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

Not sure about the severity; as luck would have it my system can boot,
but many volumes were rendered entirely unavailable so for some this
would be a showstopper.

This issue appears to be specific to the use of thin provisioned
logical volumes.  Non-thin volumes even in the same vg come up just
fine.

   * What led up to the situation?

Automated update to kernel 4.9.0-8-amd64.  The latest stable lvm2
package version 2.02.168-2 was on the system.

This combination does not work.  Apparently the thin params in
question originate out of the kernel's dm ioctl, yielding the error in
the headline from lvs, vgchange, etc.

Also, most of the tools segfault starting after I ran vgchange -ay
manually to try and activate the missing volumes.  Unclear why they
didn't segfault starting from the first run.

Non-thin volumes were activated properly at initramfs time.  So I was
able to poke around and ultimately fix things by updating lvm2.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I built the lvm2 packages from testing, installed those, and now it
works.  The only missing build-dep was debhelper, satisfied from
backports.  The system info below reflects my self-built testing
backport of lvm2, which is version 2.03.02-1.

Notably I did not install a newer thin-provisioning-tools, just the
packages from building lvm2.

BTW this lvm2-vs-kernel breakage issue, including debian having "old"
lvm2 tools, is the subject of one of Linus's patented gentle
discussions on lkml, wherein he is adament that 'NOBODY gets to say
"oh, you should just update user land tools"'.*  So it would be nice
for the deb lvm team to either mask this issue by somehow guaranteeing
compatibility of shipped versions and/or applying all due pressure
upstream to eliminate this sort of breakage.

* https://lore.kernel.org/lkml/1ec0a220-d5b0-1c27-e63b-c4d3f4ce9...@torlan.ru/T/



-- System Information:
Debian Release: 9.6
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-8-amd64 (SMP w/12 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages lvm2 depends on:
ii  dmeventd  2:1.02.155-1
ii  dmsetup   2:1.02.155-1
ii  libaio1   0.3.110-3
ii  libblkid1 2.29.2-1+deb9u1
ii  libc6 2.24-11+deb9u3
ii  libdevmapper-event1.02.1  2:1.02.155-1
ii  libdevmapper1.02.12:1.02.155-1
ii  libreadline5  5.2+dfsg-3+b1
ii  libselinux1   2.6-3+b3
ii  libsystemd0   232-25+deb9u6
ii  libudev1  232-25+deb9u6
ii  lsb-base  9.20161125

Versions of packages lvm2 recommends:
ii  thin-provisioning-tools  0.6.1-4+b1

lvm2 suggests no packages.

-- debconf-show failed



Bug#507465: mb2md often misses message boundaries in mbox files

2008-12-07 Thread Grant Taylor

Bruno De Fraine [EMAIL PROTECTED] writes:


mb2md has worked perfectly well for me with mbox files coming from
Procmail and Dovecot. Are you certain your mailboxes are not ill-
formatted to begin with?


Yes, they do seem to be badly formed.  My dud mail files were from 
thunderbird/icedove.  Evidently its local mail storage is ad-hoc mbox-like 
non-mbox files.  Sigh...


Anyway, thanks, all, for the investigation.

--
Grant Taylor
http://www.picante.com/



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



Bug#507465: mb2md often misses message boundaries in mbox files

2008-12-01 Thread Grant Taylor
Package: mb2md
Version: 3.20-2
Severity: grave
Justification: renders package unusable

This script intentionally looks for a blank line in between messages
in the mbox file.  There is no such requirement that I know of;
certainly all the mbox data I have has tons of messages with no blank
line before the '^From ' line.

As is, I got 30% fewer messages in the new Maildir, and lots of
messages were actually two or three messages run together.  The result
is so garbled I wonder if anyone else has ever used this script...

This tweak seems to have worked for me:

--- /usr/bin/mb2md  2005-07-04 16:38:47.0 -0400
+++ mb2md   2008-12-01 11:18:42.080177429 -0500
@@ -979,8 +979,6 @@
# The subject of the message
my $subject = '';
 
-   my $previous_line_was_empty = 1;
-
 # We record the message start line here, for error
 # reporting.
 my $startline;
@@ -1003,7 +1001,6 @@
 $_ =~ s/\r\n$/\n/;
 
 if ( /^From /
-$previous_line_was_empty
 (!defined $contentlength) 
   )
 {
@@ -1419,8 +1416,6 @@
 # End of the if statement dealing with message 
body.
 }
 
-   $previous_line_was_empty = ( $_ eq \n );
-
 # End of while (MBOX) loop.
 }
 # Close the input file.


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25.10.habanero2
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages mb2md depends on:
ii  libtimedate-perl1.1600-5 Time and date functions for Perl
ii  perl [perl5]5.8.8-7etch3 Larry Wall's Practical Extraction 

mb2md recommends no packages.

-- no debconf information



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