Re: [Pkg-clamav-devel] ClamAV Package on Wheezy
No. I'm not involved in the LTS project any more. The stretch update has just today been uploaded. I expect someone from the LTS team will handle it shortly. Scott K On July 21, 2018 6:48:24 AM UTC, Klaipedaville on Google wrote: >Hello Scott, > >Will you be able to take care of it again, please (as per my previous >[old] message down-below)? Is Clamav not available in packages any more >at all? Many thanks! > >Regards, >Dennis > >P.S. It looks like this "issue" is 'an every July come back occurrence' >isn't it? :) > > >From: Scott Kitterman >Sent: Sunday, July 3, 2016 19:29 >To: Sebastian Andrzej Siewior ; Klaipedaville on Google >Cc: cla...@packages.debian.org ; debian-lts@lists.debian.org >Subject: Re: [Pkg-clamav-devel] ClamAV Package on Wheezy > >I'm going to take care of it. > >Scott K > >On July 3, 2016 9:04:48 AM EDT, Sebastian Andrzej Siewior > wrote: >>On 2016-06-30 09:36:18 [+0300], Klaipedaville on Google wrote: >>> Hello there, >>Hi, >> >>> It’s been almost half a year since I’ve been getting this "Clamav is >>outdated, don't panic" message in my logs and patiently waiting for >>updates. I was wondering is it not available / coming any more in >>packages and we are on our own now to compile it from sources? Could >>anybody advise, please? Many thanks! >> >>Wheezy is now in the hands of the Debian-LTS team. I won't do an >upload >>but according to my IRC backlog someone from LTS team is looking into >>this. I CCed the LTS team to ACK/NACK my statement :) >> >>> Regards, >>> Dennis. >> >>Sebastian >> >>___ >>Pkg-clamav-devel mailing list >>pkg-clamav-de...@lists.alioth.debian.org >>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
XFS Metadata corruption detected - linux-image-4.9
Dear all
After update to linux-image-4.9 in jessie, the system cannot mount XFS
filesystem. The system recommends run xfs_repair (>= v4.3) to fix the
issue, but the current xfsprogs is v3.2.1
I have gone back to linux-image-3.16 and no longer triggers any problems
in the logs, the filesystem is OK.
BR,
Luis
kern.log:
--
Jul 21 05:16:51 kraken kernel: [ 22.859221] SGI XFS with ACLs,
security attributes, realtime, no debug enabled
Jul 21 05:16:51 kraken kernel: [ 22.860288] XFS (sdb1): Mounting V5
Filesystem
Jul 21 05:16:52 kraken kernel: [ 22.995886] XFS (sdb1): Ending clean mount
Jul 21 05:16:52 kraken kernel: [ 23.020712] XFS (sdb1): Corruption
warning: Metadata has LSN (1:142552) ahead of current LSN (1:4680).
Please unmount and run xfs_repair (>= v4.3) to resolve.
Jul 21 05:16:52 kraken kernel: [ 23.020745] XFS (sdb1): Metadata
corruption detected at xfs_dir3_block_read_verify+0x5a/0x100 [xfs],
xfs_dir3_block block 0x557fc0
Jul 21 05:16:52 kraken kernel: [ 23.020748] XFS (sdb1): Unmount and
run xfs_repair
Jul 21 05:16:52 kraken kernel: [ 23.020750] XFS (sdb1): First 64 bytes
of corrupted metadata buffer:
Jul 21 05:16:52 kraken kernel: [ 23.020752] 9eca281f: 58 44 42
33 75 e3 ce 72 00 00 00 00 00 55 7f c0 XDB3u..r.U..
Jul 21 05:16:52 kraken kernel: [ 23.020753] 9eca281f0010: 00 00 00
01 00 02 2c d8 12 14 b2 f1 8b 37 40 38 ..,..7@8
Jul 21 05:16:52 kraken kernel: [ 23.020755] 9eca281f0020: 80 85 1e
9f ee 88 85 e1 00 00 00 00 00 00 00 60 ...`
Jul 21 05:16:52 kraken kernel: [ 23.020756] 9eca281f0030: 07 f0 06
e0 00 78 01 30 02 08 00 d8 00 00 00 00 .x.0
Jul 21 05:16:52 kraken kernel: [ 23.020922] XFS (sdb1): Corruption
warning: Metadata has LSN (1:142552) ahead of current LSN (1:4680).
Please unmount and run xfs_repair (>= v4.3) to resolve.
Jul 21 05:16:52 kraken kernel: [ 23.020947] XFS (sdb1): Metadata
corruption detected at xfs_dir3_block_read_verify+0x5a/0x100 [xfs],
xfs_dir3_block block 0x557fc0
Jul 21 05:16:52 kraken kernel: [ 23.020949] XFS (sdb1): Unmount and
run xfs_repair
Jul 21 05:16:52 kraken kernel: [ 23.020950] XFS (sdb1): First 64 bytes
of corrupted metadata buffer:
Jul 21 05:16:52 kraken kernel: [ 23.020952] 9eca281f: 58 44 42
33 75 e3 ce 72 00 00 00 00 00 55 7f c0 XDB3u..r.U..
Jul 21 05:16:52 kraken kernel: [ 23.020953] 9eca281f0010: 00 00 00
01 00 02 2c d8 12 14 b2 f1 8b 37 40 38 ..,..7@8
Jul 21 05:16:52 kraken kernel: [ 23.020954] 9eca281f0020: 80 85 1e
9f ee 88 85 e1 00 00 00 00 00 00 00 60 ...`
Jul 21 05:16:52 kraken kernel: [ 23.020956] 9eca281f0030: 07 f0 06
e0 00 78 01 30 02 08 00 d8 00 00 00 00 .x.0
Jul 21 05:16:52 kraken kernel: [ 23.020972] XFS (sdb1): metadata I/O
error: block 0x557fc0 ("xfs_trans_read_buf_map") error 117 numblks 8
Jul 21 05:16:52 kraken kernel: [ 23.021116] XFS (sdb1): Corruption
warning: Metadata has LSN (1:142552) ahead of current LSN (1:4680).
Please unmount and run xfs_repair (>= v4.3) to resolve.
Jul 21 05:16:52 kraken kernel: [ 23.021140] XFS (sdb1): Metadata
corruption detected at xfs_dir3_block_read_verify+0x5a/0x100 [xfs],
xfs_dir3_block block 0x557fc0
Jul 21 05:16:52 kraken kernel: [ 23.021142] XFS (sdb1): Unmount and
run xfs_repair
Jul 21 05:16:52 kraken kernel: [ 23.021143] XFS (sdb1): First 64 bytes
of corrupted metadata buffer:
Jul 21 05:16:52 kraken kernel: [ 23.021144] 9eca281f: 58 44 42
33 75 e3 ce 72 00 00 00 00 00 55 7f c0 XDB3u..r.U..
Jul 21 05:16:52 kraken kernel: [ 23.021146] 9eca281f0010: 00 00 00
01 00 02 2c d8 12 14 b2 f1 8b 37 40 38 ..,..7@8
Jul 21 05:16:52 kraken kernel: [ 23.021147] 9eca281f0020: 80 85 1e
9f ee 88 85 e1 00 00 00 00 00 00 00 60 ...`
Jul 21 05:16:52 kraken kernel: [ 23.021148] 9eca281f0030: 07 f0 06
e0 00 78 01 30 02 08 00 d8 00 00 00 00 .x.0
Jul 21 05:16:52 kraken kernel: [ 23.021163] XFS (sdb1): metadata I/O
error: block 0x557fc0 ("xfs_trans_read_buf_map") error 117 numblks 8
Jul 21 05:16:52 kraken kernel: [ 23.021302] XFS (sdb1): Corruption
warning: Metadata has LSN (1:142552) ahead of current LSN (1:4680).
Please unmount and run xfs_repair (>= v4.3) to resolve.
--
Luis Díaz González
+34 635442700
0x628AC934F9EC8826.asc
Description: application/pgp-keys
Re: XFS Metadata corruption detected - linux-image-4.9
On Sat, 2018-07-21 at 16:26 +0200, Luis Díaz González wrote: > Dear all > > > After update to linux-image-4.9 in jessie, the system cannot mount XFS > filesystem. The system recommends run xfs_repair (>= v4.3) to fix the > issue, but the current xfsprogs is v3.2.1 > > I have gone back to linux-image-3.16 and no longer triggers any problems > in the logs, the filesystem is OK. As I wrote in the announcement, there is no need to upgrade to Linux 4.9 just because it's available. Linux 3.16 will still be supported throughout the jessie LTS period. Ben. -- Ben Hutchings Anthony's Law of Force: Don't force it, get a larger hammer. signature.asc Description: This is a digitally signed message part
Re: Jessie update of mutt?
HI Antonio, On Sa 21 Jul 2018 06:41:21 CEST, Antonio Radici wrote: On Thu, Jul 19, 2018 at 04:06:06PM +0200, Mike Gabriel wrote: Dear maintainer(s), The Debian LTS team would like to fix the security issues which are currently open in the Jessie version of mutt: https://security-tracker.debian.org/tracker/source-package/mutt Would you like to take care of this yourself? If yes, please follow the workflow we have defined here: https://wiki.debian.org/LTS/Development I'm currently working on this, Nice... the amount of bugs require some time to go through the existing patches (whcih are only for the updated unstable version) and backport them to stable. I expect the work to be completed in the next few days. Sure. If you don't mind, please ping up once uploaded to security-master (for LTS you can simply upload to security-master (jessie-security) without feedback from some security or LTS team member). I will handle the DLA announcement and the internal formalities (security tracker updates and such). Greets, Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgpCW6Kd4ZbUm.pgp Description: Digitale PGP-Signatur
