Public bug reported:
This issue is different from bug 1809869.
Test failed with:
ERROR: unable to resolve -f
And:
btrfs receive: too many arguments
This patch does exist in Bionic kernel tree.
Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5
fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5
Btrfs: send, don't send rmdir for same target multiple times
When doing an incremental send, if we delete a directory that has N > 1
hardlinks for the same file and that file has the highest inode number
inside the directory contents, an incremental send would send N times an
rmdir operation against the directory. This made the btrfs receive command
fail on the second rmdir instruction, as the target directory didn't exist
anymore.
btrfs-progs v4.15.1
See http://btrfs.wiki.kernel.org for more information.
Performing full device TRIM /dev/loop0 (1.00GiB) ...
Label: (null)
UUID: b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
Node size: 16384
Sector size: 4096
Filesystem size: 1.00GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 51.19MiB
System: DUP 8.00MiB
SSD detected: no
Incompat features: extref, skinny-metadata
Number of devices: 1
Devices:
ID SIZE PATH
1 1.00GiB /dev/loop0
Create a readonly snapshot of
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
ERROR: unable to resolve -f
Create a readonly snapshot of
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
ERROR: unable to resolve -f
btrfs-progs v4.15.1
See http://btrfs.wiki.kernel.org for more information.
Performing full device TRIM /dev/loop0 (1.00GiB) ...
Label: (null)
UUID: e6351943-c767-4339-b662-609e80dae55b
Node size: 16384
Sector size: 4096
Filesystem size: 1.00GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 51.19MiB
System: DUP 8.00MiB
SSD detected: no
Incompat features: extref, skinny-metadata
Number of devices: 1
Devices:
ID SIZE PATH
1 1.00GiB /dev/loop0
btrfs receive: too many arguments
usage: btrfs receive [options] <mount>
btrfs receive --dump [options]
Receive subvolumes from a stream
Receives one or more subvolumes that were previously
sent with btrfs send. The received subvolumes are stored
into MOUNT.
The receive will fail in case the receiving subvolume
already exists. It will also fail in case a previously
received subvolume has been changed after it was received.
After receiving a subvolume, it is immediately set to
read-only.
-v increase verbosity about performed actions
-f FILE read the stream from FILE instead of stdin
-e terminate after receiving an <end cmd> marker in the
stream.
Without this option the receiver side terminates only in
case
of an error on end of file.
-C|--chroot confine the process to <mount> using chroot
-E|--max-errors NERR
terminate as soon as NERR errors occur while
stream processing commands from the stream.
Default value is 1. A value of 0 means no limit.
-m ROOTMOUNT the root mount point of the destination filesystem.
If /proc is not accessible, use this to tell us where
this file system is mounted.
--dump dump stream metadata, one line per operation,
does not require the MOUNT parameter
btrfs receive: too many arguments
usage: btrfs receive [options] <mount>
btrfs receive --dump [options]
Receive subvolumes from a stream
Receives one or more subvolumes that were previously
sent with btrfs send. The received subvolumes are stored
into MOUNT.
The receive will fail in case the receiving subvolume
already exists. It will also fail in case a previously
received subvolume has been changed after it was received.
After receiving a subvolume, it is immediately set to
read-only.
-v increase verbosity about performed actions
-f FILE read the stream from FILE instead of stdin
-e terminate after receiving an <end cmd> marker in the
stream.
Without this option the receiver side terminates only in
case
of an error on end of file.
-C|--chroot confine the process to <mount> using chroot
-E|--max-errors NERR
terminate as soon as NERR errors occur while
stream processing commands from the stream.
Default value is 1. A value of 0 means no limit.
-m ROOTMOUNT the root mount point of the destination filesystem.
If /proc is not accessible, use this to tell us where
this file system is mounted.
--dump dump stream metadata, one line per operation,
does not require the MOUNT parameter
incremental receive failed
FAIL: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 (ret=1)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Dec 20 18:17 seq
crw-rw---- 1 root audio 116, 33 Dec 20 18:17 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
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:
CurrentDmesg:
[566315.946699] cfg80211: Loading compiled-in X.509 certificates for
regulatory database
[566316.296863] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Date: Thu Dec 27 07:36:45 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8
RelatedPackageVersions:
linux-restricted-modules-4.15.0-43-generic N/A
linux-backports-modules-4.15.0-43-generic N/A
linux-firmware 1.173.2
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
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic uec-images
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1809872
Title:
29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed
on B
Status in linux package in Ubuntu:
New
Bug description:
This issue is different from bug 1809869.
Test failed with:
ERROR: unable to resolve -f
And:
btrfs receive: too many arguments
This patch does exist in Bionic kernel tree.
Invoking test 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5
fix 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5
Btrfs: send, don't send rmdir for same target multiple times
When doing an incremental send, if we delete a directory that has N > 1
hardlinks for the same file and that file has the highest inode number
inside the directory contents, an incremental send would send N times an
rmdir operation against the directory. This made the btrfs receive command
fail on the second rmdir instruction, as the target directory didn't exist
anymore.
btrfs-progs v4.15.1
See http://btrfs.wiki.kernel.org for more information.
Performing full device TRIM /dev/loop0 (1.00GiB) ...
Label: (null)
UUID: b9297d7d-f8b6-469e-b3c5-64ac1bf1e3d8
Node size: 16384
Sector size: 4096
Filesystem size: 1.00GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 51.19MiB
System: DUP 8.00MiB
SSD detected: no
Incompat features: extref, skinny-metadata
Number of devices: 1
Devices:
ID SIZE PATH
1 1.00GiB /dev/loop0
Create a readonly snapshot of
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap1'
ERROR: unable to resolve -f
Create a readonly snapshot of
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5' in
'/tmp/mnt-29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5/snap2'
ERROR: unable to resolve -f
btrfs-progs v4.15.1
See http://btrfs.wiki.kernel.org for more information.
Performing full device TRIM /dev/loop0 (1.00GiB) ...
Label: (null)
UUID: e6351943-c767-4339-b662-609e80dae55b
Node size: 16384
Sector size: 4096
Filesystem size: 1.00GiB
Block group profiles:
Data: single 8.00MiB
Metadata: DUP 51.19MiB
System: DUP 8.00MiB
SSD detected: no
Incompat features: extref, skinny-metadata
Number of devices: 1
Devices:
ID SIZE PATH
1 1.00GiB /dev/loop0
btrfs receive: too many arguments
usage: btrfs receive [options] <mount>
btrfs receive --dump [options]
Receive subvolumes from a stream
Receives one or more subvolumes that were previously
sent with btrfs send. The received subvolumes are stored
into MOUNT.
The receive will fail in case the receiving subvolume
already exists. It will also fail in case a previously
received subvolume has been changed after it was received.
After receiving a subvolume, it is immediately set to
read-only.
-v increase verbosity about performed actions
-f FILE read the stream from FILE instead of stdin
-e terminate after receiving an <end cmd> marker in the
stream.
Without this option the receiver side terminates only in
case
of an error on end of file.
-C|--chroot confine the process to <mount> using chroot
-E|--max-errors NERR
terminate as soon as NERR errors occur while
stream processing commands from the stream.
Default value is 1. A value of 0 means no limit.
-m ROOTMOUNT the root mount point of the destination filesystem.
If /proc is not accessible, use this to tell us where
this file system is mounted.
--dump dump stream metadata, one line per operation,
does not require the MOUNT parameter
btrfs receive: too many arguments
usage: btrfs receive [options] <mount>
btrfs receive --dump [options]
Receive subvolumes from a stream
Receives one or more subvolumes that were previously
sent with btrfs send. The received subvolumes are stored
into MOUNT.
The receive will fail in case the receiving subvolume
already exists. It will also fail in case a previously
received subvolume has been changed after it was received.
After receiving a subvolume, it is immediately set to
read-only.
-v increase verbosity about performed actions
-f FILE read the stream from FILE instead of stdin
-e terminate after receiving an <end cmd> marker in the
stream.
Without this option the receiver side terminates only in
case
of an error on end of file.
-C|--chroot confine the process to <mount> using chroot
-E|--max-errors NERR
terminate as soon as NERR errors occur while
stream processing commands from the stream.
Default value is 1. A value of 0 means no limit.
-m ROOTMOUNT the root mount point of the destination filesystem.
If /proc is not accessible, use this to tell us where
this file system is mounted.
--dump dump stream metadata, one line per operation,
does not require the MOUNT parameter
incremental receive failed
FAIL: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 (ret=1)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Dec 20 18:17 seq
crw-rw---- 1 root audio 116, 33 Dec 20 18:17 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
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:
CurrentDmesg:
[566315.946699] cfg80211: Loading compiled-in X.509 certificates for
regulatory database
[566316.296863] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
Date: Thu Dec 27 07:36:45 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic
root=UUID=2f68c627-8ab4-40d5-8c06-6563436d0f96 ro console=ttyS0,115200n8
RelatedPackageVersions:
linux-restricted-modules-4.15.0-43-generic N/A
linux-backports-modules-4.15.0-43-generic N/A
linux-firmware 1.173.2
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/1809872/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
