According to the btrfs document[1], adding another disk to the existing
btrfs file system is equivalent to create a raid with Raid 1 on Meta,
Raid 0 on Data group (mkfs.btrfs -m raid1 -d raid0).
So just like bug 1809870, we should be able to mount the drive with 'rw'
in degraded mode after wipe out the second disk (unless the data chunk
was destroyed, i.e. wipe out the first disk)
The degraded mount behaviour has been change since commit
4330e183c9537df20952d4a9ee142c536fb8ae54
** Changed in: ubuntu-kernel-tests
Status: New => In Progress
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Summary changed:
- f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed
on X
+ f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes failed
on X/B/C/D
** Changed in: ubuntu-kernel-tests
Importance: Undecided => Medium
--
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/1809886
Title:
f88ba6a2a44ee98e8d59654463dc157bb6d13c43 in ubuntu_btrfs_kernel_fixes
failed on X/B/C/D
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Confirmed
Bug description:
This patch exists in the Xenial tree.
Test failed with:
failed: degraded mount should have failed, but didn't
Invoking test f88ba6a2a44ee98e8d59654463dc157bb6d13c43
fix f88ba6a2a44ee98e8d59654463dc157bb6d13c43
Btrfs: skip submitting barrier for missing device
I got an error on v3.13:
BTRFS error (device sdf1) in write_all_supers:3378: errno=-5 IO failure
(errors while submitting device barriers.)
how to reproduce:
> mkfs.btrfs -f -d raid1 /dev/sdf1 /dev/sdf2
> wipefs -a /dev/sdf2
> mount -o degraded /dev/sdf1 /mnt
> btrfs balance start -f -sconvert=single -mconvert=single
-dconvert=single /mnt
The reason of the error is that barrier_all_devices() failed to submit
barrier to the missing device. However it is clear that we cannot do
anything on missing device, and also it is not necessary to care chunks
on the missing device.
This patch stops sending/waiting barrier if device is missing.
failed: degraded mount should have failed, but didn't
FAIL: f88ba6a2a44ee98e8d59654463dc157bb6d13c43 (ret=1)
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-164-generic 3.13.0-164.214
ProcVersionSignature: User Name 3.13.0-164.214-generic 3.13.11-ckt39
Uname: Linux 3.13.0-164-generic x86_64
AlsaDevices:
total 0
crw-rw---- 1 root audio 116, 1 Dec 27 10:11 seq
crw-rw---- 1 root audio 116, 33 Dec 27 10:11 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg: [ 29.063592] random: nonblocking pool is initialized
Date: Thu Dec 27 10:11:58 2018
IwConfig: Error: [Errno 2] No such file or directory: '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-3.13.0-164-generic
root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8
RelatedPackageVersions:
linux-restricted-modules-3.13.0-164-generic N/A
linux-backports-modules-3.13.0-164-generic N/A
linux-firmware 1.127.24
RfKill: Error: [Errno 2] No such file or directory: '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-kernel-tests/+bug/1809886/+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
