[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
This bug was fixed in the package linux - 4.13.0-39.44 --- linux (4.13.0-39.44) artful; urgency=medium * linux: 4.13.0-39.44 -proposed tracker (LP: #1761456) * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel) // CVE-2017-5754 - x86/mm: Reinitialize TLB state on hotplug and resume * intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) (LP: #1759920) // CVE-2017-5715 (Spectre v2 Intel) - Revert "x86/mm: Only set IBPB when the new thread cannot ptrace current thread" - x86/speculation: Use Indirect Branch Prediction Barrier in context switch * DKMS driver builds fail with: Cannot use CONFIG_STACK_VALIDATION=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel (LP: #1760876) - [Packaging] include the retpoline extractor in the headers * retpoline hints: primary infrastructure and initial hints (LP: #1758856) - [Packaging] retpoline-extract: flag *0xNNN(%reg) branches - x86/speculation, objtool: Annotate indirect calls/jumps for objtool - x86/speculation, objtool: Annotate indirect calls/jumps for objtool on 32bit - x86/paravirt, objtool: Annotate indirect calls - [Packaging] retpoline -- add safe usage hint support - [Packaging] retpoline-check -- only report additions - [Packaging] retpoline -- widen indirect call/jmp detection - [Packaging] retpoline -- elide %rip relative indirections - [Packaging] retpoline -- clear hint information from packages - KVM: x86: Make indirect calls in emulator speculation safe - KVM: VMX: Make indirect call speculation safe - x86/boot, objtool: Annotate indirect jump in secondary_startup_64() - SAUCE: early/late -- annotate indirect calls in early/late initialisation code - SAUCE: vga_set_mode -- avoid jump tables - [Config] retpoline -- switch to new format - [Packaging] retpoline hints -- handle missing files when RETPOLINE not enabled - [Packaging] final-checks -- remove check for empty retpoline files * retpoline: ignore %cs:0xNNN constant indirections (LP: #1752655) - [Packaging] retpoline -- elide %cs:0x constants on i386 * zfs system process hung on container stop/delete (LP: #1754584) - SAUCE: Fix non-prefaulted page deadlock (LP: #1754584) * zfs-linux 0.6.5.11-1ubuntu5 ADT test failure with linux 4.15.0-1.2 (LP: #1737761) - SAUCE: (noup) Update zfs to 0.6.5.11-1ubuntu3.2 * AT_BASE_PLATFORM in AUXV is absent on kernels available on Ubuntu 17.10 (LP: #1759312) - powerpc/64s: Fix NULL AT_BASE_PLATFORM when using DT CPU features * btrfs and tar sparse truncate archives (LP: #1757565) - Btrfs: move definition of the function btrfs_find_new_delalloc_bytes - Btrfs: fix reported number of inode blocks after buffered append writes * efifb broken on ThunderX-based Gigabyte nodes (LP: #1758375) - drivers/fbdev/efifb: Allow BAR to be moved instead of claiming it * Intel i40e PF reset due to incorrect MDD detection (continues...) (LP: #1723127) - i40e/i40evf: Account for frags split over multiple descriptors in check linearize * Fix an issue that when system in S3, USB keyboard can't wake up the system. (LP: #1759511) - ACPI / PM: Allow deeper wakeup power states with no _SxD nor _SxW * [8086:3e92] display becomes blank after S3 (LP: #1759188) - drm/i915: Apply Display WA #1183 on skl, kbl, and cfl * add audio kernel patches for Raven (LP: #1758364) - ALSA: hda: Add Raven PCI ID - ALSA: hda/realtek - Fix ALC700 family no sound issue * Cpu utilization showing system time for kvm guests (performance) (sysstat) (LP: #1755979) - KVM: PPC: Book3S HV: Fix guest time accounting with VIRT_CPU_ACCOUNTING_GEN * Kernel panic on a nfsroot system (LP: #1734327) - Revert "UBUNTU: SAUCE: LSM stacking: add stacking support to apparmor network hooks" - Revert "UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of the remaining blobs" * can't record sound via front headset port on the Dell Precision 3630 (LP: #1759088) - ALSA: hda/realtek - Fix Dell headset Mic can't record * speaker can't output sound anymore after system resumes from S3 on a lenovo machine with alc257 (LP: #1758829) - ALSA: hda/realtek - Fix speaker no sound after system resume * hda driver initialization takes too much time on the machine with coffeelake audio controller [8086:a348] (LP: #1758800) - ALSA: hda - Force polling mode on CFL for fixing codec communication * Let headset-mode initialization be called on Dell Precision 3930 (LP: #1757584) - ALSA: hda/realtek - Add headset mode support for Dell laptop * ubuntu_zram_smoke test will cause soft lockup on Artful ThunderX ARM64 (LP: #1755073) - SAUCE: crypto: thunderx_zip: Fix
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Verified artful-proposed. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20180404 root@ubuntu:~# uname -a Linux ubuntu 4.13.0-38-generic #43-Ubuntu SMP Wed Mar 14 15:20:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - root@ubuntu:~# dpkg --list | grep virtual ii linux-headers-virtual 4.13.0.38.41 amd64Virtual Linux kernel headers ii linux-image-virtual4.13.0.38.41 amd64Virtual Linux kernel image ii linux-virtual 4.13.0.38.41 amd64Minimal Generic Linux kernel and headers ii open-vm-tools 2:10.1.10-3ubuntu0.1 amd64Open VMware Tools for virtual machines hosted on VMware (CLI) root@ubuntu:~# apt update && apt install linux-image-virtual Hit:1 http://archive.ubuntu.com/ubuntu artful InRelease Hit:2 http://security.ubuntu.com/ubuntu artful-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu artful-updates InRelease Hit:4 http://archive.ubuntu.com/ubuntu artful-backports InRelease Get:5 http://archive.ubuntu.com/ubuntu artful-proposed InRelease [235 kB] Get:6 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 Packages [62.3 kB] Get:7 http://archive.ubuntu.com/ubuntu artful-proposed/main Translation-en [26.1 kB] Fetched 323 kB in 1s (206 kB/s) Reading package lists... Done Building dependency tree Reading state information... Done 29 packages can be upgraded. Run 'apt list --upgradable' to see them. Reading package lists... Done Building dependency tree Reading state information... Done The following package was automatically installed and is no longer required: grub-pc-bin Use 'apt autoremove' to remove it. The following additional packages will be installed: linux-headers-4.13.0-39 linux-headers-4.13.0-39-generic linux-headers-generic linux-headers-virtual linux-image-4.13.0-39-generic linux-virtual Suggested packages: fdutils linux-doc-4.13.0 | linux-source-4.13.0 linux-tools The following NEW packages will be installed: linux-headers-4.13.0-39 linux-headers-4.13.0-39-generic linux-image-4.13.0-39-generic The following packages will be upgraded: linux-headers-generic linux-headers-virtual linux-image-virtual linux-virtual 4 upgraded, 3 newly installed, 0 to remove and 25 not upgraded. Need to get 32.5 MB of archives. After this operation, 156 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-headers-4.13.0-39 all 4.13.0-39.44 [10.9 MB] Get:2 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-headers-4.13.0-39-generic amd64 4.13.0-39.44 [704 kB] Get:3 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-image-4.13.0-39-generic amd64 4.13.0-39.44 [20.9 MB] Get:4 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-virtual amd64 4.13.0.39.42 [1780 B] Get:5 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-image-virtual amd64 4.13.0.39.42 [2308 B] Get:6 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-headers-virtual amd64 4.13.0.39.42 [1766 B] Get:7 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 linux-headers-generic amd64 4.13.0.39.42 [2294 B] Fetched 32.5 MB in 5s (5459 kB/s) Selecting previously unselected package linux-headers-4.13.0-39. (Reading database ... 57609 files and directories currently installed.) Preparing to unpack .../0-linux-headers-4.13.0-39_4.13.0-39.44_all.deb ... Unpacking linux-headers-4.13.0-39 (4.13.0-39.44) ... Selecting previously unselected package linux-headers-4.13.0-39-generic. Preparing to unpack .../1-linux-headers-4.13.0-39-generic_4.13.0-39.44_amd64.deb ... Unpacking linux-headers-4.13.0-39-generic (4.13.0-39.44) ... Selecting previously unselected package linux-image-4.13.0-39-generic. Preparing to unpack .../2-linux-image-4.13.0-39-generic_4.13.0-39.44_amd64.deb ... Done. Unpacking linux-image-4.13.0-39-generic (4.13.0-39.44) ... Preparing to unpack .../3-linux-virtual_4.13.0.39.42_amd64.deb ... Unpacking linux-virtual (4.13.0.39.42) over (4.13.0.38.41) ... Preparing to unpack .../4-linux-image-virtual_4.13.0.39.42_amd64.deb ... Unpacking linux-image-virtual (4.13.0.39.42) over (4.13.0.38.41) ... Preparing to unpack .../5-linux-headers-virtual_4.13.0.39.42_amd64.deb ... Unpacking linux-headers-virtual
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag 'verification-needed-artful' to 'verification-failed- artful'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Fix Released Status in tar package in Ubuntu: New Status in linux source package in Artful: Fix Committed Status in tar source package in Artful: New Bug description: == SRU Justification == This bug causes btrfs and tar sparse to truncate archives. This bug has been fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of f48bf66b662e. These commits were cc'd to upstream stable and are already in Bionic. However, upstream 4.13 is EOL, so Artful never recieved the fixes, which is the reason for the SRU request. == Fixes == f48bf66b662e ("Btrfs: move definition of the function btrfs_find_new_delalloc_bytes") e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered append writes") == Regression Potential == Low. This fix was also sent and accepted to stable, so it has had additional upstream review. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia:
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Fix Released Status in tar package in Ubuntu: New Status in linux source package in Artful: Fix Committed Status in tar source package in Artful: New Bug description: == SRU Justification == This bug causes btrfs and tar sparse to truncate archives. This bug has been fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of f48bf66b662e. These commits were cc'd to upstream stable and are already in Bionic. However, upstream 4.13 is EOL, so Artful never recieved the fixes, which is the reason for the SRU request. == Fixes == f48bf66b662e ("Btrfs: move definition of the function btrfs_find_new_delalloc_bytes") e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered append writes") == Regression Potential == Low. This fix was also sent and accepted to stable, so it has had additional upstream review. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install)
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/342393 ** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/342394 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Fix Released Status in tar package in Ubuntu: New Status in linux source package in Artful: In Progress Status in tar source package in Artful: New Bug description: == SRU Justification == This bug causes btrfs and tar sparse to truncate archives. This bug has been fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of f48bf66b662e. These commits were cc'd to upstream stable and are already in Bionic. However, upstream 4.13 is EOL, so Artful never recieved the fixes, which is the reason for the SRU request. == Fixes == f48bf66b662e ("Btrfs: move definition of the function btrfs_find_new_delalloc_bytes") e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered append writes") == Regression Potential == Low. This fix was also sent and accepted to stable, so it has had additional upstream review. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or
Re: [Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Joseph, Thanks for providing the link to the mailing list post. That is very helpful. On Fri, Mar 23, 2018 at 4:15 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > SRU request submitted: > https://lists.ubuntu.com/archives/kernel-team/2018-March/090976.html > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1757565 > > Title: > btrfs and tar sparse truncate archives > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1757565/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Fix Released Status in tar package in Ubuntu: New Status in linux source package in Artful: In Progress Status in tar source package in Artful: New Bug description: == SRU Justification == This bug causes btrfs and tar sparse to truncate archives. This bug has been fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of f48bf66b662e. These commits were cc'd to upstream stable and are already in Bionic. However, upstream 4.13 is EOL, so Artful never recieved the fixes, which is the reason for the SRU request. == Fixes == f48bf66b662e ("Btrfs: move definition of the function btrfs_find_new_delalloc_bytes") e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered append writes") == Regression Potential == Low. This fix was also sent and accepted to stable, so it has had additional upstream review. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom,
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-March/090976.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Fix Released Status in tar package in Ubuntu: New Status in linux source package in Artful: In Progress Status in tar source package in Artful: New Bug description: == SRU Justification == This bug causes btrfs and tar sparse to truncate archives. This bug has been fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of f48bf66b662e. These commits were cc'd to upstream stable and are already in Bionic. However, upstream 4.13 is EOL, so Artful never recieved the fixes, which is the reason for the SRU request. == Fixes == f48bf66b662e ("Btrfs: move definition of the function btrfs_find_new_delalloc_bytes") e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered append writes") == Regression Potential == Low. This fix was also sent and accepted to stable, so it has had additional upstream review. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Description changed: + + == SRU Justification == + This bug causes btrfs and tar sparse to truncate archives. This bug has been + fixed in v4.15-rc3 by commit e3b8a4858566, which has a prereq commit of f48bf66b662e. + + These commits were cc'd to upstream stable and are already in Bionic. However, upstream + 4.13 is EOL, so Artful never recieved the fixes, which is the reason for + the SRU request. + + == Fixes == + f48bf66b662e ("Btrfs: move definition of the function btrfs_find_new_delalloc_bytes") + e3b8a4858566 ("Btrfs: fix reported number of inode blocks after buffered append writes") + + == Regression Potential == + Low. This fix was also sent and accepted to stable, so it has had additional upstream review. + + == Test Case == + A test kernel was built with these patches and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 - root@ubuntu:~# apt-cache policy linux-image-virtual + root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: - Installed: 4.13.0.37.40 - Candidate: 4.13.0.37.40 - Version table: - *** 4.13.0.37.40 500 - 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages - 100 /var/lib/dpkg/status - 4.13.0.16.17 500 - 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages + Installed: 4.13.0.37.40 + Candidate: 4.13.0.37.40 + Version table: + *** 4.13.0.37.40 500 + 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages + 100 /var/lib/dpkg/status + 4.13.0.16.17 500 + 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - - grep sda /proc/mounts + - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. - % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum + % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: - # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum + # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: - https://patchwork.kernel.org/patch/10151037/ - https://www.spinics.net/lists/linux-btrfs/msg56768.html + https://patchwork.kernel.org/patch/10151037/ + https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Mar 21 22:55 seq - crw-rw 1 root audio 116, 33 Mar 21 22:55 timer + total 0 + crw-rw 1 root audio 116, 1 Mar 21 22:55 seq + crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb']
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
That's great news. I'll SRU those two commits to the Artful kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Test kernel: GOOD root@ubuntu:~# cat /proc/version_signature Ubuntu 4.13.0-37.42~lp1757565-generic 4.13.13 root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX,
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
I built an Artful test kernel with commit e3b8a48. It also needed commit f48bf66b6 as a prereq. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1757565 Can you test this kernel and see if it resolves this bug? Note, to test this kernel, you need to install both the linux-image and linux-image-extra .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to:
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Yeah, rc2 was fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/341982 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
It looks like that commit landed in -rc3: git describe --contains e3b8a48 v4.15-rc3~3^2~11 However, -rc2 is good, correct? I'll have a look at the other btrfs commits in -rc2 and see if any stick out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Hmm, even though git describe returns that tag, it seem s-rc2 has that commit. I'll still build an Artful test kernel with that commit to see if it fixes the bug and figure out the tagging in the background. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Thanks for doing all the leg work. I'll build a test kernel with that commit and post it shortly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
This looks promising and landed in -rc2: Btrfs: fix reported number of inode blocks after buffered append writes https://www.spinics.net/lists/linux-btrfs/msg71274.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
v4.15-rc6: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc6-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - v4.15-rc4: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc4-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - v4.15-rc3: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc3-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - v4.14-rc2: GOOD root@ubuntu:~# uname -r 4.15.0-041500rc2-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - So, somewhere between rc1 and rc2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error:
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
That would indicate the fix is in from v4.15-rc2 -> 4.15 Final. I'll review the commits in that range, but there are probably thousands of them. It will help to narrow it down further. Could you test the 4.15 release candidates on the following page to find the last good kernel and first bad kernel: http://kernel.ubuntu.com/~kernel-ppa/mainline/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
v4.15 Final: GOOD root@ubuntu:~# uname -r 4.15.0-041500-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
@Scott, will that upstream commit make it so the kernel fix we are looking for is not required? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
On Thu, Mar 22, 2018 at 2:56 PM, Joseph Salisburywrote: > @Scott, will that upstream commit make it so the kernel fix we are > looking for is not required? This is a curtin workaround; we're not using the sparse flag when invoking tar; However, the bug/issue remains between tar and btrfs. Outside of curtin's use of it it, any users of btrfs with any "sparse" file detection are vulnerable. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1757565 > > Title: > btrfs and tar sparse truncate archives > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias:
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
Thanks for the info, Ryan. We know that 4.15-rc1 is BAD and 4.15.7 is GOOD, so the fix came in some where in between. Can you next test v4.15 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
v4.15.7: GOOD root@ubuntu:~# uname -r 4.15.7-041507-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
The Bionic 4.15.0-12 kernel is based off of upstream 4.15.7. Can you test that kernel as well? That will tell us if the fix in Bionic is an Ubuntu SAUCE patch or a 4.15 stable update. http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15.7/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
An upstream commit landed for this bug. To view that commit see the following URL: https://git.launchpad.net/curtin/commit/?id=bd40234f -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
v4.14-rc1: BAD ubuntu@ubuntu:~$ uname -r 4.14.0-041400rc1-generic ubuntu@ubuntu:~$ sudo bash root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - v4.14 Final: BAD root@ubuntu:~# uname -r 4.14.0-041400-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - v4.15-rc1: BAD root@ubuntu:~# uname -r 4.15.0-041500rc1-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - Bionic v4.15.0-12-generic: GOOD root@ubuntu:~# uname -r 4.15.0-12-generic root@ubuntu:~# mount /dev/sda /mnt root@ubuntu:~# grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 root@ubuntu:~# SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices:
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
I'd like to perform a "Reverse" bisect to figure out what commit fixes this bug. We need to identify the last kernel version that had the bug, and the first kernel version that fixed the bug. Can you test the following kernels and report back: v4.14-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc1/ v4.14 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 v4.15-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc1/ You don't have to test every kernel, just up until the first kernel that does not have the bug. Thanks in advance! ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Also affects: tar (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => Triaged ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Triaged Status in tar package in Ubuntu: New Status in linux source package in Artful: Triaged Status in tar source package in Artful: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions:
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/341780 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Confirmed Status in tar package in Ubuntu: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1757565] Re: btrfs and tar sparse truncate archives
** Also affects: tar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1757565 Title: btrfs and tar sparse truncate archives Status in linux package in Ubuntu: Confirmed Status in tar package in Ubuntu: New Bug description: root@ubuntu:~# lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 4.13.0.37.40 Candidate: 4.13.0.37.40 Version table: *** 4.13.0.37.40 500 500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 100 /var/lib/dpkg/status 4.13.0.16.17 500 500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages 3. Taring files into an archive are not truncated 4. Files included in tar are filled with NULLs To reproduce, run an Artful system with one spare disk: - mkfs.btrfs -f /dev/sda - mount /dev/sda /mnt - grep sda /proc/mounts /dev/sda /mnt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Then run this script which copies a 4MB binary to a btrfs filesystem, tars the directory up containing the binary; then untars to stdout and md5sum compares, showing it's different. % SPARSE="-S"; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 0ce8c4139740198926273853defcb12a - And now without the sparse flag: # SPARSE=""; rm -rf /mnt/tmp; md5sum /usr/bin/python3.6; mkdir -p /mnt/tmp; cp -a /usr/bin/python3.6 /mnt/tmp; tar -C /mnt/tmp $SPARSE -czf /mnt/test.tgz .; tar $SPARSE -xzf /mnt/test.tgz -O | md5sum e4121d2f3126b8c364bfa1aaa82371a3 /usr/bin/python3.6 e4121d2f3126b8c364bfa1aaa82371a3 - This has been reported to both gnu-tar and linux-btrfs; I'm not aware of an actual fix. Note that Xenial 4.4 kernels do not exhibit this behavior, and Bionic 4.15 kernel appears to be fixed as well though I'm not sure what the difference is. References: https://patchwork.kernel.org/patch/10151037/ https://www.spinics.net/lists/linux-btrfs/msg56768.html https://www.spinics.net/lists/linux-btrfs/msg57111.html ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-virtual 4.13.0.37.40 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 21 22:55 seq crw-rw 1 root audio 116, 33 Mar 21 22:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Wed Mar 21 23:08:05 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1757565/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp