* Missing half of available space (resend)
@ 2015-12-09 5:02 David Hampton
2015-12-09 5:27 ` Chris Murphy
0 siblings, 1 reply; 12+ messages in thread
From: David Hampton @ 2015-12-09 5:02 UTC (permalink / raw)
To: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 2150 bytes --]
Hi all. I'm trying to figuring out why my btrfs file system doesn't
show all the available space. I currently have four 4TB drives set up
as a raid6 array, so I would expect to see a total available data size
slightly under 8TB (two drives for data + two drives for parity). The
'btrfs fi df' command consistently shows a total size of around 3TB, and
says that space is almost completely full. Here's my current system
information...
===
root@selene:~# uname -a
Linux selene.dhampton.net 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu
Oct 22 09:41:40 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
root@selene:~# btrfs --version
Btrfs v3.12
root@selene:~# btrfs fi show /video
Label: none uuid: 74a4c4fa-9e83-465a-850d-cc089ecd00f6
Total devices 4 FS bytes used 3.12TiB
devid 1 size 3.64TiB used 1.58TiB path /dev/vdb
devid 2 size 3.64TiB used 1.58TiB path /dev/vda
devid 3 size 3.64TiB used 1.58TiB path /dev/vdc
devid 4 size 3.64TiB used 1.58TiB path /dev/vdd
Btrfs v3.12
root@selene:~# btrfs fi df /video
Data, RAID6: total=3.15TiB, used=3.11TiB
System, RAID6: total=64.00MiB, used=352.00KiB
Metadata, RAID6: total=5.00GiB, used=3.73GiB
unknown, single: total=512.00MiB, used=1.07MiB
root@selene:~# df -h /video
Filesystem Size Used Avail Use% Mounted on
/dev/vda 15T 3.2T 8.3T 28% /video
===
I have tried issuing the command "btrfs filesystem resize
<id>:max /video" on each devid in the array, and also tried balancing
the array. None of these commands changed the indication that the file
system is almost full. I'm wondering if the problem is because this
file system began as a two drive raid1 array, and I later added the
other two drives and used the 'btrfs balance' command to convert to
raid6. Any suggestions on what I can try to get the 'btrfs fi df'
command to show me more available space? Did I forget a command when I
converted the raid1 array to raid6?
Alternatively, can I trust the numbers in the standard df command? The
'used' number seems right but the 'avail' number seems high.
If i can provide any more information to help figure out what's
happening, please ask.
Thanks.
David
[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 38759 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.19.0-32-generic (buildd@lgw01-43) (gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ) #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40 UTC 2015 (Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7)
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=b9fb1104-f681-4664-b0c3-b17db28d9d68 ro quiet splash vt.handoff=7
[ 0.000000] KERNEL supported cpus:
[ 0.000000] Intel GenuineIntel
[ 0.000000] AMD AuthenticAMD
[ 0.000000] Centaur CentaurHauls
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003fffdfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003fffe000-0x000000003fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: Red Hat KVM, BIOS 0.5.1 01/01/2011
[ 0.000000] Hypervisor detected: KVM
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] e820: last_pfn = 0x3fffe max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: write-back
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000080000000 mask 3FFF80000000 uncachable
[ 0.000000] 1 disabled
[ 0.000000] 2 disabled
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC
[ 0.000000] found SMP MP-table at [mem 0x000f1ff0-0x000f1fff] mapped at [ffff8800000f1ff0]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] Base memory trampoline at [ffff880000099000] 99000 size 24576
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] BRK [0x01fd4000, 0x01fd4fff] PGTABLE
[ 0.000000] BRK [0x01fd5000, 0x01fd5fff] PGTABLE
[ 0.000000] BRK [0x01fd6000, 0x01fd6fff] PGTABLE
[ 0.000000] init_memory_mapping: [mem 0x3fc00000-0x3fdfffff]
[ 0.000000] [mem 0x3fc00000-0x3fdfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x20000000-0x3fbfffff]
[ 0.000000] [mem 0x20000000-0x3fbfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x1fffffff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x1fffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x3fe00000-0x3fffdfff]
[ 0.000000] [mem 0x3fe00000-0x3fffdfff] page 4k
[ 0.000000] BRK [0x01fd7000, 0x01fd7fff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x3597e000-0x36cb6fff]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x00000000000F1E50 000014 (v00 BOCHS )
[ 0.000000] ACPI: RSDT 0x000000003FFFFA9B 000030 (v01 BOCHS BXPCRSDT 00000001 BXPC 00000001)
[ 0.000000] ACPI: FACP 0x000000003FFFF177 000074 (v01 BOCHS BXPCFACP 00000001 BXPC 00000001)
[ 0.000000] ACPI: DSDT 0x000000003FFFE040 001137 (v01 BXPC BXDSDT 00000001 INTL 20140926)
[ 0.000000] ACPI: FACS 0x000000003FFFE000 000040
[ 0.000000] ACPI: SSDT 0x000000003FFFF1EB 000838 (v01 BOCHS BXPCSSDT 00000001 BXPC 00000001)
[ 0.000000] ACPI: APIC 0x000000003FFFFA23 000078 (v01 BOCHS BXPCAPIC 00000001 BXPC 00000001)
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000003fffdfff]
[ 0.000000] NODE_DATA(0) allocated [mem 0x3fff9000-0x3fffdfff]
[ 0.000000] kvm-clock: Using msrs 4b564d01 and 4b564d00
[ 0.000000] kvm-clock: cpu 0, msr 0:3fff5001, primary cpu clock
[ 0.000000] [ffffea0000000000-ffffea0000ffffff] PMD -> [ffff88003e600000-ffff88003f5fffff] on node 0
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0x3fffdfff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009efff]
[ 0.000000] node 0: [mem 0x00100000-0x3fffdfff]
[ 0.000000] Initmem setup node 0 [mem 0x00001000-0x3fffdfff]
[ 0.000000] On node 0 totalpages: 262044
[ 0.000000] DMA zone: 64 pages used for memmap
[ 0.000000] DMA zone: 21 pages reserved
[ 0.000000] DMA zone: 3998 pages, LIFO batch:0
[ 0.000000] DMA32 zone: 4032 pages used for memmap
[ 0.000000] DMA32 zone: 258046 pages, LIFO batch:31
[ 0.000000] ACPI: PM-Timer IO Port: 0x608
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x00] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 0, version 17, address 0xfec00000, GSI 0-23
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level)
[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ5 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] ACPI: IRQ10 used by override.
[ 0.000000] ACPI: IRQ11 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] smpboot: Allowing 1 CPUs, 0 hotplug CPUs
[ 0.000000] PM: Registered nosave memory: [mem 0x00000000-0x00000fff]
[ 0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000effff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000f0000-0x000fffff]
[ 0.000000] e820: [mem 0x40000000-0xfeffbfff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on KVM
[ 0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:1 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 31 pages/cpu @ffff88003fc00000 s86144 r8192 d32640 u2097152
[ 0.000000] pcpu-alloc: s86144 r8192 d32640 u2097152 alloc=1*2097152
[ 0.000000] pcpu-alloc: [0] 0
[ 0.000000] KVM setup async PF for cpu 0
[ 0.000000] kvm-stealtime: cpu 0, msr 3fc0e100
[ 0.000000] Built 1 zonelists in Node order, mobility grouping on. Total pages: 257927
[ 0.000000] Policy zone: DMA32
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=b9fb1104-f681-4664-b0c3-b17db28d9d68 ro quiet splash vt.handoff=7
[ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
[ 0.000000] AGP: Checking aperture...
[ 0.000000] AGP: No AGP bridge found
[ 0.000000] Calgary: detecting Calgary via BIOS EBDA area
[ 0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
[ 0.000000] Memory: 995380K/1048176K available (7920K kernel code, 1174K rwdata, 3756K rodata, 1408K init, 1292K bss, 52796K reserved, 0K cma-reserved)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] Hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=1.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1
[ 0.000000] NR_IRQS:16640 nr_irqs:256 16
[ 0.000000] Offload RCU callbacks from all CPUs
[ 0.000000] Offload RCU callbacks from CPUs: 0.
[ 0.000000] vt handoff: transparent VT on vt#7
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] tsc: Detected 3499.996 MHz processor
[ 0.004000] Calibrating delay loop (skipped) preset value.. 6999.99 BogoMIPS (lpj=13999984)
[ 0.004000] pid_max: default: 32768 minimum: 301
[ 0.004000] ACPI: Core revision 20141107
[ 0.004000] ACPI: All ACPI Tables successfully acquired
[ 0.004000] Security Framework initialized
[ 0.004000] AppArmor: AppArmor initialized
[ 0.004000] Yama: becoming mindful.
[ 0.004000] Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
[ 0.004000] Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
[ 0.004000] Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.004000] Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
[ 0.004000] Initializing cgroup subsys memory
[ 0.004000] Initializing cgroup subsys devices
[ 0.004000] Initializing cgroup subsys freezer
[ 0.004000] Initializing cgroup subsys net_cls
[ 0.004000] Initializing cgroup subsys blkio
[ 0.004000] Initializing cgroup subsys perf_event
[ 0.004000] Initializing cgroup subsys net_prio
[ 0.004000] Initializing cgroup subsys hugetlb
[ 0.004000] mce: CPU supports 10 MCE banks
[ 0.004000] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
[ 0.004000] Last level dTLB entries: 4KB 0, 2MB 0, 4MB 0, 1GB 0
[ 0.010339] Freeing SMP alternatives memory: 32K (ffffffff81e87000 - ffffffff81e8f000)
[ 0.012839] ftrace: allocating 30021 entries in 118 pages
[ 0.024409] Enabling x2apic
[ 0.024420] Enabled x2apic
[ 0.024786] Switched APIC routing to physical x2apic.
[ 0.028851] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.028853] smpboot: CPU0: Intel Core i7 9xx (Nehalem Class Core i7) (fam: 06, model: 1a, stepping: 03)
[ 0.032000] Performance Events: unsupported p6 CPU model 26 no PMU driver, software events only.
[ 0.032956] KVM setup paravirtual spinlock
[ 0.033709] x86: Booted up 1 node, 1 CPUs
[ 0.033711] smpboot: Total of 1 processors activated (6999.99 BogoMIPS)
[ 0.033968] NMI watchdog: disabled (cpu0): hardware events not enabled
[ 0.035577] devtmpfs: initialized
[ 0.039347] evm: security.selinux
[ 0.039351] evm: security.SMACK64
[ 0.039353] evm: security.SMACK64EXEC
[ 0.039355] evm: security.SMACK64TRANSMUTE
[ 0.039356] evm: security.SMACK64MMAP
[ 0.039358] evm: security.ima
[ 0.039359] evm: security.capability
[ 0.039725] pinctrl core: initialized pinctrl subsystem
[ 0.040258] RTC time: 19:03:29, date: 12/07/15
[ 0.040436] NET: Registered protocol family 16
[ 0.040729] cpuidle: using governor ladder
[ 0.040734] cpuidle: using governor menu
[ 0.040814] ACPI: bus type PCI registered
[ 0.040817] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.041597] PCI: Using configuration type 1 for base access
[ 0.044696] ACPI: Added _OSI(Module Device)
[ 0.044700] ACPI: Added _OSI(Processor Device)
[ 0.044702] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.044704] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.047891] ACPI: Interpreter enabled
[ 0.047900] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20141107/hwxface-580)
[ 0.047906] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20141107/hwxface-580)
[ 0.047910] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20141107/hwxface-580)
[ 0.047914] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S4_] (20141107/hwxface-580)
[ 0.047922] ACPI: (supports S0 S5)
[ 0.047924] ACPI: Using IOAPIC for interrupt routing
[ 0.047943] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.051685] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.051692] acpi PNP0A03:00: _OSC: OS supports [ASPM ClockPM Segments MSI]
[ 0.051699] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.051798] acpi PNP0A03:00: fail to add MMCONFIG information, can't access extended PCI configuration space under this bridge.
[ 0.052248] acpiphp: Slot [3] registered
[ 0.052275] acpiphp: Slot [4] registered
[ 0.052314] acpiphp: Slot [6] registered
[ 0.052352] acpiphp: Slot [7] registered
[ 0.052388] acpiphp: Slot [8] registered
[ 0.052416] acpiphp: Slot [9] registered
[ 0.052441] acpiphp: Slot [10] registered
[ 0.052466] acpiphp: Slot [11] registered
[ 0.052491] acpiphp: Slot [12] registered
[ 0.052516] acpiphp: Slot [13] registered
[ 0.052548] acpiphp: Slot [14] registered
[ 0.052579] acpiphp: Slot [15] registered
[ 0.052615] acpiphp: Slot [16] registered
[ 0.052638] acpiphp: Slot [17] registered
[ 0.052661] acpiphp: Slot [18] registered
[ 0.052684] acpiphp: Slot [19] registered
[ 0.052712] acpiphp: Slot [20] registered
[ 0.052736] acpiphp: Slot [21] registered
[ 0.052765] acpiphp: Slot [22] registered
[ 0.052791] acpiphp: Slot [23] registered
[ 0.052814] acpiphp: Slot [24] registered
[ 0.052836] acpiphp: Slot [25] registered
[ 0.052859] acpiphp: Slot [26] registered
[ 0.052883] acpiphp: Slot [27] registered
[ 0.052912] acpiphp: Slot [28] registered
[ 0.052937] acpiphp: Slot [29] registered
[ 0.052960] acpiphp: Slot [30] registered
[ 0.052983] acpiphp: Slot [31] registered
[ 0.052994] PCI host bridge to bus 0000:00
[ 0.052999] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.053002] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.053004] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.053011] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.053014] pci_bus 0000:00: root bus resource [mem 0x40000000-0xfebfffff]
[ 0.053058] pci 0000:00:00.0: [8086:1237] type 00 class 0x060000
[ 0.053519] pci 0000:00:01.0: [8086:7000] type 00 class 0x060100
[ 0.054145] pci 0000:00:01.1: [8086:7010] type 00 class 0x010180
[ 0.076006] pci 0000:00:01.1: reg 0x20: [io 0xc4c0-0xc4cf]
[ 0.086205] pci 0000:00:01.1: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
[ 0.086209] pci 0000:00:01.1: legacy IDE quirk: reg 0x14: [io 0x03f6]
[ 0.086211] pci 0000:00:01.1: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
[ 0.086213] pci 0000:00:01.1: legacy IDE quirk: reg 0x1c: [io 0x0376]
[ 0.086397] pci 0000:00:01.3: [8086:7113] type 00 class 0x068000
[ 0.086793] pci 0000:00:01.3: quirk: [io 0x0600-0x063f] claimed by PIIX4 ACPI
[ 0.086803] pci 0000:00:01.3: quirk: [io 0x0700-0x070f] claimed by PIIX4 SMB
[ 0.087032] pci 0000:00:02.0: [1b36:0100] type 00 class 0x030000
[ 0.092021] pci 0000:00:02.0: reg 0x10: [mem 0xf4000000-0xf7ffffff]
[ 0.100017] pci 0000:00:02.0: reg 0x14: [mem 0xf8000000-0xfbffffff]
[ 0.108018] pci 0000:00:02.0: reg 0x18: [mem 0xfc0d4000-0xfc0d5fff]
[ 0.116023] pci 0000:00:02.0: reg 0x1c: [io 0xc400-0xc41f]
[ 0.140013] pci 0000:00:02.0: reg 0x30: [mem 0xfc0c0000-0xfc0cffff pref]
[ 0.140305] pci 0000:00:03.0: [10ec:8139] type 00 class 0x020000
[ 0.148004] pci 0000:00:03.0: reg 0x10: [io 0xc000-0xc0ff]
[ 0.152004] pci 0000:00:03.0: reg 0x14: [mem 0xfc0d6000-0xfc0d60ff]
[ 0.178385] pci 0000:00:03.0: reg 0x30: [mem 0xfc000000-0xfc03ffff pref]
[ 0.178622] pci 0000:00:04.0: [8086:2668] type 00 class 0x040300
[ 0.181221] pci 0000:00:04.0: reg 0x10: [mem 0xfc0d0000-0xfc0d3fff]
[ 0.196190] pci 0000:00:05.0: [8086:2934] type 00 class 0x0c0300
[ 0.207322] pci 0000:00:05.0: reg 0x20: [io 0xc420-0xc43f]
[ 0.212211] pci 0000:00:05.1: [8086:2935] type 00 class 0x0c0300
[ 0.222167] pci 0000:00:05.1: reg 0x20: [io 0xc440-0xc45f]
[ 0.227380] pci 0000:00:05.2: [8086:2936] type 00 class 0x0c0300
[ 0.238138] pci 0000:00:05.2: reg 0x20: [io 0xc460-0xc47f]
[ 0.242366] pci 0000:00:05.7: [8086:293a] type 00 class 0x0c0320
[ 0.244003] pci 0000:00:05.7: reg 0x10: [mem 0xfc0d7000-0xfc0d7fff]
[ 0.257192] pci 0000:00:06.0: [1af4:1003] type 00 class 0x078000
[ 0.260003] pci 0000:00:06.0: reg 0x10: [io 0xc480-0xc49f]
[ 0.266102] pci 0000:00:06.0: reg 0x14: [mem 0xfc0d8000-0xfc0d8fff]
[ 0.286392] pci 0000:00:07.0: [1af4:1002] type 00 class 0x00ff00
[ 0.289080] pci 0000:00:07.0: reg 0x10: [io 0xc4a0-0xc4bf]
[ 0.302303] pci 0000:00:08.0: [10ec:8139] type 00 class 0x020000
[ 0.306113] pci 0000:00:08.0: reg 0x10: [io 0xc100-0xc1ff]
[ 0.310109] pci 0000:00:08.0: reg 0x14: [mem 0xfc0d9000-0xfc0d90ff]
[ 0.332003] pci 0000:00:08.0: reg 0x30: [mem 0xfc040000-0xfc07ffff pref]
[ 0.332230] pci 0000:00:09.0: [10ec:8139] type 00 class 0x020000
[ 0.336003] pci 0000:00:09.0: reg 0x10: [io 0xc200-0xc2ff]
[ 0.340002] pci 0000:00:09.0: reg 0x14: [mem 0xfc0da000-0xfc0da0ff]
[ 0.362112] pci 0000:00:09.0: reg 0x30: [mem 0xfc080000-0xfc0bffff pref]
[ 0.362262] pci 0000:00:0a.0: [1af4:1001] type 00 class 0x010000
[ 0.366118] pci 0000:00:0a.0: reg 0x10: [io 0xc300-0xc33f]
[ 0.370157] pci 0000:00:0a.0: reg 0x14: [mem 0xfc0db000-0xfc0dbfff]
[ 0.392256] pci 0000:00:0b.0: [1af4:1001] type 00 class 0x010000
[ 0.396003] pci 0000:00:0b.0: reg 0x10: [io 0xc340-0xc37f]
[ 0.400004] pci 0000:00:0b.0: reg 0x14: [mem 0xfc0dc000-0xfc0dcfff]
[ 0.420275] pci 0000:00:0c.0: [1af4:1001] type 00 class 0x010000
[ 0.426115] pci 0000:00:0c.0: reg 0x10: [io 0xc380-0xc3bf]
[ 0.430112] pci 0000:00:0c.0: reg 0x14: [mem 0xfc0dd000-0xfc0ddfff]
[ 0.452160] pci 0000:00:0d.0: [1af4:1001] type 00 class 0x010000
[ 0.456003] pci 0000:00:0d.0: reg 0x10: [io 0xc3c0-0xc3ff]
[ 0.460003] pci 0000:00:0d.0: reg 0x14: [mem 0xfc0de000-0xfc0defff]
[ 0.480538] ACPI: PCI Interrupt Link [LNKA] (IRQs 5 *10 11)
[ 0.480596] ACPI: PCI Interrupt Link [LNKB] (IRQs 5 *10 11)
[ 0.480650] ACPI: PCI Interrupt Link [LNKC] (IRQs 5 10 *11)
[ 0.480699] ACPI: PCI Interrupt Link [LNKD] (IRQs 5 10 *11)
[ 0.480724] ACPI: PCI Interrupt Link [LNKS] (IRQs *9)
[ 0.480921] ACPI: Enabled 16 GPEs in block 00 to 0F
[ 0.481053] vgaarb: setting as boot device: PCI:0000:00:02.0
[ 0.481055] vgaarb: device added: PCI:0000:00:02.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.481057] vgaarb: loaded
[ 0.481058] vgaarb: bridge control possible 0000:00:02.0
[ 0.481265] SCSI subsystem initialized
[ 0.481323] libata version 3.00 loaded.
[ 0.481349] ACPI: bus type USB registered
[ 0.481380] usbcore: registered new interface driver usbfs
[ 0.481388] usbcore: registered new interface driver hub
[ 0.481396] usbcore: registered new device driver usb
[ 0.481524] PCI: Using ACPI for IRQ routing
[ 0.481525] PCI: pci_cache_line_size set to 64 bytes
[ 0.481690] e820: reserve RAM buffer [mem 0x0009fc00-0x0009ffff]
[ 0.481691] e820: reserve RAM buffer [mem 0x3fffe000-0x3fffffff]
[ 0.481779] NetLabel: Initializing
[ 0.481780] NetLabel: domain hash size = 128
[ 0.481780] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.481789] NetLabel: unlabeled traffic allowed by default
[ 0.481876] Switched to clocksource kvm-clock
[ 0.485471] AppArmor: AppArmor Filesystem Enabled
[ 0.485516] pnp: PnP ACPI init
[ 0.485804] pnp 00:00: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.485847] pnp 00:01: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.485875] pnp 00:02: Plug and Play ACPI device, IDs PNP0f13 (active)
[ 0.485901] pnp 00:03: [dma 2]
[ 0.485916] pnp 00:03: Plug and Play ACPI device, IDs PNP0700 (active)
[ 0.485975] pnp 00:04: Plug and Play ACPI device, IDs PNP0501 (active)
[ 0.486088] pnp: PnP ACPI: found 5 devices
[ 0.492173] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.492175] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.492176] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.492177] pci_bus 0000:00: resource 7 [mem 0x40000000-0xfebfffff]
[ 0.492196] NET: Registered protocol family 2
[ 0.492813] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.492839] TCP bind hash table entries: 8192 (order: 5, 131072 bytes)
[ 0.493566] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.495245] TCP: reno registered
[ 0.495251] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.495260] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.495565] NET: Registered protocol family 1
[ 0.495588] pci 0000:00:00.0: Limiting direct PCI/PCI transfers
[ 0.495624] pci 0000:00:01.0: PIIX3: Enabling Passive Release
[ 0.495653] pci 0000:00:01.0: Activating ISA DMA hang workarounds
[ 0.495706] pci 0000:00:02.0: Video device with shadowed ROM
[ 0.496293] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10
[ 0.499888] ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 11
[ 0.503135] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
[ 0.506020] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10
[ 0.508188] PCI: CLS 0 bytes, default 64
[ 0.508309] Trying to unpack rootfs image as initramfs...
[ 0.774378] Freeing initrd memory: 19684K (ffff88003597e000 - ffff880036cb7000)
[ 0.774545] microcode: CPU0 sig=0x106a3, pf=0x1, revision=0x1
[ 0.774582] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 0.774601] Scanning for low memory corruption every 60 seconds
[ 0.776365] futex hash table entries: 256 (order: 2, 16384 bytes)
[ 0.776384] Initialise system trusted keyring
[ 0.776421] audit: initializing netlink subsys (disabled)
[ 0.776446] audit: type=2000 audit(1449515030.489:1): initialized
[ 0.776817] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 0.779227] zpool: loaded
[ 0.779234] zbud: loaded
[ 0.779487] VFS: Disk quotas dquot_6.5.2
[ 0.779551] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[ 0.780377] fuse init (API version 7.23)
[ 0.780602] Key type big_key registered
[ 0.780891] Key type asymmetric registered
[ 0.780896] Asymmetric key parser 'x509' registered
[ 0.780957] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.780997] io scheduler noop registered
[ 0.781002] io scheduler deadline registered (default)
[ 0.781053] io scheduler cfq registered
[ 0.781212] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 0.781238] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 0.781295] vesafb: mode is 640x480x32, linelength=2560, pages=0
[ 0.781297] vesafb: scrolling: redraw
[ 0.781300] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 0.781390] vesafb: framebuffer at 0xf4000000, mapped to 0xffffc90000200000, using 1216k, total 1216k
[ 0.781551] Console: switching to colour frame buffer device 80x30
[ 0.781565] fb0: VESA VGA frame buffer device
[ 0.781595] intel_idle: does not run on family 6 model 26
[ 0.781705] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input0
[ 0.781711] ACPI: Power Button [PWRF]
[ 0.781946] GHES: HEST is not enabled!
[ 0.798190] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[ 0.820468] 00:04: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
[ 0.912272] Linux agpgart interface v0.103
[ 0.913159] brd: module loaded
[ 0.913578] loop: module loaded
[ 0.924119] vda: unknown partition table
[ 0.938315] vdb: unknown partition table
[ 0.958461] vdc: unknown partition table
[ 0.966275] vdd: unknown partition table
[ 0.966612] ata_piix 0000:00:01.1: version 2.13
[ 0.970163] scsi host0: ata_piix
[ 0.970321] scsi host1: ata_piix
[ 0.970379] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc4c0 irq 14
[ 0.970382] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc4c8 irq 15
[ 0.970525] libphy: Fixed MDIO Bus: probed
[ 0.970530] tun: Universal TUN/TAP device driver, 1.6
[ 0.970532] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 0.971087] PPP generic driver version 2.4.2
[ 0.971188] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.971194] ehci-pci: EHCI PCI platform driver
[ 0.973369] ehci-pci 0000:00:05.7: EHCI Host Controller
[ 0.973382] ehci-pci 0000:00:05.7: new USB bus registered, assigned bus number 1
[ 0.973559] ehci-pci 0000:00:05.7: irq 10, io mem 0xfc0d7000
[ 0.984090] ehci-pci 0000:00:05.7: USB 2.0 started, EHCI 1.00
[ 0.984167] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.984171] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.984173] usb usb1: Product: EHCI Host Controller
[ 0.984176] usb usb1: Manufacturer: Linux 3.19.0-32-generic ehci_hcd
[ 0.984178] usb usb1: SerialNumber: 0000:00:05.7
[ 0.984311] hub 1-0:1.0: USB hub found
[ 0.984318] hub 1-0:1.0: 6 ports detected
[ 0.984501] ehci-platform: EHCI generic platform driver
[ 0.984513] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 0.984518] ohci-pci: OHCI PCI platform driver
[ 0.984533] ohci-platform: OHCI generic platform driver
[ 0.984541] uhci_hcd: USB Universal Host Controller Interface driver
[ 0.986961] uhci_hcd 0000:00:05.0: UHCI Host Controller
[ 0.986969] uhci_hcd 0000:00:05.0: new USB bus registered, assigned bus number 2
[ 0.987005] uhci_hcd 0000:00:05.0: detected 2 ports
[ 0.987060] uhci_hcd 0000:00:05.0: irq 10, io base 0x0000c420
[ 0.987131] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.987133] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.987135] usb usb2: Product: UHCI Host Controller
[ 0.987137] usb usb2: Manufacturer: Linux 3.19.0-32-generic uhci_hcd
[ 0.987139] usb usb2: SerialNumber: 0000:00:05.0
[ 0.987239] hub 2-0:1.0: USB hub found
[ 0.987244] hub 2-0:1.0: 2 ports detected
[ 0.989990] uhci_hcd 0000:00:05.1: UHCI Host Controller
[ 0.989999] uhci_hcd 0000:00:05.1: new USB bus registered, assigned bus number 3
[ 0.990017] uhci_hcd 0000:00:05.1: detected 2 ports
[ 0.990075] uhci_hcd 0000:00:05.1: irq 11, io base 0x0000c440
[ 0.990141] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.990144] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.990146] usb usb3: Product: UHCI Host Controller
[ 0.990147] usb usb3: Manufacturer: Linux 3.19.0-32-generic uhci_hcd
[ 0.990149] usb usb3: SerialNumber: 0000:00:05.1
[ 0.990251] hub 3-0:1.0: USB hub found
[ 0.990256] hub 3-0:1.0: 2 ports detected
[ 0.993143] uhci_hcd 0000:00:05.2: UHCI Host Controller
[ 0.993152] uhci_hcd 0000:00:05.2: new USB bus registered, assigned bus number 4
[ 0.993180] uhci_hcd 0000:00:05.2: detected 2 ports
[ 0.993244] uhci_hcd 0000:00:05.2: irq 11, io base 0x0000c460
[ 0.993330] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 0.993333] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.993336] usb usb4: Product: UHCI Host Controller
[ 0.993338] usb usb4: Manufacturer: Linux 3.19.0-32-generic uhci_hcd
[ 0.993340] usb usb4: SerialNumber: 0000:00:05.2
[ 0.993489] hub 4-0:1.0: USB hub found
[ 0.993498] hub 4-0:1.0: 2 ports detected
[ 0.993718] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12
[ 0.994489] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 0.994496] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 0.994632] mousedev: PS/2 mouse device common for all mice
[ 0.994910] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input1
[ 0.995165] rtc_cmos 00:00: RTC can wake from S4
[ 0.995441] rtc_cmos 00:00: rtc core: registered rtc_cmos as rtc0
[ 0.995535] rtc_cmos 00:00: alarms up to one day, 114 bytes nvram
[ 0.995545] i2c /dev entries driver
[ 0.995617] device-mapper: uevent: version 1.0.3
[ 0.995680] device-mapper: ioctl: 4.29.0-ioctl (2014-10-28) initialised: dm-devel@redhat.com
[ 0.995702] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.995790] PCCT header not found.
[ 0.995792] ACPI PCC probe failed.
[ 0.995893] TCP: cubic registered
[ 0.996020] NET: Registered protocol family 10
[ 0.996188] NET: Registered protocol family 17
[ 0.996203] Key type dns_resolver registered
[ 0.996427] Loading compiled-in X.509 certificates
[ 0.997356] Loaded X.509 cert 'Magrathea: Glacier signing key: 0c8befe0c1e289e4d8990926117ada3bdfeb419c'
[ 0.997377] registered taskstats version 1
[ 0.999020] Key type trusted registered
[ 1.001878] Key type encrypted registered
[ 1.001886] AppArmor: AppArmor sha1 policy hashing enabled
[ 1.001899] ima: No TPM chip found, activating TPM-bypass!
[ 1.001919] evm: HMAC attrs: 0x1
[ 1.002343] Magic number: 11:92:91
[ 1.002461] rtc_cmos 00:00: setting system clock to 2015-12-07 19:03:30 UTC (1449515010)
[ 1.002512] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 1.002514] EDD information not available.
[ 1.002563] PM: Hibernation image not present or could not be loaded.
[ 1.124961] ata1.00: ATA-7: QEMU HARDDISK, 1.5.3, max UDMA/100
[ 1.124968] ata1.00: 104857600 sectors, multi 16: LBA48
[ 1.124975] ata1.01: ATAPI: QEMU DVD-ROM, 1.5.3, max UDMA/100
[ 1.125621] ata1.00: configured for MWDMA2
[ 1.126109] ata1.01: configured for MWDMA2
[ 1.126462] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK 3 PQ: 0 ANSI: 5
[ 1.126733] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 1.127150] scsi 0:0:1:0: CD-ROM QEMU QEMU DVD-ROM 1.5. PQ: 0 ANSI: 5
[ 1.132733] sd 0:0:0:0: [sda] 104857600 512-byte logical blocks: (53.6 GB/50.0 GiB)
[ 1.132749] sr 0:0:1:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray
[ 1.132769] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 1.132937] sr 0:0:1:0: Attached scsi CD-ROM sr0
[ 1.133165] sr 0:0:1:0: Attached scsi generic sg1 type 5
[ 1.133425] sd 0:0:0:0: [sda] Write Protect is off
[ 1.133429] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 1.133447] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.136257] sda: sda1 sda2 < sda5 >
[ 1.136590] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.136975] Freeing unused kernel memory: 1408K (ffffffff81d27000 - ffffffff81e87000)
[ 1.136978] Write protecting the kernel read-only data: 12288k
[ 1.137265] Freeing unused kernel memory: 260K (ffff8800017bf000 - ffff880001800000)
[ 1.137433] Freeing unused kernel memory: 340K (ffff880001bab000 - ffff880001c00000)
[ 1.156190] systemd-udevd[104]: starting version 204
[ 1.193651] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004)
[ 1.204385] FDC 0 is a S82078B
[ 1.218085] 8139cp 0000:00:03.0 eth0: RTL-8139C+ at 0xffffc900001e2000, 52:54:00:fb:b3:5c, IRQ 11
[ 1.223131] 8139cp 0000:00:08.0 eth1: RTL-8139C+ at 0xffffc900001e6000, 52:54:00:26:fd:fb, IRQ 10
[ 1.238342] 8139cp 0000:00:09.0 eth2: RTL-8139C+ at 0xffffc900001ea000, 52:54:00:c9:4b:3b, IRQ 10
[ 1.246561] 8139too: 8139too Fast Ethernet driver 0.9.28
[ 1.416012] raid6: sse2x1 9606 MB/s
[ 1.484007] raid6: sse2x2 13948 MB/s
[ 1.552006] raid6: sse2x4 16002 MB/s
[ 1.552008] raid6: using algorithm sse2x4 (16002 MB/s)
[ 1.552009] raid6: using ssse3x2 recovery algorithm
[ 1.553215] xor: measuring software checksum speed
[ 1.592005] prefetch64-sse: 17929.000 MB/sec
[ 1.632003] generic_sse: 16612.000 MB/sec
[ 1.632004] xor: using function: prefetch64-sse (17929.000 MB/sec)
[ 1.669084] Btrfs loaded
[ 1.792338] BTRFS: device fsid 74a4c4fa-9e83-465a-850d-cc089ecd00f6 devid 2 transid 98119 /dev/vda
[ 1.793210] BTRFS: device fsid 74a4c4fa-9e83-465a-850d-cc089ecd00f6 devid 1 transid 98119 /dev/vdb
[ 1.794161] BTRFS: device fsid 74a4c4fa-9e83-465a-850d-cc089ecd00f6 devid 3 transid 98119 /dev/vdc
[ 1.795205] BTRFS: device fsid 74a4c4fa-9e83-465a-850d-cc089ecd00f6 devid 4 transid 98119 /dev/vdd
[ 1.814134] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
[ 1.909817] random: init urandom read with 64 bits of entropy available
[ 1.945395] init: plymouth-upstart-bridge main process (157) terminated with status 1
[ 1.945402] init: plymouth-upstart-bridge main process ended, respawning
[ 1.959224] init: plymouth-upstart-bridge main process (167) terminated with status 1
[ 1.959233] init: plymouth-upstart-bridge main process ended, respawning
[ 2.175756] Adding 1045500k swap on /dev/sda5. Priority:-1 extents:1 across:1045500k FS
[ 2.303629] systemd-udevd[292]: starting version 204
[ 2.367261] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ 2.384977] input: ImExPS/2 Generic Explorer Mouse as /devices/platform/i8042/serio1/input/input3
[ 2.408687] lp: driver loaded but no devices found
[ 2.524279] BTRFS info (device vdd): disk space caching is enabled
[ 2.533278] piix4_smbus 0000:00:01.3: SMBus Host Controller at 0x700, revision 0
[ 2.658899] [drm] Initialized drm 1.1.0 20060810
[ 2.661742] audit: type=1400 audit(1449515012.154:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=399 comm="apparmor_parser"
[ 2.661746] audit: type=1400 audit(1449515012.154:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=399 comm="apparmor_parser"
[ 2.661748] audit: type=1400 audit(1449515012.154:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=399 comm="apparmor_parser"
[ 2.662061] audit: type=1400 audit(1449515012.154:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=399 comm="apparmor_parser"
[ 2.662065] audit: type=1400 audit(1449515012.154:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=399 comm="apparmor_parser"
[ 2.663823] audit: type=1400 audit(1449515012.154:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=399 comm="apparmor_parser"
[ 2.678921] audit: type=1400 audit(1449515012.170:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ntpd" pid=413 comm="apparmor_parser"
[ 2.727964] 8139cp 0000:00:03.0 eth0: link up, 100Mbps, full-duplex, lpa 0x05E1
[ 2.757807] 8139cp 0000:00:08.0 eth1: link up, 100Mbps, full-duplex, lpa 0x05E1
[ 2.768710] 8139cp 0000:00:09.0 eth2: link up, 100Mbps, full-duplex, lpa 0x05E1
[ 2.821692] random: nonblocking pool is initialized
[ 3.167752] FS-Cache: Loaded
[ 3.168357] [drm] Device Version 0.0
[ 3.168359] [drm] Compression level 0 log level 0
[ 3.168360] [drm] Currently using mode #0, list at 0x488
[ 3.168360] [drm] 12286 io pages at offset 0x1000000
[ 3.168361] [drm] 16777216 byte draw area at offset 0x0
[ 3.168362] [drm] RAM header offset: 0x3ffe000
[ 3.168362] [drm] rom modes offset 0x488 for 128 modes
[ 3.180730] [TTM] Zone kernel: Available graphics memory: 508552 kiB
[ 3.180731] [TTM] Initializing pool allocator
[ 3.180735] [TTM] Initializing DMA pool allocator
[ 3.180742] [drm] qxl: 16M of VRAM memory size
[ 3.180743] [drm] qxl: 63M of IO pages memory ready (VRAM domain)
[ 3.180743] [drm] qxl: 64M of Surface memory size
[ 3.194516] RPC: Registered named UNIX socket transport module.
[ 3.194518] RPC: Registered udp transport module.
[ 3.194519] RPC: Registered tcp transport module.
[ 3.194519] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 3.231286] FS-Cache: Netfs 'nfs' registered for caching
[ 3.280673] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 3.315281] [drm] main mem slot 1 [f4000000,3ffe000]
[ 3.315283] [drm] surface mem slot 2 [f8000000,4000000]
[ 3.320159] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.320161] [drm] No driver support for vblank timestamp query.
[ 3.320853] [drm] fb mappable at 0xF4000000, size 3145728
[ 3.320855] [drm] fb: depth 24, pitch 4096, width 1024, height 768
[ 3.320857] checking generic (f4000000 130000) vs hw (f4000000 1000000)
[ 3.320858] fb: switching to qxldrmfb from VESA VGA
[ 3.320874] Console: switching to colour dummy device 80x25
[ 3.333711] fbcon: qxldrmfb (fb0) is primary device
[ 3.333724] Console: switching to colour frame buffer device 128x48
[ 3.333734] qxl 0000:00:02.0: fb0: qxldrmfb frame buffer device
[ 3.333736] qxl 0000:00:02.0: registered panic notifier
[ 3.333739] [drm] Initialized qxl 0.1.0 20120117 for 0000:00:02.0 on minor 0
[ 3.718614] init: avahi-cups-reload main process (793) terminated with status 1
[ 3.939374] ppdev: user-space parallel port driver
[ 4.048220] init: failsafe main process (838) killed by TERM signal
[ 4.104131] sound hdaudioC0D0: autoconfig: line_outs=1 (0x3/0x0/0x0/0x0/0x0) type:line
[ 4.104149] sound hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 4.104151] sound hdaudioC0D0: hp_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 4.104152] sound hdaudioC0D0: mono: mono_out=0x0
[ 4.104153] sound hdaudioC0D0: inputs:
[ 4.104154] sound hdaudioC0D0: Line=0x5
[ 4.200342] init: Failed to obtain startpar-bridge instance: Unknown parameter: INSTANCE
[ 4.759928] audit: type=1400 audit(1449515014.250:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/lightdm/lightdm-guest-session" pid=1062 comm="apparmor_parser"
[ 4.759933] audit: type=1400 audit(1449515014.250:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="chromium" pid=1062 comm="apparmor_parser"
[ 5.596798] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
[ 5.597664] NFSD: starting 90-second grace period (net ffffffff81cda040)
[ 6.222391] init: plymouth-upstart-bridge main process ended, respawning
[ 6.232735] init: plymouth-upstart-bridge main process ended, respawning
[ 7.428820] init: plymouth-stop pre-start process (1672) terminated with status 1
[ 11.282352] NFS: Registering the id_resolver key type
[ 11.282366] Key type id_resolver registered
[ 11.282368] Key type id_legacy registered
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 5:02 Missing half of available space (resend) David Hampton
@ 2015-12-09 5:27 ` Chris Murphy
2015-12-09 6:30 ` David Hampton
0 siblings, 1 reply; 12+ messages in thread
From: Chris Murphy @ 2015-12-09 5:27 UTC (permalink / raw)
To: David Hampton; +Cc: Btrfs BTRFS
On Tue, Dec 8, 2015 at 10:02 PM, David Hampton
<mailinglists@love2code.net> wrote:
> The
> 'btrfs fi df' command consistently shows a total size of around 3TB, and
> says that space is almost completely full.
and
> root@selene:~# btrfs fi df /video
> Data, RAID6: total=3.15TiB, used=3.11TiB
The "total=3.15TiB" means "there's a total of 3.15TiB allocated for
data chunks using raid6 profile" and of that 3.11TiB is used.
btrfs fi df doesn't ever show how much is free or available. You can
get an estimate of that by using 'btrfs fi usage' instead.
> root@selene:~# df -h /video
> Filesystem Size Used Avail Use% Mounted on
> /dev/vda 15T 3.2T 8.3T 28% /video
That's about right although it seems it's slightly overestimating the
available free space.
--
Chris Murphy
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 5:27 ` Chris Murphy
@ 2015-12-09 6:30 ` David Hampton
2015-12-09 16:48 ` Duncan
0 siblings, 1 reply; 12+ messages in thread
From: David Hampton @ 2015-12-09 6:30 UTC (permalink / raw)
To: Chris Murphy; +Cc: Btrfs BTRFS
On Tue, 2015-12-08 at 22:27 -0700, Chris Murphy wrote:
> On Tue, Dec 8, 2015 at 10:02 PM, David Hampton
> <mailinglists@love2code.net> wrote:
> > The
> > 'btrfs fi df' command consistently shows a total size of around
> > 3TB, and says that space is almost completely full.
>
> and
>
>
> > root@selene:~# btrfs fi df /video
> > Data, RAID6: total=3.15TiB, used=3.11TiB
>
> The "total=3.15TiB" means "there's a total of 3.15TiB allocated for
> data chunks using raid6 profile" and of that 3.11TiB is used.
>
> btrfs fi df doesn't ever show how much is free or available.
I think I get it. The numbers in the 'df' command don't show the total
number of chunks that exist, only the subset of those chunks that have
been allocated to something.
> You can get an estimate of that by using 'btrfs fi usage' instead.
Seems I need to upgrade my tools. That command was added in 3.18 and I
only have the 3.12 tools.
> > root@selene:~# df -h /video
> > Filesystem Size Used Avail Use% Mounted on
> > /dev/vda 15T 3.2T 8.3T 28% /video
>
> That's about right although it seems it's slightly overestimating the
> available free space.
Thanks. Make me feel a lot better.
David
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 6:30 ` David Hampton
@ 2015-12-09 16:48 ` Duncan
2015-12-09 17:28 ` David Hampton
0 siblings, 1 reply; 12+ messages in thread
From: Duncan @ 2015-12-09 16:48 UTC (permalink / raw)
To: linux-btrfs
David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
> Seems I need to upgrade my tools. That command was added in 3.18 and I
> only have the 3.12 tools.
Definitely so, especially because you're running raid6, which wasn't
stable until 4.1 for both kernel and userspace. 3.12? I guess it did
have the very basic raid56 support, but it's definitely nothing I'd
trust, at that old not for btrfs in general, but FOR SURE not raid56.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 16:48 ` Duncan
@ 2015-12-09 17:28 ` David Hampton
2015-12-09 19:39 ` Chris Murphy
0 siblings, 1 reply; 12+ messages in thread
From: David Hampton @ 2015-12-09 17:28 UTC (permalink / raw)
To: linux-btrfs
On Wed, 2015-12-09 at 16:48 +0000, Duncan wrote:
> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
>
> > Seems I need to upgrade my tools. That command was added in 3.18 and I
> > only have the 3.12 tools.
>
> Definitely so, especially because you're running raid6, which wasn't
> stable until 4.1 for both kernel and userspace. 3.12? I guess it did
> have the very basic raid56 support, but it's definitely nothing I'd
> trust, at that old not for btrfs in general, but FOR SURE not raid56.
I've upgraded to the 4.2.0 kernel and the 4.0 btrfs-tools package.
These are the latest that Ubuntu has packaged for 15.10, and I've pulled
them into my 14.10 based release. Is this recent enough, or do I need
to try the 4.3 kernel/tools build from the active development tree (that
will eventually become 16.04)?
David
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 17:28 ` David Hampton
@ 2015-12-09 19:39 ` Chris Murphy
2015-12-09 19:56 ` Gareth Pye
2015-12-10 3:27 ` Duncan
0 siblings, 2 replies; 12+ messages in thread
From: Chris Murphy @ 2015-12-09 19:39 UTC (permalink / raw)
To: David Hampton; +Cc: Btrfs BTRFS
On Wed, Dec 9, 2015 at 10:28 AM, David Hampton
<mailinglists@dhampton.net> wrote:
> On Wed, 2015-12-09 at 16:48 +0000, Duncan wrote:
>> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
>>
>> > Seems I need to upgrade my tools. That command was added in 3.18 and I
>> > only have the 3.12 tools.
>>
>> Definitely so, especially because you're running raid6, which wasn't
>> stable until 4.1 for both kernel and userspace. 3.12? I guess it did
>> have the very basic raid56 support, but it's definitely nothing I'd
>> trust, at that old not for btrfs in general, but FOR SURE not raid56.
>
> I've upgraded to the 4.2.0 kernel and the 4.0 btrfs-tools package.
I think btrfs-progs 4.0 has a mkfs bug in it (or was that 4.0.1?)
Anyway, even that is still old in Btrfs terms. I think Ubuntu needs to
do better than this, or just acknowledge Btrfs is not supported, don't
include btrfs-progs at all by default, and stop making it an install
time option.
> These are the latest that Ubuntu has packaged for 15.10, and I've pulled
> them into my 14.10 based release. Is this recent enough, or do I need
> to try the 4.3 kernel/tools build from the active development tree (that
> will eventually become 16.04)?
It's probably fine day to day, but if you ever were to need btrfs
check or repair, you'd want the current version no matter what. There
are just too many bug fixes and enhancements happening to not make
that effort. You kinda have to understand that you're effectively
testing Btrfs by using raid56. It is stabilizing, but it can hardly be
called stable or even feature complete seeing as there are all sorts
of missing failure notifications.
More than anything else you need to be willing to lose everything on
this volume, without further notice, i.e. you need a backup strategy
that you're prepared to use without undue stress. If you can't do
that, you need to look at another arrangement. Both LVM and mdadm
raid6 + XFS are more stable.
--
Chris Murphy
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 19:39 ` Chris Murphy
@ 2015-12-09 19:56 ` Gareth Pye
2015-12-09 21:26 ` David Hampton
2015-12-09 21:28 ` Chris Murphy
2015-12-10 3:27 ` Duncan
1 sibling, 2 replies; 12+ messages in thread
From: Gareth Pye @ 2015-12-09 19:56 UTC (permalink / raw)
To: Chris Murphy; +Cc: David Hampton, Btrfs BTRFS
I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
(which counts as a long time when it's only for people happy to
upgrade every 6 months).
The kernel ppa's builds tend to run fine on the latest LTS & regular
releases, although they can cause issues (I've had some fun with
nvidia drivers at times). That ppa will get you to 4.3 or 4.4rc4.
On Thu, Dec 10, 2015 at 6:39 AM, Chris Murphy <lists@colorremedies.com> wrote:
> On Wed, Dec 9, 2015 at 10:28 AM, David Hampton
> <mailinglists@dhampton.net> wrote:
>> On Wed, 2015-12-09 at 16:48 +0000, Duncan wrote:
>>> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
>>>
>>> > Seems I need to upgrade my tools. That command was added in 3.18 and I
>>> > only have the 3.12 tools.
>>>
>>> Definitely so, especially because you're running raid6, which wasn't
>>> stable until 4.1 for both kernel and userspace. 3.12? I guess it did
>>> have the very basic raid56 support, but it's definitely nothing I'd
>>> trust, at that old not for btrfs in general, but FOR SURE not raid56.
>>
>> I've upgraded to the 4.2.0 kernel and the 4.0 btrfs-tools package.
>
> I think btrfs-progs 4.0 has a mkfs bug in it (or was that 4.0.1?)
> Anyway, even that is still old in Btrfs terms. I think Ubuntu needs to
> do better than this, or just acknowledge Btrfs is not supported, don't
> include btrfs-progs at all by default, and stop making it an install
> time option.
>
>
>> These are the latest that Ubuntu has packaged for 15.10, and I've pulled
>> them into my 14.10 based release. Is this recent enough, or do I need
>> to try the 4.3 kernel/tools build from the active development tree (that
>> will eventually become 16.04)?
>
> It's probably fine day to day, but if you ever were to need btrfs
> check or repair, you'd want the current version no matter what. There
> are just too many bug fixes and enhancements happening to not make
> that effort. You kinda have to understand that you're effectively
> testing Btrfs by using raid56. It is stabilizing, but it can hardly be
> called stable or even feature complete seeing as there are all sorts
> of missing failure notifications.
>
> More than anything else you need to be willing to lose everything on
> this volume, without further notice, i.e. you need a backup strategy
> that you're prepared to use without undue stress. If you can't do
> that, you need to look at another arrangement. Both LVM and mdadm
> raid6 + XFS are more stable.
>
>
> --
> Chris Murphy
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gareth Pye - blog.cerberos.id.au
Level 2 MTG Judge, Melbourne, Australia
"Dear God, I would like to file a bug report"
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 19:56 ` Gareth Pye
@ 2015-12-09 21:26 ` David Hampton
2015-12-09 21:28 ` Chris Murphy
1 sibling, 0 replies; 12+ messages in thread
From: David Hampton @ 2015-12-09 21:26 UTC (permalink / raw)
To: Btrfs BTRFS
This is a Mythbuntu system, and the latest they support is 14.04.
Thanks for all the responses.
David
On Thu, 2015-12-10 at 06:56 +1100, Gareth Pye wrote:
> I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
> (which counts as a long time when it's only for people happy to
> upgrade every 6 months).
>
> The kernel ppa's builds tend to run fine on the latest LTS & regular
> releases, although they can cause issues (I've had some fun with
> nvidia drivers at times). That ppa will get you to 4.3 or 4.4rc4.
>
> On Thu, Dec 10, 2015 at 6:39 AM, Chris Murphy <lists@colorremedies.com> wrote:
> > On Wed, Dec 9, 2015 at 10:28 AM, David Hampton
> > <mailinglists@dhampton.net> wrote:
> >> On Wed, 2015-12-09 at 16:48 +0000, Duncan wrote:
> >>> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
> >>>
> >>> > Seems I need to upgrade my tools. That command was added in 3.18 and I
> >>> > only have the 3.12 tools.
> >>>
> >>> Definitely so, especially because you're running raid6, which wasn't
> >>> stable until 4.1 for both kernel and userspace. 3.12? I guess it did
> >>> have the very basic raid56 support, but it's definitely nothing I'd
> >>> trust, at that old not for btrfs in general, but FOR SURE not raid56.
> >>
> >> I've upgraded to the 4.2.0 kernel and the 4.0 btrfs-tools package.
> >
> > I think btrfs-progs 4.0 has a mkfs bug in it (or was that 4.0.1?)
> > Anyway, even that is still old in Btrfs terms. I think Ubuntu needs to
> > do better than this, or just acknowledge Btrfs is not supported, don't
> > include btrfs-progs at all by default, and stop making it an install
> > time option.
> >
> >
> >> These are the latest that Ubuntu has packaged for 15.10, and I've pulled
> >> them into my 14.10 based release. Is this recent enough, or do I need
> >> to try the 4.3 kernel/tools build from the active development tree (that
> >> will eventually become 16.04)?
> >
> > It's probably fine day to day, but if you ever were to need btrfs
> > check or repair, you'd want the current version no matter what. There
> > are just too many bug fixes and enhancements happening to not make
> > that effort. You kinda have to understand that you're effectively
> > testing Btrfs by using raid56. It is stabilizing, but it can hardly be
> > called stable or even feature complete seeing as there are all sorts
> > of missing failure notifications.
> >
> > More than anything else you need to be willing to lose everything on
> > this volume, without further notice, i.e. you need a backup strategy
> > that you're prepared to use without undue stress. If you can't do
> > that, you need to look at another arrangement. Both LVM and mdadm
> > raid6 + XFS are more stable.
> >
> >
> > --
> > Chris Murphy
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 19:56 ` Gareth Pye
2015-12-09 21:26 ` David Hampton
@ 2015-12-09 21:28 ` Chris Murphy
2015-12-09 21:41 ` David Hampton
1 sibling, 1 reply; 12+ messages in thread
From: Chris Murphy @ 2015-12-09 21:28 UTC (permalink / raw)
To: Gareth Pye; +Cc: Chris Murphy, David Hampton, Btrfs BTRFS
On Wed, Dec 9, 2015 at 12:56 PM, Gareth Pye <gareth@cerberos.id.au> wrote:
> I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
OP reported 3.19.0-32-generic #37~14.04.1-Ubuntu. And 14.04 is LTS
supported until 2019. I think it should have something newer for both
kernel and progs, if it's going to offer btrfs as an install time
option. It's really easy to just have the LTS installer not offer
Btrfs, and not install btrfs-progs.
--
Chris Murphy
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 21:28 ` Chris Murphy
@ 2015-12-09 21:41 ` David Hampton
2015-12-09 21:59 ` Gareth Pye
0 siblings, 1 reply; 12+ messages in thread
From: David Hampton @ 2015-12-09 21:41 UTC (permalink / raw)
To: Btrfs BTRFS
Ubuntu 14.04 actually ships with the 3.13 kernel. I had already
upgraded it to 3.19 from the Ubuntu 15.04 release.
I'm pretty sure I created the btrfs partition, not the MythBuntu
installer. I don't remember if that was even an option.
David
On Wed, 2015-12-09 at 14:28 -0700, Chris Murphy wrote:
> On Wed, Dec 9, 2015 at 12:56 PM, Gareth Pye <gareth@cerberos.id.au> wrote:
> > I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
>
> OP reported 3.19.0-32-generic #37~14.04.1-Ubuntu. And 14.04 is LTS
> supported until 2019. I think it should have something newer for both
> kernel and progs, if it's going to offer btrfs as an install time
> option. It's really easy to just have the LTS installer not offer
> Btrfs, and not install btrfs-progs.
>
>
>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 21:41 ` David Hampton
@ 2015-12-09 21:59 ` Gareth Pye
0 siblings, 0 replies; 12+ messages in thread
From: Gareth Pye @ 2015-12-09 21:59 UTC (permalink / raw)
To: David Hampton; +Cc: Btrfs BTRFS
Sorry his message 4 hours ago mentioned 14.10.
On Thu, Dec 10, 2015 at 8:41 AM, David Hampton
<mailinglists@dhampton.net> wrote:
> Ubuntu 14.04 actually ships with the 3.13 kernel. I had already
> upgraded it to 3.19 from the Ubuntu 15.04 release.
>
> I'm pretty sure I created the btrfs partition, not the MythBuntu
> installer. I don't remember if that was even an option.
>
> David
>
>
> On Wed, 2015-12-09 at 14:28 -0700, Chris Murphy wrote:
>> On Wed, Dec 9, 2015 at 12:56 PM, Gareth Pye <gareth@cerberos.id.au> wrote:
>> > I wouldn't blame Ubuntu too much, 14.10 went out of support months ago
>>
>> OP reported 3.19.0-32-generic #37~14.04.1-Ubuntu. And 14.04 is LTS
>> supported until 2019. I think it should have something newer for both
>> kernel and progs, if it's going to offer btrfs as an install time
>> option. It's really easy to just have the LTS installer not offer
>> Btrfs, and not install btrfs-progs.
>>
>>
>>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Gareth Pye - blog.cerberos.id.au
Level 2 MTG Judge, Melbourne, Australia
"Dear God, I would like to file a bug report"
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Missing half of available space (resend)
2015-12-09 19:39 ` Chris Murphy
2015-12-09 19:56 ` Gareth Pye
@ 2015-12-10 3:27 ` Duncan
1 sibling, 0 replies; 12+ messages in thread
From: Duncan @ 2015-12-10 3:27 UTC (permalink / raw)
To: linux-btrfs
Chris Murphy posted on Wed, 09 Dec 2015 12:39:01 -0700 as excerpted:
> On Wed, Dec 9, 2015 at 10:28 AM, David Hampton
> <mailinglists@dhampton.net> wrote:
>> On Wed, 2015-12-09 at 16:48 +0000, Duncan wrote:
>>> David Hampton posted on Wed, 09 Dec 2015 01:30:09 -0500 as excerpted:
>>>
>>> > Seems I need to upgrade my tools. That command was added in 3.18
>>> > and I only have the 3.12 tools.
>>>
>>> Definitely so, especially because you're running raid6, which wasn't
>>> stable until 4.1 for both kernel and userspace. 3.12? I guess it did
>>> have the very basic raid56 support, but it's definitely nothing I'd
>>> trust, at that old not for btrfs in general, but FOR SURE not raid56.
>>
>> I've upgraded to the 4.2.0 kernel and the 4.0 btrfs-tools package.
>
> I think btrfs-progs 4.0 has a mkfs bug in it (or was that 4.0.1?)
Looking at the wiki, it was -progs 4.1.1 that had the mkfs.btrfs bug,
with 4.1.2 being the urgent bug-fix for it. (I just looked that up
myself for a different thread, a couple days ago, so had it fresh and
knew what I was looking for.)
https://btrfs.wiki.kernel.org/index.php/Changelog#btrfs-
progs_4.1.1_.28Jul_2015.29
> Anyway, even that is still old in Btrfs terms. I think Ubuntu needs to
> do better than this, or just acknowledge Btrfs is not supported, don't
> include btrfs-progs at all by default, and stop making it an install
> time option.
Three points related to list vs. distro release version support here:
1) In terms of this list, as a general rule there's currently four
recommended kernel series at any point in time. The latest two series
from either the current or LTS support series. On current, 4.4 is
getting close to release, so 4.3 and 4.2 are generally supported. On LTS,
again 4.4 will be an LTS series, with the previous two LTS series being
4.1 and 3.18, so those are generally supported. But 3.18 is getting a
bit long in the tooth now and 4.4 will be another LTS series, so people
still on it should already be planning their upgrade to at least 4.1.
For userspace (btrfs-progs), daily usage version isn't as critical as the
kernel, but if there's problems you'll probably want the newest, since it
has the latest fixes and the best chance for fixing things. As a general
rule of thumb, however, the kernel and userspace version numbers are
series-synced and developed at the same time with the same issues in
mind, so try to keep userspace version series at least equal to kernel
series, which if you're following kernel recommendations above, will
ensure that userspace doesn't get /too/ outdated and that it's roughly in
sync with your kernel. Newer userspace than kernel is fine. Which means
a 3.18 series userspace at the oldest, as well.
2) While that's the general rule, btrfs raid56 mode was only nominally
complete (earlier versions of raid56 had runtime completion, but recovery
tooling was incomplete, so you were effectively running a slow raid0 in
terms of recovery, that would be updated "for free" when the recovery
tools were complete) with 3.19 and there were major bugs into early 4.1.
So for raid56 mode you really *NEED* at least the latest LTS 4.1 kernel,
and following the userspace rule of thumb, the corresponding latest 4.1
series userspace, 4.1.2, with the bugfix for that mkfs.btrfs bug
mentioned above. That's the absolute minimum I'd consider reasonable
with raid56 mode, as before that, there ARE known bugs and it's simply
not worth the risk running btrfs raid56 mode on older, period.
However, with btrfs raid56 mode completion still so new, it really can't
be considered as stable as btrfs in general, with btrfs itself still
"stabilizing, but not fully stable or mature yet, so be sure you have
backups available if you value your data." I've long suggested that
btrfs raid56 mode would take a year (effectively five kernel series) to
stabilize after nominal code completion, before I'd consider it as stable
as btrfs in general. As it happens, that's 4.4, which is an LTS series
as well, so the timing is pretty sweet.
But that means as a practical matter, people running btrfs raid56 mode
have even more reason to be on the very latest, into the coming 4.4
series at least, because until then, it really can't be considered as
stable as btrfs in general. So while 4.1 is the absolute minimum I'd
consider running with raid56, you /really/ should be on the latest 4.3.x
stable kernel and 4.3.1 btrfs-progs userspace, and upgrade to 4.4 series
reasonably soon after it comes out as well. With 4.4 kernel being an LTS,
at that point you can relax a bit and stay on that series for awhile, if
desired.
3) Ubuntu unfortunately has a way of picking kernel versions to
standardize on, that aren't upstream kernel LTS versions. As a result,
while 3.18 for example, was an upstream LTS, the 3.19 ubuntu chose to
standardize on, was not. Fortunately, they've announced that they'll
standardize on the upcoming 4.4 LTS series for 2016.04, so hopefully
they've seen the light now and will sync a bit better with upstream LTS
than they have been doing.
The less distro-specific version of this point is that while the above
two latest current kernel and lts kernel series (and corresponding rule
of thumb userspace version syncing) recommendations stand for this list,
distros have their own kernel and userspace support rules, and to the
extent that they choose to support btrfs but diverge from the above
general list recommendations, users have a choice, they can either follow
their distro and presumably rely on the distro for primary btrfs support,
or follow list recommendations.
Meanwhile, it's not that the list won't try to support versions not in
sync with list recommendations, we'll certainly try, but that we'll have
a harder time doing so, because as those versions age, they get further
from the versions we're immediately familiar with. So we'll do our best,
but it's not going to be to the level we'd be able to support recommended
versions, and at times the best recommendation will be to upgrade to
something better supported and see what the results are.
As for level of distro support where their recommended versions differ
from those of this list and upstream, many of them do backport patches
from current where they consider appropriate, so in fact they _may_ have
a reasonably stable supported version, outside of upstream's recommended
versions. But the point is, that's their choice and their business, and
people on the list aren't likely to be particularly familiar with what
particular patches a distro has backported for their various releases, so
again, we won't be able to provide the level of support we could with
recommended versions as to some extent the distro packaged releases are
unknown quantities. Which is why in that case primary support really
should come from the distro. As to how well they actually provide it...
well, that's between the distro and its users, and isn't really a matter
this list is directly involved in, as we're btrfs kernel and userspace
upstream.
So in summary:
1) List primary support: Latest two upstream current and LTS kernel
release series, with userspace at least kernel-series-synced if not newer.
2) Btrfs raid56 mode is new and not yet as stable as btrfs in general.
LTS 4.1 series is the absolute minimum acceptable for base support,
current is preferred, thru at least the soon to be release 4.4 LTS, which
should stabilize raid56 to roughly the same level as btrfs in general.
3) Distros have their own release support models and users are free to
choose them for primary support over this list, but where distro support
series differ from those of this list, we'll still try to provide
support, but it'll be degraded compared to that provided to primary
supported release series, and the best list recommendation at times is
very likely to simply be, upgrade to something we can better support.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2015-12-10 3:27 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-09 5:02 Missing half of available space (resend) David Hampton
2015-12-09 5:27 ` Chris Murphy
2015-12-09 6:30 ` David Hampton
2015-12-09 16:48 ` Duncan
2015-12-09 17:28 ` David Hampton
2015-12-09 19:39 ` Chris Murphy
2015-12-09 19:56 ` Gareth Pye
2015-12-09 21:26 ` David Hampton
2015-12-09 21:28 ` Chris Murphy
2015-12-09 21:41 ` David Hampton
2015-12-09 21:59 ` Gareth Pye
2015-12-10 3:27 ` Duncan
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.