* illegal snapshot, cannot be deleted
@ 2015-11-11 22:11 Vedran Vucic
2015-11-12 12:32 ` Austin S Hemmelgarn
0 siblings, 1 reply; 17+ messages in thread
From: Vedran Vucic @ 2015-11-11 22:11 UTC (permalink / raw)
To: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
Hello,
I use OpenSuse 13.2 on my Toshiba Satellite laptop. I noticed that I run
out of disk space, checked documentation and I realized that there were
many snapshots. I used Yast Snapper to delete snapshots.
I noticed that one snapshot with number 748 could not be deleted.
I entered terminal and after the command:
snapper -c root delete 748
I got message Illegal snapshot.
I woudl like to delete it since it is old one.
Please find details about my system as requested on your wiki page.
uname -a
Linux linux-jjcc.site 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23 00:46:04
UTC 2015 (6be6a97) i686 i686 i386 GNU/Linux
btrfs --version
btrfs-progs v4.0+20150429
btrfs fi show
Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
Total devices 1 FS bytes used 10.98GiB
devid 1 size 18.71GiB used 18.71GiB path /dev/sda6
btrfs fi df /
Data, single: total=15.19GiB, used=10.37GiB
System, DUP: total=8.00MiB, used=16.00KiB
System, single: total=4.00MiB, used=0.00B
Metadata, DUP: total=1.75GiB, used=622.53MiB
Metadata, single: total=8.00MiB, used=0.00B
GlobalReserve, single: total=208.00MiB, used=0.00B
Please find attached dmesg.log as requested.
Please advise what have to do in order to delete snapshot that is reported
to be illegal.
Thanks
Vedran Vucic
[-- Attachment #2: dmesg.log --]
[-- Type: text/x-log, Size: 64198 bytes --]
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.16.7-29-desktop (geeko@buildhost) (gcc version 4.8.3 20140627 [gcc-4_8-branch revision 212064] (SUSE Linux) ) #1 SMP PREEMPT Fri Oct 23 00:46:04 UTC 2015 (6be6a97)
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009f7ff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009f800-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000dc000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000005fe6ffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000005fe70000-0x000000005fefffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000005ff00000-0x000000005fffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec0ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed00000-0x00000000fed003ff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed14000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed8ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: TOSHIBA Satellite A200/CAPELL VALLEY(NAPA) CRB, BIOS 1.20 03/24/2007
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x5fe70 max_arch_pfn = 0x1000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-CFFFF write-protect
[ 0.000000] D0000-DFFFF uncachable
[ 0.000000] E0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 000000000 mask FC0000000 write-back
[ 0.000000] 1 base 040000000 mask FE0000000 write-back
[ 0.000000] 2 base 05FF00000 mask FFFF00000 uncachable
[ 0.000000] 3 disabled
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
[ 0.000000] found SMP MP-table at [mem 0x000f71d0-0x000f71df] mapped at [c00f71d0]
[ 0.000000] Scanning 1 areas for low memory corruption
[ 0.000000] initial memory mapped: [mem 0x00000000-0x011fffff]
[ 0.000000] Base memory trampoline at [c009b000] 9b000 size 16384
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] [mem 0x00000000-0x000fffff] page 4k
[ 0.000000] init_memory_mapping: [mem 0x36a00000-0x36bfffff]
[ 0.000000] [mem 0x36a00000-0x36bfffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x34000000-0x369fffff]
[ 0.000000] [mem 0x34000000-0x369fffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x00100000-0x33ffffff]
[ 0.000000] [mem 0x00100000-0x001fffff] page 4k
[ 0.000000] [mem 0x00200000-0x33ffffff] page 2M
[ 0.000000] init_memory_mapping: [mem 0x36c00000-0x36dfdfff]
[ 0.000000] [mem 0x36c00000-0x36dfdfff] page 4k
[ 0.000000] BRK [0x00da2000, 0x00da2fff] PGTABLE
[ 0.000000] BRK [0x00da3000, 0x00da3fff] PGTABLE
[ 0.000000] BRK [0x00da4000, 0x00da4fff] PGTABLE
[ 0.000000] BRK [0x00da5000, 0x00da5fff] PGTABLE
[ 0.000000] BRK [0x00da6000, 0x00da6fff] PGTABLE
[ 0.000000] BRK [0x00da7000, 0x00da7fff] PGTABLE
[ 0.000000] RAMDISK: [mem 0x36efa000-0x37774fff]
[ 0.000000] Allocated new RAMDISK: [mem 0x3657c000-0x36df6d3b]
[ 0.000000] Move RAMDISK from [mem 0x36efa000-0x37774d3b] to [mem 0x3657c000-0x36df6d3b]
[ 0.000000] ACPI: Early table checksum verification disabled
[ 0.000000] ACPI: RSDP 0x000F7120 000024 (v02 TOSINV)
[ 0.000000] ACPI: XSDT 0x5FE7B5F2 00008C (v01 TOSINV TOSINV00 06040000 INV 00000000)
[ 0.000000] ACPI: FACP 0x5FE82BF8 0000F4 (v03 TOSINV TOSINV00 06040000 ALAN 00000001)
[ 0.000000] ACPI: DSDT 0x5FE7D387 0057FD (v02 TOSINV CALISTGA 06040000 INTL 20050624)
[ 0.000000] ACPI: FACS 0x5FE83FC0 000040
[ 0.000000] ACPI: APIC 0x5FE82CEC 000068 (v01 INTEL CALISTGA 06040000 LOHR 0000005A)
[ 0.000000] ACPI: HPET 0x5FE82D54 000038 (v01 INTEL CALISTGA 06040000 LOHR 0000005A)
[ 0.000000] ACPI: MCFG 0x5FE82D8C 00003C (v01 INTEL CALISTGA 06040000 LOHR 0000005A)
[ 0.000000] ACPI: TCPA 0x5FE82DC8 000032 (v01 PTLTD CALISTGA 06040000 PTL 00000001)
[ 0.000000] ACPI: APIC 0x5FE82DFA 000068 (v01 TOSINV APIC 06040000 INV 00000000)
[ 0.000000] ACPI: SLIC 0x5FE82E62 000176 (v01 TOSINV TOSINV00 06040000 INV 00000000)
[ 0.000000] ACPI: BOOT 0x5FE82FD8 000028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001)
[ 0.000000] ACPI: SSDT 0x5FE7CD38 00064F (v01 SataRe SataPri 00001000 INTL 20050624)
[ 0.000000] ACPI: SSDT 0x5FE7C6A6 000692 (v01 SataRe SataSec 00001000 INTL 20050624)
[ 0.000000] ACPI: SSDT 0x5FE7BC0A 00025F (v01 PmRef Cpu0Tst 00003000 INTL 20050624)
[ 0.000000] ACPI: SSDT 0x5FE7BB64 0000A6 (v01 PmRef Cpu1Tst 00003000 INTL 20050624)
[ 0.000000] ACPI: SSDT 0x5FE7B67E 0004E6 (v01 PmRef CpuPm 00003000 INTL 20050624)
[ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
[ 0.000000] ACPI: If "acpi_apic_instance=2" works better, notify linux-acpi@vger.kernel.org
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] No NUMA configuration found
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x000000005fe6ffff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x5fe6ffff]
[ 0.000000] NODE_DATA [mem 0x3657a000-0x3657bfff]
[ 0.000000] 656MB HIGHMEM available.
[ 0.000000] 877MB LOWMEM available.
[ 0.000000] max_low_pfn = 36dfe, highstart_pfn = 36dfe
[ 0.000000] Low memory ends at vaddr f6dfe000
[ 0.000000] High memory starts at vaddr f6dfe000
[ 0.000000] mapped low ram: 0 - 36dfe000
[ 0.000000] low ram: 0 - 36dfe000
[ 0.000000] Node: 0, start_pfn: 1, end_pfn: 9f
[ 0.000000] Setting physnode_map array to node 0 for pfns:
[ 0.000000] 0
[ 0.000000] Node: 0, start_pfn: 100, end_pfn: 5fe70
[ 0.000000] Setting physnode_map array to node 0 for pfns:
[ 0.000000] 0 4000 8000 c000 10000 14000 18000 1c000 20000 24000 28000 2c000 30000 34000 38000 3c000 40000 44000 48000 4c000 50000 54000 58000 5c000
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] Normal [mem 0x01000000-0x36dfdfff]
[ 0.000000] HighMem [mem 0x36dfe000-0x5fe6ffff]
[ 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-0x5fe6ffff]
[ 0.000000] On node 0 totalpages: 392718
[ 0.000000] free_area_init_node: node 0, pgdat f657a000, node_mem_map f5979020
[ 0.000000] DMA zone: 32 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 3998 pages, LIFO batch:0
[ 0.000000] Normal zone: 1724 pages used for memmap
[ 0.000000] Normal zone: 220670 pages, LIFO batch:31
[ 0.000000] HighMem zone: 1313 pages used for memmap
[ 0.000000] HighMem zone: 168050 pages, LIFO batch:31
[ 0.000000] Using APIC driver default
[ 0.000000] ACPI: PM-Timer IO Port: 0x1008
[ 0.000000] ACPI: Local APIC address 0xfee00000
[ 0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
[ 0.000000] ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
[ 0.000000] IOAPIC[0]: apic_id 1, version 32, 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 9 global_irq 9 high level)
[ 0.000000] ACPI: IRQ0 used by override.
[ 0.000000] ACPI: IRQ2 used by override.
[ 0.000000] ACPI: IRQ9 used by override.
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000
[ 0.000000] smpboot: Allowing 2 CPUs, 0 hotplug CPUs
[ 0.000000] nr_irqs_gsi: 40
[ 0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dbfff]
[ 0.000000] PM: Registered nosave memory: [mem 0x000dc000-0x000fffff]
[ 0.000000] e820: [mem 0x60000000-0xfebfffff] available for PCI devices
[ 0.000000] Booting paravirtualized kernel on bare hardware
[ 0.000000] setup_percpu: NR_CPUS:128 nr_cpumask_bits:128 nr_cpu_ids:2 nr_node_ids:1
[ 0.000000] PERCPU: Embedded 14 pages/cpu @f5954000 s32960 r0 d24384 u57344
[ 0.000000] pcpu-alloc: s32960 r0 d24384 u57344 alloc=14*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 390962
[ 0.000000] Policy zone: HighMem
[ 0.000000] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-3.16.7-29-desktop root=UUID=d6934db3-3ac9-49d0-83db-287be7b995a5 resume=/dev/sda5 splash=silent quiet showopts
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] CPU0 microcode updated early to revision 0x5c, date = 2010-10-02
[ 0.000000] Initializing CPU#0
[ 0.000000] allocated 3142520 bytes of page_cgroup
[ 0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[ 0.000000] Initializing HighMem for node 0 (00036dfe:0005fe70)
[ 0.000000] Initializing Movable for node 0 (00000000:00000000)
[ 0.000000] Memory: 1533848K/1570872K available (5723K kernel code, 531K rwdata, 3956K rodata, 728K init, 896K bss, 37024K reserved, 672200K highmem)
[ 0.000000] virtual kernel memory layout:
fixmap : 0xff5b5000 - 0xfffff000 (10536 kB)
pkmap : 0xfee00000 - 0xff000000 (2048 kB)
vmalloc : 0xf75fe000 - 0xfedfe000 ( 120 MB)
lowmem : 0xc0000000 - 0xf6dfe000 ( 877 MB)
.init : 0xc0bfc000 - 0xc0cb2000 ( 728 kB)
.data : 0xc0797137 - 0xc0bfaf80 (4495 kB)
.text : 0xc0200000 - 0xc0797137 (5724 kB)
[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok.
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] RCU dyntick-idle grace-period acceleration is enabled.
[ 0.000000] RCU restricting CPUs from NR_CPUS=128 to nr_cpu_ids=2.
[ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000] NR_IRQS:8448 nr_irqs:512 16
[ 0.000000] CPU 0 irqstacks, hard=f5006000 soft=f5008000
[ 0.000000] Console: colour dummy device 80x25
[ 0.000000] console [tty0] enabled
[ 0.000000] hpet clockevent registered
[ 0.000000] tsc: Fast TSC calibration using PIT
[ 0.000000] tsc: Detected 1728.986 MHz processor
[ 0.001015] Calibrating delay loop (skipped), value calculated using timer frequency.. 3457.97 BogoMIPS (lpj=1728986)
[ 0.001019] pid_max: default: 32768 minimum: 301
[ 0.001033] ACPI: Core revision 20140424
[ 0.001038] TOSHIBA Satellite detected - force copy of DSDT to local memory
[ 0.002040] ACPI: Forced DSDT copy: length 0x057FD copied locally, original unmapped
[ 0.013787] ACPI: All ACPI Tables successfully acquired
[ 0.014049] Security Framework initialized
[ 0.014076] AppArmor: AppArmor initialized
[ 0.014143] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.014146] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.015364] Initializing cgroup subsys memory
[ 0.015402] Initializing cgroup subsys devices
[ 0.015415] Initializing cgroup subsys freezer
[ 0.015420] Initializing cgroup subsys net_cls
[ 0.015430] Initializing cgroup subsys blkio
[ 0.015438] Initializing cgroup subsys perf_event
[ 0.015442] Initializing cgroup subsys net_prio
[ 0.015453] Initializing cgroup subsys hugetlb
[ 0.015483] CPU: Physical Processor ID: 0
[ 0.015485] CPU: Processor Core ID: 0
[ 0.015493] mce: CPU supports 6 MCE banks
[ 0.015504] CPU0: Thermal monitoring handled by SMI
[ 0.015519] Last level iTLB entries: 4KB 128, 2MB 4, 4MB 4
Last level dTLB entries: 4KB 256, 2MB 0, 4MB 32, 1GB 0
tlb_flushall_shift: -1
[ 0.016040] Freeing SMP alternatives memory: 24K (c0cb2000 - c0cb8000)
[ 0.016959] ftrace: allocating 23724 entries in 47 pages
[ 0.024165] Enabling APIC mode: Flat. Using 1 I/O APICs
[ 0.024645] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
[ 0.035070] smpboot: CPU0: Intel(R) Core(TM)2 CPU T5300 @ 1.73GHz (fam: 06, model: 0f, stepping: 02)
[ 0.036000] Performance Events: PEBS fmt0-, 4-deep LBR, Core2 events, Intel PMU driver.
[ 0.036000] perf_event_intel: PEBS disabled due to CPU errata
[ 0.036000] ... version: 2
[ 0.036000] ... bit width: 40
[ 0.036000] ... generic registers: 2
[ 0.036000] ... value mask: 000000ffffffffff
[ 0.036000] ... max period: 000000007fffffff
[ 0.036000] ... fixed-purpose events: 3
[ 0.036000] ... event mask: 0000000700000003
[ 0.047176] CPU 1 irqstacks, hard=f516c000 soft=f516e000
[ 0.047180] x86: Booting SMP configuration:
[ 0.047182] .... node #0, CPUs: #1
[ 0.002000] CPU1 microcode updated early to revision 0x5c, date = 2010-10-02
[ 0.002000] Initializing CPU#1
[ 0.002000] CPU1: Thermal monitoring handled by SMI
[ 0.059124] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 0.059145] x86: Booted up 1 node, 2 CPUs
[ 0.059148] smpboot: Total of 2 processors activated (6915.94 BogoMIPS)
[ 0.061066] devtmpfs: initialized
[ 0.061422] PM: Registering ACPI NVS region [mem 0x5fe70000-0x5fefffff] (589824 bytes)
[ 0.063531] pinctrl core: initialized pinctrl subsystem
[ 0.063587] RTC time: 22:23:54, date: 11/11/15
[ 0.063680] NET: Registered protocol family 16
[ 0.063973] cpuidle: using governor ladder
[ 0.063977] cpuidle: using governor menu
[ 0.064103] ACPI: bus type PCI registered
[ 0.064107] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
[ 0.064253] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.064257] PCI: not using MMCONFIG
[ 0.064485] PCI : PCI BIOS area is rw and x. Use pci=nobios if you want it NX.
[ 0.064489] PCI: PCI BIOS revision 2.10 entry at 0xfd604, last bus=7
[ 0.064491] PCI: Using configuration type 1 for base access
[ 0.064717] mtrr: your CPUs had inconsistent variable MTRR settings
[ 0.064719] mtrr: probably your BIOS does not setup all CPUs.
[ 0.064720] mtrr: corrected configuration.
[ 0.069127] ACPI: Added _OSI(Module Device)
[ 0.069127] ACPI: Added _OSI(Processor Device)
[ 0.069127] ACPI: Added _OSI(3.0 _SCP Extensions)
[ 0.069127] ACPI: Added _OSI(Processor Aggregator Device)
[ 0.075048] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[ 0.076098] ACPI: Dynamic OEM Table Load:
[ 0.076109] ACPI: SSDT 0xF5220C00 00023B (v01 PmRef Cpu0Ist 00003000 INTL 20050624)
[ 0.076868] ACPI: Dynamic OEM Table Load:
[ 0.076877] ACPI: SSDT 0xF51F9000 0004C2 (v01 PmRef Cpu0Cst 00003001 INTL 20050624)
[ 0.078095] ACPI: Dynamic OEM Table Load:
[ 0.078104] ACPI: SSDT 0xF51CC100 0000BB (v01 PmRef Cpu1Ist 00003000 INTL 20050624)
[ 0.078697] ACPI: Dynamic OEM Table Load:
[ 0.078705] ACPI: SSDT 0xF51CC040 000085 (v01 PmRef Cpu1Cst 00003000 INTL 20050624)
[ 0.080093] ACPI : EC: GPE storm detected(29 GPEs), transactions will use polling mode
[ 0.097078] ACPI: Interpreter enabled
[ 0.097095] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20140424/hwxface-580)
[ 0.097101] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20140424/hwxface-580)
[ 0.097125] ACPI: (supports S0 S3 S4 S5)
[ 0.097127] ACPI: Using IOAPIC for interrupt routing
[ 0.097158] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0xe0000000-0xefffffff] (base 0xe0000000)
[ 0.098369] PCI: MMCONFIG at [mem 0xe0000000-0xefffffff] reserved in ACPI motherboard resources
[ 0.098372] PCI: Using MMCONFIG for extended config space
[ 0.098397] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.119244] ACPI: Power Resource [FN00] (off)
[ 0.124896] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
[ 0.124906] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[ 0.124915] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.126604] PCI host bridge to bus 0000:00
[ 0.126609] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.126613] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7]
[ 0.126616] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff]
[ 0.126619] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
[ 0.126623] pci_bus 0000:00: root bus resource [mem 0x000d0000-0x000d3fff]
[ 0.126626] pci_bus 0000:00: root bus resource [mem 0x000d4000-0x000d7fff]
[ 0.126629] pci_bus 0000:00: root bus resource [mem 0x000d8000-0x000dbfff]
[ 0.126632] pci_bus 0000:00: root bus resource [mem 0x60000000-0xfebfffff]
[ 0.126648] pci 0000:00:00.0: [8086:27a0] type 00 class 0x060000
[ 0.126828] pci 0000:00:01.0: [8086:27a1] type 01 class 0x060400
[ 0.126898] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
[ 0.127109] pci 0000:00:1b.0: [8086:27d8] type 00 class 0x040300
[ 0.127140] pci 0000:00:1b.0: reg 0x10: [mem 0xf0c00000-0xf0c03fff 64bit]
[ 0.127271] pci 0000:00:1b.0: PME# supported from D0 D3hot D3cold
[ 0.127354] pci 0000:00:1b.0: System wakeup disabled by ACPI
[ 0.127444] pci 0000:00:1c.0: [8086:27d0] type 01 class 0x060400
[ 0.127582] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
[ 0.127749] pci 0000:00:1c.1: [8086:27d2] type 01 class 0x060400
[ 0.127887] pci 0000:00:1c.1: PME# supported from D0 D3hot D3cold
[ 0.128055] pci 0000:00:1c.2: [8086:27d4] type 01 class 0x060400
[ 0.128195] pci 0000:00:1c.2: PME# supported from D0 D3hot D3cold
[ 0.128362] pci 0000:00:1d.0: [8086:27c8] type 00 class 0x0c0300
[ 0.128427] pci 0000:00:1d.0: reg 0x20: [io 0x1800-0x181f]
[ 0.128558] pci 0000:00:1d.0: System wakeup disabled by ACPI
[ 0.128643] pci 0000:00:1d.1: [8086:27c9] type 00 class 0x0c0300
[ 0.128707] pci 0000:00:1d.1: reg 0x20: [io 0x1820-0x183f]
[ 0.128836] pci 0000:00:1d.1: System wakeup disabled by ACPI
[ 0.128922] pci 0000:00:1d.2: [8086:27ca] type 00 class 0x0c0300
[ 0.128986] pci 0000:00:1d.2: reg 0x20: [io 0x1840-0x185f]
[ 0.129152] pci 0000:00:1d.3: [8086:27cb] type 00 class 0x0c0300
[ 0.129216] pci 0000:00:1d.3: reg 0x20: [io 0x1860-0x187f]
[ 0.129390] pci 0000:00:1d.7: [8086:27cc] type 00 class 0x0c0320
[ 0.129419] pci 0000:00:1d.7: reg 0x10: [mem 0xf0c04000-0xf0c043ff]
[ 0.129540] pci 0000:00:1d.7: PME# supported from D0 D3hot D3cold
[ 0.129617] pci 0000:00:1d.7: System wakeup disabled by ACPI
[ 0.129703] pci 0000:00:1e.0: [8086:2448] type 01 class 0x060401
[ 0.129924] pci 0000:00:1f.0: [8086:27b9] type 00 class 0x060100
[ 0.130055] pci 0000:00:1f.0: can't claim BAR 13 [io 0x1000-0x107f]: address conflict with ACPI CPU throttle [io 0x1010-0x1015]
[ 0.130063] pci 0000:00:1f.0: quirk: [io 0x1180-0x11bf] claimed by ICH6 GPIO
[ 0.130073] pci 0000:00:1f.0: ICH7 LPC Generic IO decode 3 PIO at 0068 (mask 0007)
[ 0.130251] pci 0000:00:1f.2: [8086:27c4] type 00 class 0x010180
[ 0.130277] pci 0000:00:1f.2: reg 0x10: [io 0x0000-0x0007]
[ 0.130291] pci 0000:00:1f.2: reg 0x14: [io 0x0000-0x0003]
[ 0.130305] pci 0000:00:1f.2: reg 0x18: [io 0x0000-0x0007]
[ 0.130319] pci 0000:00:1f.2: reg 0x1c: [io 0x0000-0x0003]
[ 0.130333] pci 0000:00:1f.2: reg 0x20: [io 0x18b0-0x18bf]
[ 0.130363] pci 0000:00:1f.2: legacy IDE quirk: reg 0x10: [io 0x01f0-0x01f7]
[ 0.130366] pci 0000:00:1f.2: legacy IDE quirk: reg 0x14: [io 0x03f6]
[ 0.130369] pci 0000:00:1f.2: legacy IDE quirk: reg 0x18: [io 0x0170-0x0177]
[ 0.130372] pci 0000:00:1f.2: legacy IDE quirk: reg 0x1c: [io 0x0376]
[ 0.130410] pci 0000:00:1f.2: PME# supported from D3hot
[ 0.130560] pci 0000:00:1f.3: [8086:27da] type 00 class 0x0c0500
[ 0.130642] pci 0000:00:1f.3: reg 0x20: [io 0x18c0-0x18df]
[ 0.130935] pci 0000:01:00.0: [10de:01d7] type 00 class 0x030000
[ 0.130975] pci 0000:01:00.0: reg 0x10: [mem 0xcd000000-0xcdffffff]
[ 0.131013] pci 0000:01:00.0: reg 0x14: [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.131046] pci 0000:01:00.0: reg 0x1c: [mem 0xce000000-0xceffffff 64bit]
[ 0.131089] pci 0000:01:00.0: reg 0x30: [mem 0x00000000-0x0001ffff pref]
[ 0.131320] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.131336] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.131343] pci 0000:00:01.0: bridge window [mem 0xcd000000-0xceffffff]
[ 0.131349] pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.131505] pci 0000:02:00.0: [11ab:4353] type 00 class 0x020000
[ 0.131546] pci 0000:02:00.0: reg 0x10: [mem 0xf0600000-0xf0603fff 64bit]
[ 0.131565] pci 0000:02:00.0: reg 0x18: [io 0x2000-0x20ff]
[ 0.131741] pci 0000:02:00.0: supports D1 D2
[ 0.131744] pci 0000:02:00.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.131785] pci 0000:02:00.0: System wakeup disabled by ACPI
[ 0.131861] pci 0000:02:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.131875] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.131882] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
[ 0.131888] pci 0000:00:1c.0: bridge window [mem 0xf0600000-0xf06fffff]
[ 0.131898] pci 0000:00:1c.0: bridge window [mem 0xf0000000-0xf01fffff 64bit pref]
[ 0.132137] pci 0000:03:00.0: [8086:4222] type 00 class 0x028000
[ 0.132208] pci 0000:03:00.0: reg 0x10: [mem 0xf0700000-0xf0700fff]
[ 0.132672] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
[ 0.132871] pci 0000:03:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 0.132912] pci 0000:00:1c.1: PCI bridge to [bus 03-04]
[ 0.132919] pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
[ 0.132925] pci 0000:00:1c.1: bridge window [mem 0xf0700000-0xf07fffff]
[ 0.132935] pci 0000:00:1c.1: bridge window [mem 0xf0200000-0xf03fffff 64bit pref]
[ 0.133099] acpiphp: Slot [1] registered
[ 0.133108] pci 0000:00:1c.2: PCI bridge to [bus 05-06]
[ 0.133115] pci 0000:00:1c.2: bridge window [io 0x4000-0x4fff]
[ 0.133121] pci 0000:00:1c.2: bridge window [mem 0xf0800000-0xf08fffff]
[ 0.133131] pci 0000:00:1c.2: bridge window [mem 0xf0400000-0xf05fffff 64bit pref]
[ 0.133263] pci 0000:07:06.0: [104c:8039] type 02 class 0x060700
[ 0.133290] pci 0000:07:06.0: reg 0x10: [mem 0x00000000-0x00000fff]
[ 0.133339] pci 0000:07:06.0: supports D1 D2
[ 0.133342] pci 0000:07:06.0: PME# supported from D0 D1 D2 D3hot D3cold
[ 0.133462] pci 0000:07:06.1: [104c:803a] type 00 class 0x0c0010
[ 0.133492] pci 0000:07:06.1: reg 0x10: [mem 0xf0905000-0xf09057ff]
[ 0.133510] pci 0000:07:06.1: reg 0x14: [mem 0xf0900000-0xf0903fff]
[ 0.133626] pci 0000:07:06.1: supports D1 D2
[ 0.133629] pci 0000:07:06.1: PME# supported from D0 D1 D2 D3hot
[ 0.133743] pci 0000:07:06.2: [104c:803b] type 00 class 0x018000
[ 0.133772] pci 0000:07:06.2: reg 0x10: [mem 0xf0904000-0xf0904fff]
[ 0.133895] pci 0000:07:06.2: supports D1 D2
[ 0.133898] pci 0000:07:06.2: PME# supported from D0 D1 D2 D3hot
[ 0.134011] pci 0000:07:06.3: [104c:803c] type 00 class 0x080501
[ 0.134040] pci 0000:07:06.3: reg 0x10: [mem 0xf0905800-0xf09058ff]
[ 0.134167] pci 0000:07:06.3: supports D1 D2
[ 0.134170] pci 0000:07:06.3: PME# supported from D0 D1 D2 D3hot
[ 0.134321] pci 0000:00:1e.0: PCI bridge to [bus 07] (subtractive decode)
[ 0.134331] pci 0000:00:1e.0: bridge window [mem 0xf0900000-0xf09fffff]
[ 0.134341] pci 0000:00:1e.0: bridge window [io 0x0000-0x0cf7] (subtractive decode)
[ 0.134344] pci 0000:00:1e.0: bridge window [io 0x0d00-0xffff] (subtractive decode)
[ 0.134348] pci 0000:00:1e.0: bridge window [mem 0x000a0000-0x000bffff] (subtractive decode)
[ 0.134351] pci 0000:00:1e.0: bridge window [mem 0x000d0000-0x000d3fff] (subtractive decode)
[ 0.134354] pci 0000:00:1e.0: bridge window [mem 0x000d4000-0x000d7fff] (subtractive decode)
[ 0.134358] pci 0000:00:1e.0: bridge window [mem 0x000d8000-0x000dbfff] (subtractive decode)
[ 0.134361] pci 0000:00:1e.0: bridge window [mem 0x60000000-0xfebfffff] (subtractive decode)
[ 0.134367] pci 0000:07:06.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.134451] pci_bus 0000:08: busn_res: can not insert [bus 08-ff] under [bus 07] (conflicts with (null) [bus 07])
[ 0.134459] pci_bus 0000:08: busn_res: [bus 08-ff] end is updated to 0b
[ 0.134463] pci_bus 0000:08: busn_res: can not insert [bus 08-0b] under [bus 07] (conflicts with (null) [bus 07])
[ 0.134469] pci_bus 0000:08: [bus 08-0b] partially hidden behind transparent bridge 0000:07 [bus 07]
[ 0.134474] pci 0000:00:1e.0: bridge has subordinate 07 but max busn 0b
[ 0.134823] ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
[ 0.134958] ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
[ 0.135099] ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 *10 12 14 15)
[ 0.135231] ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 11 12 14 15) *10
[ 0.135364] ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
[ 0.135496] ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 11 12 14 15) *0, disabled.
[ 0.135629] ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 *10 12 14 15)
[ 0.135764] ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
[ 0.137042] ACPI: Enabled 5 GPEs in block 00 to 1F
[ 0.137123] ACPI : EC: GPE = 0x16, I/O: command/status = 0x66, data = 0x62
[ 0.137213] vgaarb: setting as boot device: PCI:0000:01:00.0
[ 0.137213] vgaarb: device added: PCI:0000:01:00.0,decodes=io+mem,owns=io+mem,locks=none
[ 0.137213] vgaarb: loaded
[ 0.137213] vgaarb: bridge control possible 0000:01:00.0
[ 0.137213] SCSI subsystem initialized
[ 0.137254] libata version 3.00 loaded.
[ 0.137254] ACPI: bus type USB registered
[ 0.137254] usbcore: registered new interface driver usbfs
[ 0.137254] usbcore: registered new interface driver hub
[ 0.137254] usbcore: registered new device driver usb
[ 0.137254] PCI: Using ACPI for IRQ routing
[ 0.137296] PCI: pci_cache_line_size set to 64 bytes
[ 0.137398] e820: reserve RAM buffer [mem 0x0009f800-0x0009ffff]
[ 0.137401] e820: reserve RAM buffer [mem 0x5fe70000-0x5fffffff]
[ 0.137630] NetLabel: Initializing
[ 0.137633] NetLabel: domain hash size = 128
[ 0.137635] NetLabel: protocols = UNLABELED CIPSOv4
[ 0.137655] NetLabel: unlabeled traffic allowed by default
[ 0.138061] HPET: 3 timers in total, 0 timers will be used for per-cpu timer
[ 0.138069] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
[ 0.138076] hpet0: 3 comparators, 64-bit 14.318180 MHz counter
[ 0.140037] Switched to clocksource hpet
[ 0.154192] AppArmor: AppArmor Filesystem Enabled
[ 0.154272] pnp: PnP ACPI init
[ 0.154310] ACPI: bus type PNP registered
[ 0.158238] system 00:00: [mem 0xe0000000-0xefffffff] has been reserved
[ 0.158243] system 00:00: [mem 0xfed14000-0xfed17fff] has been reserved
[ 0.158248] system 00:00: [mem 0xfed18000-0xfed18fff] has been reserved
[ 0.158252] system 00:00: [mem 0xfed19000-0xfed19fff] has been reserved
[ 0.158256] system 00:00: [mem 0xfed1c000-0xfed1ffff] has been reserved
[ 0.158260] system 00:00: [mem 0xfed20000-0xfed3ffff] has been reserved
[ 0.158266] system 00:00: [mem 0xfed40000-0xfed44fff] has been reserved
[ 0.158270] system 00:00: [mem 0xfed45000-0xfed8ffff] has been reserved
[ 0.158275] system 00:00: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.158898] system 00:01: [mem 0xfed00000-0xfed003ff] has been reserved
[ 0.158903] system 00:01: Plug and Play ACPI device, IDs PNP0103 PNP0c01 (active)
[ 0.159037] system 00:02: [io 0x03e8-0x03ef] has been reserved
[ 0.159041] system 00:02: [io 0x0400-0x0401] has been reserved
[ 0.159045] system 00:02: [io 0x0680-0x069f] has been reserved
[ 0.159049] system 00:02: [io 0x0800-0x080f] has been reserved
[ 0.159054] system 00:02: [io 0x1000-0x107f] could not be reserved
[ 0.159057] system 00:02: [io 0x1180-0x11bf] has been reserved
[ 0.159061] system 00:02: [io 0x1640-0x164f] has been reserved
[ 0.159065] system 00:02: [io 0xfe00-0xfe01] has been reserved
[ 0.159069] system 00:02: Plug and Play ACPI device, IDs PNP0c02 (active)
[ 0.159154] pnp 00:03: Plug and Play ACPI device, IDs PNP0b00 (active)
[ 0.159229] pnp 00:04: Plug and Play ACPI device, IDs PNP0303 (active)
[ 0.159316] pnp 00:05: Plug and Play ACPI device, IDs SYN1909 SYN1900 SYN0002 PNP0f13 (active)
[ 0.161068] pnp: PnP ACPI: found 6 devices
[ 0.161071] ACPI: bus type PNP unregistered
[ 0.200460] pci 0000:07:06.0: res[13]=[io 0x0100-0x00ff] get_res_add_size add_size 100
[ 0.200465] pci 0000:07:06.0: res[14]=[io 0x0100-0x00ff] get_res_add_size add_size 100
[ 0.200470] pci 0000:00:1e.0: bridge window [io 0x1000-0x0fff] to [bus 07] add_size 1000
[ 0.200478] pci 0000:00:1f.0: BAR 13: [io 0x1000-0x107f] has bogus alignment
[ 0.200482] pci 0000:00:1e.0: res[13]=[io 0x1000-0x0fff] get_res_add_size add_size 1000
[ 0.200493] pci 0000:00:1e.0: BAR 13: assigned [io 0x5000-0x5fff]
[ 0.200499] pci 0000:01:00.0: BAR 6: can't assign mem pref (size 0x20000)
[ 0.200503] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.200509] pci 0000:00:01.0: bridge window [mem 0xcd000000-0xceffffff]
[ 0.200514] pci 0000:00:01.0: bridge window [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.200521] pci 0000:00:1c.0: PCI bridge to [bus 02]
[ 0.200526] pci 0000:00:1c.0: bridge window [io 0x2000-0x2fff]
[ 0.200534] pci 0000:00:1c.0: bridge window [mem 0xf0600000-0xf06fffff]
[ 0.200540] pci 0000:00:1c.0: bridge window [mem 0xf0000000-0xf01fffff 64bit pref]
[ 0.200549] pci 0000:00:1c.1: PCI bridge to [bus 03-04]
[ 0.200554] pci 0000:00:1c.1: bridge window [io 0x3000-0x3fff]
[ 0.200562] pci 0000:00:1c.1: bridge window [mem 0xf0700000-0xf07fffff]
[ 0.200568] pci 0000:00:1c.1: bridge window [mem 0xf0200000-0xf03fffff 64bit pref]
[ 0.200578] pci 0000:00:1c.2: PCI bridge to [bus 05-06]
[ 0.200582] pci 0000:00:1c.2: bridge window [io 0x4000-0x4fff]
[ 0.200590] pci 0000:00:1c.2: bridge window [mem 0xf0800000-0xf08fffff]
[ 0.200596] pci 0000:00:1c.2: bridge window [mem 0xf0400000-0xf05fffff 64bit pref]
[ 0.200609] pci 0000:07:06.0: res[15]=[mem 0x04000000-0x03ffffff pref] get_res_add_size add_size 4000000
[ 0.200613] pci 0000:07:06.0: res[16]=[mem 0x04000000-0x03ffffff] get_res_add_size add_size 4000000
[ 0.200616] pci 0000:07:06.0: res[13]=[io 0x0100-0x00ff] get_res_add_size add_size 100
[ 0.200619] pci 0000:07:06.0: res[14]=[io 0x0100-0x00ff] get_res_add_size add_size 100
[ 0.200627] pci 0000:07:06.0: BAR 0: assigned [mem 0x60000000-0x60000fff]
[ 0.200638] pci 0000:07:06.0: BAR 15: assigned [mem 0x64000000-0x67ffffff pref]
[ 0.200644] pci 0000:07:06.0: BAR 16: assigned [mem 0x68000000-0x6bffffff]
[ 0.200647] pci 0000:07:06.0: BAR 13: assigned [io 0x5000-0x50ff]
[ 0.200651] pci 0000:07:06.0: BAR 14: assigned [io 0x5400-0x54ff]
[ 0.200655] pci 0000:07:06.0: CardBus bridge to [bus 08-0b]
[ 0.200658] pci 0000:07:06.0: bridge window [io 0x5000-0x50ff]
[ 0.200665] pci 0000:07:06.0: bridge window [io 0x5400-0x54ff]
[ 0.200672] pci 0000:07:06.0: bridge window [mem 0x64000000-0x67ffffff pref]
[ 0.200679] pci 0000:07:06.0: bridge window [mem 0x68000000-0x6bffffff]
[ 0.200686] pci 0000:00:1e.0: PCI bridge to [bus 07]
[ 0.200690] pci 0000:00:1e.0: bridge window [io 0x5000-0x5fff]
[ 0.200698] pci 0000:00:1e.0: bridge window [mem 0xf0900000-0xf09fffff]
[ 0.200711] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7]
[ 0.200714] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff]
[ 0.200718] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.200721] pci_bus 0000:00: resource 7 [mem 0x000d0000-0x000d3fff]
[ 0.200724] pci_bus 0000:00: resource 8 [mem 0x000d4000-0x000d7fff]
[ 0.200727] pci_bus 0000:00: resource 9 [mem 0x000d8000-0x000dbfff]
[ 0.200730] pci_bus 0000:00: resource 10 [mem 0x60000000-0xfebfffff]
[ 0.200733] pci_bus 0000:01: resource 1 [mem 0xcd000000-0xceffffff]
[ 0.200737] pci_bus 0000:01: resource 2 [mem 0xd0000000-0xdfffffff 64bit pref]
[ 0.200740] pci_bus 0000:02: resource 0 [io 0x2000-0x2fff]
[ 0.200743] pci_bus 0000:02: resource 1 [mem 0xf0600000-0xf06fffff]
[ 0.200746] pci_bus 0000:02: resource 2 [mem 0xf0000000-0xf01fffff 64bit pref]
[ 0.200750] pci_bus 0000:03: resource 0 [io 0x3000-0x3fff]
[ 0.200753] pci_bus 0000:03: resource 1 [mem 0xf0700000-0xf07fffff]
[ 0.200756] pci_bus 0000:03: resource 2 [mem 0xf0200000-0xf03fffff 64bit pref]
[ 0.200759] pci_bus 0000:05: resource 0 [io 0x4000-0x4fff]
[ 0.200762] pci_bus 0000:05: resource 1 [mem 0xf0800000-0xf08fffff]
[ 0.200765] pci_bus 0000:05: resource 2 [mem 0xf0400000-0xf05fffff 64bit pref]
[ 0.200769] pci_bus 0000:07: resource 0 [io 0x5000-0x5fff]
[ 0.200772] pci_bus 0000:07: resource 1 [mem 0xf0900000-0xf09fffff]
[ 0.200775] pci_bus 0000:07: resource 4 [io 0x0000-0x0cf7]
[ 0.200778] pci_bus 0000:07: resource 5 [io 0x0d00-0xffff]
[ 0.200781] pci_bus 0000:07: resource 6 [mem 0x000a0000-0x000bffff]
[ 0.200784] pci_bus 0000:07: resource 7 [mem 0x000d0000-0x000d3fff]
[ 0.200787] pci_bus 0000:07: resource 8 [mem 0x000d4000-0x000d7fff]
[ 0.200790] pci_bus 0000:07: resource 9 [mem 0x000d8000-0x000dbfff]
[ 0.200793] pci_bus 0000:07: resource 10 [mem 0x60000000-0xfebfffff]
[ 0.200796] pci_bus 0000:08: resource 0 [io 0x5000-0x50ff]
[ 0.200799] pci_bus 0000:08: resource 1 [io 0x5400-0x54ff]
[ 0.200802] pci_bus 0000:08: resource 2 [mem 0x64000000-0x67ffffff pref]
[ 0.200805] pci_bus 0000:08: resource 3 [mem 0x68000000-0x6bffffff]
[ 0.200880] NET: Registered protocol family 2
[ 0.201247] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.201275] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.201318] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.201360] TCP: reno registered
[ 0.201364] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.201378] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.201471] NET: Registered protocol family 1
[ 0.203864] pci 0000:01:00.0: Video device with shadowed ROM
[ 0.203888] PCI: CLS mismatch (64 != 16), using 64 bytes
[ 0.203967] Unpacking initramfs...
[ 1.648996] Freeing initrd memory: 8684K (f657c000 - f6df7000)
[ 1.649167] Simple Boot Flag at 0x36 set to 0x1
[ 1.649448] microcode: CPU0 sig=0x6f2, pf=0x20, revision=0x5c
[ 1.649461] microcode: CPU1 sig=0x6f2, pf=0x20, revision=0x5c
[ 1.649593] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 1.649643] Scanning for low memory corruption every 60 seconds
[ 1.650190] futex hash table entries: 512 (order: 3, 32768 bytes)
[ 1.650257] audit: initializing netlink subsys (disabled)
[ 1.650295] audit: type=2000 audit(1447280635.649:1): initialized
[ 1.650757] HugeTLB registered 2 MB page size, pre-allocated 0 pages
[ 1.650832] zbud: loaded
[ 1.650994] VFS: Disk quotas dquot_6.5.2
[ 1.651035] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.651316] msgmni has been set to 1699
[ 1.651375] Key type big_key registered
[ 1.651927] bounce: pool size: 64 pages
[ 1.651953] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 1.652038] io scheduler noop registered
[ 1.652043] io scheduler deadline registered
[ 1.652103] io scheduler cfq registered (default)
[ 1.652576] pcieport 0000:00:01.0: irq 40 for MSI/MSI-X
[ 1.652908] pcieport 0000:00:1c.0: irq 41 for MSI/MSI-X
[ 1.653286] pcieport 0000:00:1c.1: irq 42 for MSI/MSI-X
[ 1.653653] pcieport 0000:00:1c.2: irq 43 for MSI/MSI-X
[ 1.653834] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 1.653866] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
[ 1.653955] vesafb: mode is 1024x768x32, linelength=4096, pages=0
[ 1.653958] vesafb: scrolling: redraw
[ 1.653961] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.653991] vesafb: framebuffer at 0xd0000000, mapped to 0xf7680000, using 3072k, total 3072k
[ 1.714147] Console: switching to colour frame buffer device 128x48
[ 1.774012] fb0: VESA VGA frame buffer device
[ 1.774045] intel_idle: does not run on family 6 model 15
[ 1.774125] GHES: HEST is not enabled!
[ 1.774222] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled
[ 1.775577] Non-volatile memory driver v1.3
[ 1.775583] Linux agpgart interface v0.103
[ 1.776079] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.776089] ehci-pci: EHCI PCI platform driver
[ 1.776369] ehci-pci 0000:00:1d.7: EHCI Host Controller
[ 1.776380] ehci-pci 0000:00:1d.7: new USB bus registered, assigned bus number 1
[ 1.776400] ehci-pci 0000:00:1d.7: debug port 1
[ 1.780318] ehci-pci 0000:00:1d.7: cache line size of 64 is not supported
[ 1.780346] ehci-pci 0000:00:1d.7: irq 23, io mem 0xf0c04000
[ 1.786026] ehci-pci 0000:00:1d.7: USB 2.0 started, EHCI 1.00
[ 1.786105] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.786109] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.786112] usb usb1: Product: EHCI Host Controller
[ 1.786115] usb usb1: Manufacturer: Linux 3.16.7-29-desktop ehci_hcd
[ 1.786118] usb usb1: SerialNumber: 0000:00:1d.7
[ 1.786354] hub 1-0:1.0: USB hub found
[ 1.786369] hub 1-0:1.0: 8 ports detected
[ 1.786988] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 1.786995] uhci_hcd: USB Universal Host Controller Interface driver
[ 1.787273] uhci_hcd 0000:00:1d.0: UHCI Host Controller
[ 1.787282] uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
[ 1.787293] uhci_hcd 0000:00:1d.0: detected 2 ports
[ 1.787318] uhci_hcd 0000:00:1d.0: irq 23, io base 0x00001800
[ 1.787397] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.787400] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.787404] usb usb2: Product: UHCI Host Controller
[ 1.787407] usb usb2: Manufacturer: Linux 3.16.7-29-desktop uhci_hcd
[ 1.787409] usb usb2: SerialNumber: 0000:00:1d.0
[ 1.787628] hub 2-0:1.0: USB hub found
[ 1.787639] hub 2-0:1.0: 2 ports detected
[ 1.788102] uhci_hcd 0000:00:1d.1: UHCI Host Controller
[ 1.788111] uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
[ 1.788120] uhci_hcd 0000:00:1d.1: detected 2 ports
[ 1.788160] uhci_hcd 0000:00:1d.1: irq 19, io base 0x00001820
[ 1.788235] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.788239] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.788242] usb usb3: Product: UHCI Host Controller
[ 1.788245] usb usb3: Manufacturer: Linux 3.16.7-29-desktop uhci_hcd
[ 1.788248] usb usb3: SerialNumber: 0000:00:1d.1
[ 1.788466] hub 3-0:1.0: USB hub found
[ 1.788478] hub 3-0:1.0: 2 ports detected
[ 1.788925] uhci_hcd 0000:00:1d.2: UHCI Host Controller
[ 1.788934] uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
[ 1.788945] uhci_hcd 0000:00:1d.2: detected 2 ports
[ 1.788983] uhci_hcd 0000:00:1d.2: irq 18, io base 0x00001840
[ 1.789068] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.789072] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.789075] usb usb4: Product: UHCI Host Controller
[ 1.789078] usb usb4: Manufacturer: Linux 3.16.7-29-desktop uhci_hcd
[ 1.789081] usb usb4: SerialNumber: 0000:00:1d.2
[ 1.789300] hub 4-0:1.0: USB hub found
[ 1.789311] hub 4-0:1.0: 2 ports detected
[ 1.789754] uhci_hcd 0000:00:1d.3: UHCI Host Controller
[ 1.789763] uhci_hcd 0000:00:1d.3: new USB bus registered, assigned bus number 5
[ 1.789772] uhci_hcd 0000:00:1d.3: detected 2 ports
[ 1.789811] uhci_hcd 0000:00:1d.3: irq 16, io base 0x00001860
[ 1.789887] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 1.789891] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.789894] usb usb5: Product: UHCI Host Controller
[ 1.789897] usb usb5: Manufacturer: Linux 3.16.7-29-desktop uhci_hcd
[ 1.789900] usb usb5: SerialNumber: 0000:00:1d.3
[ 1.790128] hub 5-0:1.0: USB hub found
[ 1.790139] hub 5-0:1.0: 2 ports detected
[ 1.790430] i8042: PNP: PS/2 Controller [PNP0303:PS2K,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
[ 1.793186] serio: i8042 KBD port at 0x60,0x64 irq 1
[ 1.793246] serio: i8042 AUX port at 0x60,0x64 irq 12
[ 1.793456] mousedev: PS/2 mouse device common for all mice
[ 1.793661] rtc_cmos 00:03: RTC can wake from S4
[ 1.793880] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0
[ 1.793917] rtc_cmos 00:03: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
[ 1.793941] ledtrig-cpu: registered to indicate activity on CPUs
[ 1.793969] hidraw: raw HID events driver (C) Jiri Kosina
[ 1.794180] usbcore: registered new interface driver usbhid
[ 1.794182] usbhid: USB HID core driver
[ 1.794301] TCP: cubic registered
[ 1.794357] NET: Registered protocol family 10
[ 1.795041] Using IPI No-Shortcut mode
[ 1.795286] registered taskstats version 1
[ 1.795344] AppArmor: AppArmor sha1 policy hashing enabled
[ 1.795999] Magic number: 7:16:401
[ 1.796138] rtc_cmos 00:03: setting system clock to 2015-11-11 22:23:56 UTC (1447280636)
[ 1.796255] PM: Checking hibernation image partition /dev/sda5
[ 1.815383] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0
[ 2.493197] psmouse serio1: synaptics: Touchpad model: 1, fw: 6.3, id: 0x9280b1, caps: 0xa04713/0x204000/0x0, board id: 3655, fw id: 304412
[ 2.493203] psmouse serio1: synaptics: Toshiba Satellite A200 detected, limiting rate to 40pps.
[ 2.526377] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input2
[ 2.528931] PM: Hibernation image not present or could not be loaded.
[ 2.529472] Freeing unused kernel memory: 728K (c0bfc000 - c0cb2000)
[ 2.529576] Write protecting the kernel text: 5728k
[ 2.529670] Write protecting the kernel read-only data: 3960k
[ 2.529672] NX-protecting the kernel data: 6560k
[ 2.532268] systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
[ 2.532843] random: systemd urandom read with 6 bits of entropy available
[ 2.652026] tsc: Refined TSC clocksource calibration: 1728.999 MHz
[ 2.703048] usb 3-1: new low-speed USB device number 2 using uhci_hcd
[ 2.809838] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input3
[ 2.809994] ACPI: Lid Switch [LID]
[ 2.810150] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input4
[ 2.810213] ACPI: Power Button [PWRB]
[ 2.810349] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5
[ 2.810403] ACPI: Power Button [PWRF]
[ 2.817406] ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
[ 2.823373] acpi device:02: registered as cooling_device0
[ 2.823525] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input6
[ 2.840913] [drm] Initialized drm 1.1.0 20060810
[ 2.843543] wmi: Mapper loaded
[ 2.854315] checking generic (d0000000 300000) vs hw (d0000000 10000000)
[ 2.854319] fb: switching to nouveaufb from VESA VGA
[ 2.854353] Console: switching to colour dummy device 80x25
[ 2.857344] nouveau [ DEVICE][0000:01:00.0] BOOT0 : 0x046700a3
[ 2.857351] nouveau [ DEVICE][0000:01:00.0] Chipset: G72 (NV46)
[ 2.857354] nouveau [ DEVICE][0000:01:00.0] Family : NV40
[ 2.857433] nouveau [ VBIOS][0000:01:00.0] checking PRAMIN for image...
[ 2.868226] usb 3-1: New USB device found, idVendor=046d, idProduct=c024
[ 2.868232] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 2.868236] usb 3-1: Product: USB-PS/2 Optical Mouse
[ 2.868239] usb 3-1: Manufacturer: B16_b_02
[ 2.886688] input: B16_b_02 USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/0003:046D:C024.0001/input/input7
[ 2.886884] hid-generic 0003:046D:C024.0001: input,hidraw0: USB HID v1.10 Mouse [B16_b_02 USB-PS/2 Optical Mouse] on usb-0000:00:1d.1-1/input0
[ 2.889351] ata_piix 0000:00:1f.2: version 2.13
[ 2.890210] ata_piix 0000:00:1f.2: MAP [ P0 P2 IDE IDE ]
[ 2.905156] firewire_ohci 0000:07:06.1: added OHCI v1.10 device as card 0, 4 IR + 8 IT contexts, quirks 0x2
[ 2.905306] yenta_cardbus 0000:07:06.0: enabling device (0000 -> 0003)
[ 2.905481] yenta_cardbus 0000:07:06.0: CardBus bridge found [1179:ff10]
[ 2.905507] yenta_cardbus 0000:07:06.0: Enabling burst memory read transactions
[ 2.905514] yenta_cardbus 0000:07:06.0: Using CSCINT to route CSC interrupts to PCI
[ 2.905517] yenta_cardbus 0000:07:06.0: Routing CardBus interrupts to PCI
[ 2.905525] yenta_cardbus 0000:07:06.0: TI: mfunc 0x01a01b22, devctl 0x66
[ 2.961120] nouveau [ VBIOS][0000:01:00.0] ... appears to be valid
[ 2.961125] nouveau [ VBIOS][0000:01:00.0] using image from PRAMIN
[ 2.961270] nouveau [ VBIOS][0000:01:00.0] BIT signature found
[ 2.961274] nouveau [ VBIOS][0000:01:00.0] version 05.72.22.74.12
[ 2.961574] nouveau 0000:01:00.0: irq 44 for MSI/MSI-X
[ 2.961587] nouveau [ PMC][0000:01:00.0] MSI interrupts enabled
[ 2.961623] nouveau [ PFB][0000:01:00.0] RAM type: DDR2
[ 2.961626] nouveau [ PFB][0000:01:00.0] RAM size: 128 MiB
[ 2.961629] nouveau [ PFB][0000:01:00.0] ZCOMP: 0 tags
[ 2.976782] nouveau [ VOLT][0000:01:00.0] GPU voltage: 1100000uv
[ 3.007798] nouveau [ PTHERM][0000:01:00.0] FAN control: none / external
[ 3.007809] nouveau [ PTHERM][0000:01:00.0] fan management: automatic
[ 3.007813] nouveau [ PTHERM][0000:01:00.0] internal sensor: yes
[ 3.027833] nouveau [ CLK][0000:01:00.0] 20: core 100 MHz shader 100 MHz memory 270 MHz
[ 3.027839] nouveau [ CLK][0000:01:00.0] 21: core 200 MHz shader 200 MHz memory 400 MHz
[ 3.027845] nouveau [ CLK][0000:01:00.0] 22: core 350 MHz shader 350 MHz memory 700 MHz
[ 3.027855] nouveau [ CLK][0000:01:00.0] --: core 199 MHz memory 391 MHz
[ 3.028021] [TTM] Zone kernel: Available graphics memory: 435542 kiB
[ 3.028024] [TTM] Zone highmem: Available graphics memory: 771642 kiB
[ 3.028028] [TTM] Initializing pool allocator
[ 3.028038] [TTM] Initializing DMA pool allocator
[ 3.028058] nouveau [ DRM] VRAM: 124 MiB
[ 3.028060] nouveau [ DRM] GART: 512 MiB
[ 3.028066] nouveau [ DRM] TMDS table version 1.1
[ 3.028069] nouveau W[ DRM] TMDS table script pointers not stubbed
[ 3.028072] nouveau [ DRM] DCB version 3.0
[ 3.028076] nouveau [ DRM] DCB outp 00: 03000323 00000004
[ 3.028079] nouveau [ DRM] DCB outp 01: 01011300 00000028
[ 3.028082] nouveau [ DRM] DCB outp 02: 020223f1 0000c030
[ 3.028085] nouveau [ DRM] DCB conn 00: 0040
[ 3.028089] nouveau [ DRM] DCB conn 01: 0100
[ 3.028092] nouveau [ DRM] DCB conn 02: 0211
[ 3.030535] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 3.030538] [drm] Driver supports precise vblank timestamp query.
[ 3.034277] nouveau [ DRM] MM: using M2MF for buffer copies
[ 3.034287] nouveau [ DRM] Calling LVDS script 6:
[ 3.034290] nouveau [ DRM] 0xC2F5: Parsing digital output script table
[ 3.043146] scsi0 : ata_piix
[ 3.043381] scsi1 : ata_piix
[ 3.043475] ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x18b0 irq 14
[ 3.043479] ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0x18b8 irq 15
[ 3.093031] usb 4-2: new full-speed USB device number 2 using uhci_hcd
[ 3.128819] yenta_cardbus 0000:07:06.0: ISA IRQ mask 0x0cf8, PCI irq 18
[ 3.128824] yenta_cardbus 0000:07:06.0: Socket status: 30000006
[ 3.128830] pci_bus 0000:07: Raising subordinate bus# of parent bus (#07) from #07 to #0b
[ 3.128839] yenta_cardbus 0000:07:06.0: pcmcia: parent PCI bridge window: [io 0x5000-0x5fff]
[ 3.128842] yenta_cardbus 0000:07:06.0: pcmcia: parent PCI bridge window: [mem 0xf0900000-0xf09fffff]
[ 3.128847] pcmcia_socket pcmcia_socket0: cs: memory probe 0xf0900000-0xf09fffff:
[ 3.128853] excluding 0xf0900000-0xf090ffff
[ 3.133838] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
[ 3.133850] excluding 0xc0000-0xcffff 0xdc000-0xfffff
[ 3.133915] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:
[ 3.133938] clean.
[ 3.133987] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
[ 3.133992] excluding 0x60000000-0x600fffff
[ 3.198401] ata2.00: ATAPI: MATSHITADVD-RAM UJ-850S, 1.20, max UDMA/33
[ 3.204340] ata2.00: configured for UDMA/33
[ 3.246766] ata1.00: ATA-8: WDC WD1600BEVS-00VAT0, 11.01A11, max UDMA/133
[ 3.246770] ata1.00: 312581808 sectors, multi 16: LBA48 NCQ (depth 0/32)
[ 3.253078] ata1.00: configured for UDMA/133
[ 3.253227] scsi 0:0:0:0: Direct-Access ATA WDC WD1600BEVS-0 1A11 PQ: 0 ANSI: 5
[ 3.253613] sd 0:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
[ 3.253693] sd 0:0:0:0: [sda] Write Protect is off
[ 3.253697] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 3.253733] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.253839] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 3.257205] scsi 1:0:0:0: CD-ROM MATSHITA DVD-RAM UJ-850S 1.20 PQ: 0 ANSI: 5
[ 3.258145] usb 4-2: New USB device found, idVendor=0483, idProduct=2016
[ 3.258149] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.258153] usb 4-2: Product: Biometric Coprocessor
[ 3.258156] usb 4-2: Manufacturer: STMicroelectronics
[ 3.267968] scsi 1:0:0:0: Attached scsi generic sg1 type 5
[ 3.301216] sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
[ 3.302057] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.317223] nouveau [ DRM] Setting dpms mode 3 on TV encoder (output 2)
[ 3.318867] sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
[ 3.318873] cdrom: Uniform CD-ROM driver Revision: 3.20
[ 3.319247] sr 1:0:0:0: Attached scsi CD-ROM sr0
[ 3.379189] nouveau [ DRM] allocated 1280x800 fb: 0x9000, bo f6b46c00
[ 3.379336] fbcon: nouveaufb (fb0) is primary device
[ 3.400097] nouveau [ DRM] Calling LVDS script 2:
[ 3.400101] nouveau [ DRM] 0xC356: Parsing digital output script table
[ 3.406150] firewire_core 0000:07:06.1: created device fw0: GUID 00080da0d1755747, S400
[ 3.534971] nouveau [ DRM] Calling LVDS script 5:
[ 3.534975] nouveau [ DRM] 0xC2E6: Parsing digital output script table
[ 3.535033] Console: switching to colour frame buffer device 160x50
[ 3.536877] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer device
[ 3.536880] nouveau 0000:01:00.0: registered panic notifier
[ 3.544052] [drm] Initialized nouveau 1.1.2 20120801 for 0000:01:00.0 on minor 0
[ 3.652113] Switched to clocksource tsc
[ 3.678242] random: nonblocking pool is initialized
[ 4.128041] raid6: mmxx1 2281 MB/s
[ 4.145020] raid6: mmxx2 2609 MB/s
[ 4.162026] raid6: sse1x1 1359 MB/s
[ 4.179006] raid6: sse1x2 1855 MB/s
[ 4.196024] raid6: sse2x1 2554 MB/s
[ 4.213016] raid6: sse2x2 3148 MB/s
[ 4.213019] raid6: using algorithm sse2x2 (3148 MB/s)
[ 4.213021] raid6: using ssse3x1 recovery algorithm
[ 4.213403] xor: measuring software checksum speed
[ 4.223011] pIII_sse : 6276.000 MB/sec
[ 4.233004] prefetch64-sse: 7148.000 MB/sec
[ 4.233006] xor: using function: prefetch64-sse (7148.000 MB/sec)
[ 4.240062] Btrfs loaded, assert=on
[ 4.252963] BTRFS: device fsid d6934db3-3ac9-49d0-83db-287be7b995a5 devid 1 transid 56835 /dev/sda6
[ 4.279259] PM: Marking nosave pages: [mem 0x0009f000-0x000fffff]
[ 4.279268] PM: Basic memory bitmaps created
[ 4.289918] PM: Basic memory bitmaps freed
[ 4.289931] video LNXVIDEO:00: Restoring backlight state
[ 4.297408] PM: Starting manual resume from disk
[ 4.297416] PM: Hibernation image partition 8:5 present
[ 4.297419] PM: Looking for hibernation image.
[ 4.313038] PM: Image not found (code -22)
[ 4.313041] PM: Hibernation image not present or could not be loaded.
[ 4.435306] BTRFS info (device sda6): disk space caching is enabled
[ 6.060219] systemd[1]: RTC configured in localtime, applying delta of 60 minutes to system time.
[ 7.339431] systemd-fstab-generator[337]: Checking was requested for /dev/sda2, but /sbin/fsck.ntfs cannot be used: No such file or directory
[ 7.529273] device-mapper: uevent: version 1.0.3
[ 7.529365] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
[ 9.326709] BTRFS info (device sda6): disk space caching is enabled
[ 10.664892] coretemp coretemp.0: Using relative temperature scale!
[ 10.664913] coretemp coretemp.0: Using relative temperature scale!
[ 10.720864] ACPI: Fan [FAN0] (off)
[ 10.771917] toshiba_bluetooth: Detected Toshiba ACPI Bluetooth device - installing RFKill handler
[ 10.887087] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 10.892090] ACPI: AC Adapter [ADP0] (on-line)
[ 10.973286] Monitor-Mwait will be used to enter C-1 state
[ 10.973297] Monitor-Mwait will be used to enter C-2 state
[ 10.973304] Monitor-Mwait will be used to enter C-3 state
[ 10.973310] tsc: Marking TSC unstable due to TSC halts in idle
[ 10.973333] ACPI: acpi_idle registered with cpuidle
[ 10.973373] Switched to clocksource hpet
[ 10.979927] intel_rng: FWH not detected
[ 10.994181] thermal LNXTHERM:00: registered as thermal_zone0
[ 10.994207] ACPI: Thermal Zone [TZ00] (32 C)
[ 10.995790] thermal LNXTHERM:01: registered as thermal_zone1
[ 10.995801] ACPI: Thermal Zone [TZ01] (28 C)
[ 11.037334] ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
[ 11.037349] ACPI: Battery Slot [BAT0] (battery present)
[ 11.095171] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 11.173996] input: PC Speaker as /devices/platform/pcspkr/input/input8
[ 11.386350] sdhci: Secure Digital Host Controller Interface driver
[ 11.386355] sdhci: Copyright(c) Pierre Ossman
[ 11.441303] toshiba_acpi: Toshiba Laptop ACPI Extras version 0.20
[ 11.451679] input: Toshiba input device as /devices/virtual/input/input9
[ 11.470803] toshiba_acpi: Accelerometer not supported
[ 11.541402] ACPI Warning: SystemIO range 0x000018c0-0x000018df conflicts with OpRegion 0x000018c0-0x000018cf (\_SB_.PCI0.SBUS.SMBI) (20140424/utaddress-258)
[ 11.541413] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.722234] ACPI Warning: SystemIO range 0x00001028-0x0000102f conflicts with OpRegion 0x00001000-0x0000107f (\PMIO) (20140424/utaddress-258)
[ 11.722247] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.722253] ACPI Warning: SystemIO range 0x000011b0-0x000011bf conflicts with OpRegion 0x00001180-0x000011bb (\GPIO) (20140424/utaddress-258)
[ 11.722259] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.722261] ACPI Warning: SystemIO range 0x00001180-0x000011af conflicts with OpRegion 0x00001180-0x000011bb (\GPIO) (20140424/utaddress-258)
[ 11.722266] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 11.722269] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 11.826184] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c0000-0x0fffff:
[ 11.826196] excluding 0xc0000-0xcffff 0xdc000-0xfffff
[ 11.826262] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa0000000-0xa0ffffff:
[ 11.826285] clean.
[ 11.826335] pcmcia_socket pcmcia_socket0: cs: memory probe 0x60000000-0x60ffffff:
[ 11.826340] excluding 0x60000000-0x600fffff
[ 11.906916] leds_ss4200: no LED devices found
[ 11.993385] iTCO_vendor_support: vendor-support=0
[ 12.089160] cfg80211: Calling CRDA to update world regulatory domain
[ 12.114619] sdhci-pci 0000:07:06.3: SDHCI controller found [104c:803c] (rev 0)
[ 12.114808] mmc0: no vqmmc regulator found
[ 12.114811] mmc0: no vmmc regulator found
[ 12.115038] mmc0: SDHCI controller on PCI [0000:07:06.3] using DMA
[ 12.123397] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[ 12.123453] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, TCOBASE=0x1060)
[ 12.123623] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[ 12.347967] sky2: driver version 1.30
[ 12.348244] sky2 0000:02:00.0: Yukon-2 FE chip revision 3
[ 12.348314] sky2 0000:02:00.0: irq 45 for MSI/MSI-X
[ 12.348731] sky2 0000:02:00.0 eth0: addr 00:a0:d1:75:57:47
[ 12.418737] snd_hda_intel 0000:00:1b.0: irq 46 for MSI/MSI-X
[ 12.652373] sound hdaudioC0D0: autoconfig: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
[ 12.652380] sound hdaudioC0D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[ 12.652384] sound hdaudioC0D0: hp_outs=1 (0x15/0x0/0x0/0x0/0x0)
[ 12.652387] sound hdaudioC0D0: mono: mono_out=0x0
[ 12.652389] sound hdaudioC0D0: inputs:
[ 12.652393] sound hdaudioC0D0: Internal Mic=0x19
[ 12.652397] sound hdaudioC0D0: Mic=0x18
[ 12.664581] input: HDA Digital PCBeep as /devices/pci0000:00/0000:00:1b.0/sound/card0/hdaudioC0D0/input10
[ 12.665895] input: HDA Intel Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input11
[ 12.666072] input: HDA Intel Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input12
[ 12.696791] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, in-tree:s
[ 12.696798] iwl3945: Copyright(c) 2003-2011 Intel Corporation
[ 12.696897] iwl3945 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
[ 12.752184] iwl3945 0000:03:00.0: Tunable channels: 11 802.11bg, 13 802.11a channels
[ 12.752190] iwl3945 0000:03:00.0: Detected Intel Wireless WiFi Link 3945ABG
[ 12.752261] iwl3945 0000:03:00.0: irq 47 for MSI/MSI-X
[ 12.777364] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[ 12.884732] cfg80211: World regulatory domain updated:
[ 12.884738] cfg80211: DFS Master region: unset
[ 12.884741] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
[ 12.884745] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.884748] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.884751] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.884754] cfg80211: (5170000 KHz - 5250000 KHz @ 160000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.884757] cfg80211: (5250000 KHz - 5330000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 12.884760] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
[ 12.884763] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
[ 12.884766] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
[ 15.450068] Adding 2096996k swap on /dev/sda5. Priority:-1 extents:1 across:2096996k FS
[ 15.471963] fuse init (API version 7.23)
[ 16.449188] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
[ 16.608490] XFS (sda7): Mounting V5 Filesystem
[ 16.733383] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[ 18.168421] XFS (sda7): Ending clean mount
[ 19.146901] audit: type=1305 audit(1447277053.849:2): audit_pid=629 old=0 auid=4294967295 ses=4294967295 res=1
[ 21.238156] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 21.248799] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[ 21.253932] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 26.410387] sky2 0000:02:00.0 enp2s0: enabling interface
[ 26.410546] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 28.185337] sky2 0000:02:00.0 enp2s0: Link is up at 100 Mbps, full duplex, flow control both
[ 28.185337] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 28.514759] NET: Registered protocol family 17
[ 28.603311] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev enp2s0
[ 28.603327] ll header: 00000000: 00 a0 d1 75 57 47 cc a2 23 06 46 7a 08 00 ...uWG..#.Fz..
[ 29.825061] SFW2-INext-DROP-DEFLT IN=enp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:02a0:d1ff:fe75:5747 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=428 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=388
[ 29.827460] SFW2-INext-DROP-DEFLT IN=enp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:02a0:d1ff:fe75:5747 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=258 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=218
[ 30.075700] SFW2-INext-DROP-DEFLT IN=enp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:02a0:d1ff:fe75:5747 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=428 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=388
[ 30.326033] SFW2-INext-DROP-DEFLT IN=enp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:02a0:d1ff:fe75:5747 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=428 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=388
[ 30.526338] SFW2-INext-DROP-DEFLT IN=enp2s0 OUT= MAC= SRC=fe80:0000:0000:0000:02a0:d1ff:fe75:5747 DST=ff02:0000:0000:0000:0000:0000:0000:00fb LEN=398 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=UDP SPT=5353 DPT=5353 LEN=358
[ 33.633187] IPv4: martian source 255.255.255.255 from 192.168.1.1, on dev enp2s0
[ 33.633205] ll header: 00000000: 00 a0 d1 75 57 47 cc a2 23 06 46 7a 08 00 ...uWG..#.Fz..
[ 130.411827] SFW2-INext-DROP-DEFLT IN=enp2s0 OUT= MAC=00:a0:d1:75:57:47:cc:a2:23:06:46:7a:08:00 SRC=192.168.1.1 DST=192.168.1.3 LEN=321 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=1900 DPT=52188 LEN=301
[ 386.907227] perf interrupt took too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[ 424.328106] [sched_delayed] \x014CE: hpet increased min_delta_ns to 20115 nsec
[ 450.168472] [sched_delayed] \x014CE: hpet increased min_delta_ns to 30172 nsec
[ 822.416306] perf interrupt took too long (5021 > 5000), lowering kernel.perf_event_max_sample_rate to 25000
[ 1025.599723] systemd-fstab-generator[2973]: Checking was requested for /dev/sda2, but /sbin/fsck.ntfs cannot be used: No such file or directory
[ 1026.614628] systemd-fstab-generator[2996]: Checking was requested for /dev/sda2, but /sbin/fsck.ntfs cannot be used: No such file or directory
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: illegal snapshot, cannot be deleted
2015-11-11 22:11 illegal snapshot, cannot be deleted Vedran Vucic
@ 2015-11-12 12:32 ` Austin S Hemmelgarn
2015-11-13 16:12 ` Vedran Vucic
0 siblings, 1 reply; 17+ messages in thread
From: Austin S Hemmelgarn @ 2015-11-12 12:32 UTC (permalink / raw)
To: Vedran Vucic, linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 3444 bytes --]
On 2015-11-11 17:11, Vedran Vucic wrote:
> Hello,
>
> I use OpenSuse 13.2 on my Toshiba Satellite laptop. I noticed that I run
> out of disk space, checked documentation and I realized that there were
> many snapshots. I used Yast Snapper to delete snapshots.
> I noticed that one snapshot with number 748 could not be deleted.
> I entered terminal and after the command:
> snapper -c root delete 748
> I got message Illegal snapshot.
This sounds like some sort of issue with snapper, not BTRFS itself, but
see below for some suggestions.
> I woudl like to delete it since it is old one.
> Please find details about my system as requested on your wiki page.
> uname -a
> Linux linux-jjcc.site 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23 00:46:04
> UTC 2015 (6be6a97) i686 i686 i386 GNU/Linux
>
> btrfs --version
> btrfs-progs v4.0+20150429
>
> btrfs fi show
> Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
> Total devices 1 FS bytes used 10.98GiB
> devid 1 size 18.71GiB used 18.71GiB path /dev/sda6
>
> btrfs fi df /
> Data, single: total=15.19GiB, used=10.37GiB
> System, DUP: total=8.00MiB, used=16.00KiB
> System, single: total=4.00MiB, used=0.00B
> Metadata, DUP: total=1.75GiB, used=622.53MiB
> Metadata, single: total=8.00MiB, used=0.00B
> GlobalReserve, single: total=208.00MiB, used=0.00B
> Please find attached dmesg.log as requested.
>
> Please advise what have to do in order to delete snapshot that is reported
> to be illegal.
Have you tried running 'btrfs subvolume delete' on the snapshot? You'll
have to find the full path to it first of course, but that shouldn't be
too hard. Based on the lack of BTRFS error messages in the kernel log
you posted, I'm pretty certain that this isn't an issue with the
filesystem itself (although the filesystem doesn't look particularly
healthy, see further below), so manually deleting the snapshot using the
regular BTRFS commands should work just fine. That said, you may also
want to look into changing the config for snapper, as it has a
ridiculously aggressive retention policy for snapshots by default, which
tends to lead to excessive space usage on filesystems smaller than about
250GB.
You may also want to look at running a balance on the filesystem, the
numbers from btrfs fi show and btrfs fi df look somewhat worrying,
you've got all the space on the disk allocated as chunks by BTRFS, but
have a significant amount of empty space in those chunks. Given that
fact, ENOSPC issues are a very real possibility, and you'll probably
have to run a series of partial balances to fix this (and it's important
to do it before it becomes a visible issue also, because once you start
getting ENOSPC errors, it is a lot harder to fix). Try running a
balance with '-dusage=0 -musage=0', then re-run repeatedly increasing
the number for both arguments by 5 each time until you get to 50. If a
run complains about 'ENOSPC errors during balance', re-run it with the
same number for -dusage and -musage. If you end up re-running with the
same value 3 times and keep getting the errors, then you're probably
beyond the point of this being fixable, and should just recreate the
filesystem (you do have backups, right?). Otherwise, after finishing
the run with '-dusage=50 -musage=50' successfully, run a full balance
without the dusage and musage options.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-12 12:32 ` Austin S Hemmelgarn
@ 2015-11-13 16:12 ` Vedran Vucic
2015-11-13 16:30 ` Austin S Hemmelgarn
0 siblings, 1 reply; 17+ messages in thread
From: Vedran Vucic @ 2015-11-13 16:12 UTC (permalink / raw)
To: Austin S Hemmelgarn; +Cc: linux-btrfs
Hello,
I succeeded to delete illegal snapshot with command:
btrfs subvolume delete /.snapshots/741/snapshot
When I have done
btrfs balance / -dusage=0 -musage=0
increasing value up to 4o I did not have issues.
But on value 4- for-dusage= and -musage=
I got message that there is no space left on disk.
Do you have any advice how to manage that?
Vedran
On Thu, Nov 12, 2015 at 1:32 PM, Austin S Hemmelgarn
<ahferroin7@gmail.com> wrote:
> On 2015-11-11 17:11, Vedran Vucic wrote:
>>
>> Hello,
>>
>> I use OpenSuse 13.2 on my Toshiba Satellite laptop. I noticed that I run
>> out of disk space, checked documentation and I realized that there were
>> many snapshots. I used Yast Snapper to delete snapshots.
>> I noticed that one snapshot with number 748 could not be deleted.
>> I entered terminal and after the command:
>> snapper -c root delete 748
>> I got message Illegal snapshot.
>
> This sounds like some sort of issue with snapper, not BTRFS itself, but see
> below for some suggestions.
>>
>> I woudl like to delete it since it is old one.
>> Please find details about my system as requested on your wiki page.
>> uname -a
>> Linux linux-jjcc.site 3.16.7-29-desktop #1 SMP PREEMPT Fri Oct 23 00:46:04
>> UTC 2015 (6be6a97) i686 i686 i386 GNU/Linux
>>
>> btrfs --version
>> btrfs-progs v4.0+20150429
>>
>> btrfs fi show
>> Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
>> Total devices 1 FS bytes used 10.98GiB
>> devid 1 size 18.71GiB used 18.71GiB path /dev/sda6
>>
>> btrfs fi df /
>> Data, single: total=15.19GiB, used=10.37GiB
>> System, DUP: total=8.00MiB, used=16.00KiB
>> System, single: total=4.00MiB, used=0.00B
>> Metadata, DUP: total=1.75GiB, used=622.53MiB
>> Metadata, single: total=8.00MiB, used=0.00B
>> GlobalReserve, single: total=208.00MiB, used=0.00B
>> Please find attached dmesg.log as requested.
>>
>> Please advise what have to do in order to delete snapshot that is reported
>> to be illegal.
>
> Have you tried running 'btrfs subvolume delete' on the snapshot? You'll
> have to find the full path to it first of course, but that shouldn't be too
> hard. Based on the lack of BTRFS error messages in the kernel log you
> posted, I'm pretty certain that this isn't an issue with the filesystem
> itself (although the filesystem doesn't look particularly healthy, see
> further below), so manually deleting the snapshot using the regular BTRFS
> commands should work just fine. That said, you may also want to look into
> changing the config for snapper, as it has a ridiculously aggressive
> retention policy for snapshots by default, which tends to lead to excessive
> space usage on filesystems smaller than about 250GB.
>
> You may also want to look at running a balance on the filesystem, the
> numbers from btrfs fi show and btrfs fi df look somewhat worrying, you've
> got all the space on the disk allocated as chunks by BTRFS, but have a
> significant amount of empty space in those chunks. Given that fact, ENOSPC
> issues are a very real possibility, and you'll probably have to run a series
> of partial balances to fix this (and it's important to do it before it
> becomes a visible issue also, because once you start getting ENOSPC errors,
> it is a lot harder to fix). Try running a balance with '-dusage=0
> -musage=0', then re-run repeatedly increasing the number for both arguments
> by 5 each time until you get to 50. If a run complains about 'ENOSPC errors
> during balance', re-run it with the same number for -dusage and -musage. If
> you end up re-running with the same value 3 times and keep getting the
> errors, then you're probably beyond the point of this being fixable, and
> should just recreate the filesystem (you do have backups, right?).
> Otherwise, after finishing the run with '-dusage=50 -musage=50'
> successfully, run a full balance without the dusage and musage options.
>
>
>
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 16:12 ` Vedran Vucic
@ 2015-11-13 16:30 ` Austin S Hemmelgarn
2015-11-13 17:30 ` Vedran Vucic
0 siblings, 1 reply; 17+ messages in thread
From: Austin S Hemmelgarn @ 2015-11-13 16:30 UTC (permalink / raw)
To: Vedran Vucic; +Cc: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 625 bytes --]
On 2015-11-13 11:12, Vedran Vucic wrote:
> Hello,
>
> I succeeded to delete illegal snapshot with command:
> btrfs subvolume delete /.snapshots/741/snapshot
> When I have done
> btrfs balance / -dusage=0 -musage=0
> increasing value up to 4o I did not have issues.
> But on value 4- for-dusage= and -musage=
> I got message that there is no space left on disk.
> Do you have any advice how to manage that?
Can you post the output of 'btrfs fi df' and 'btrfs fi show' again?
Both should have changed after the balance, and I'd need to see what it
looks like now to be able to give any reasonable advice.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 16:30 ` Austin S Hemmelgarn
@ 2015-11-13 17:30 ` Vedran Vucic
2015-11-13 17:55 ` Henk Slager
2015-11-13 18:10 ` Austin S Hemmelgarn
0 siblings, 2 replies; 17+ messages in thread
From: Vedran Vucic @ 2015-11-13 17:30 UTC (permalink / raw)
To: Austin S Hemmelgarn; +Cc: linux-btrfs
Hello,
Here are outputs of commands as you requested:
btrfs fi df /
Data, single: total=8.00GiB, used=7.71GiB
System, DUP: total=32.00MiB, used=16.00KiB
Metadata, DUP: total=1.12GiB, used=377.25MiB
GlobalReserve, single: total=128.00MiB, used=0.00B
btrfs fi show
Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
Total devices 1 FS bytes used 8.08GiB
devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
btrfs-progs v4.0+20150429
Thanks,
vedran
On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
<ahferroin7@gmail.com> wrote:
> On 2015-11-13 11:12, Vedran Vucic wrote:
>>
>> Hello,
>>
>> I succeeded to delete illegal snapshot with command:
>> btrfs subvolume delete /.snapshots/741/snapshot
>> When I have done
>> btrfs balance / -dusage=0 -musage=0
>> increasing value up to 4o I did not have issues.
>> But on value 4- for-dusage= and -musage=
>> I got message that there is no space left on disk.
>> Do you have any advice how to manage that?
>
>
> Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
> should have changed after the balance, and I'd need to see what it looks
> like now to be able to give any reasonable advice.
>
>
^ permalink raw reply [flat|nested] 17+ messages in thread* Re: illegal snapshot, cannot be deleted
2015-11-13 17:30 ` Vedran Vucic
@ 2015-11-13 17:55 ` Henk Slager
2015-11-13 17:57 ` Vedran Vucic
2015-11-13 18:10 ` Austin S Hemmelgarn
1 sibling, 1 reply; 17+ messages in thread
From: Henk Slager @ 2015-11-13 17:55 UTC (permalink / raw)
To: Vedran Vucic; +Cc: Austin S Hemmelgarn, linux-btrfs
Vedran,
I see 2 snapshot numbers (748 and 741), maybe copy-paste error or
typo, but can you confirm that the illegal one is deleted?
/Henk
On Fri, Nov 13, 2015 at 6:30 PM, Vedran Vucic <vedran.vucic@gmail.com> wrote:
> Hello,
>
> Here are outputs of commands as you requested:
> btrfs fi df /
> Data, single: total=8.00GiB, used=7.71GiB
> System, DUP: total=32.00MiB, used=16.00KiB
> Metadata, DUP: total=1.12GiB, used=377.25MiB
> GlobalReserve, single: total=128.00MiB, used=0.00B
>
> btrfs fi show
> Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
> Total devices 1 FS bytes used 8.08GiB
> devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
>
> btrfs-progs v4.0+20150429
>
> Thanks,
>
> vedran
>
> On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> On 2015-11-13 11:12, Vedran Vucic wrote:
>>>
>>> Hello,
>>>
>>> I succeeded to delete illegal snapshot with command:
>>> btrfs subvolume delete /.snapshots/741/snapshot
>>> When I have done
>>> btrfs balance / -dusage=0 -musage=0
>>> increasing value up to 4o I did not have issues.
>>> But on value 4- for-dusage= and -musage=
>>> I got message that there is no space left on disk.
>>> Do you have any advice how to manage that?
>>
>>
>> Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
>> should have changed after the balance, and I'd need to see what it looks
>> like now to be able to give any reasonable advice.
>>
>>
> --
> 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] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 17:55 ` Henk Slager
@ 2015-11-13 17:57 ` Vedran Vucic
0 siblings, 0 replies; 17+ messages in thread
From: Vedran Vucic @ 2015-11-13 17:57 UTC (permalink / raw)
To: Henk Slager; +Cc: Austin S Hemmelgarn, linux-btrfs
Helo,
Yes, Illegal one is deleted. Sorry it was my typo.
Thanks,
vedran
On Fri, Nov 13, 2015 at 6:55 PM, Henk Slager <eye1tm@gmail.com> wrote:
> Vedran,
>
> I see 2 snapshot numbers (748 and 741), maybe copy-paste error or
> typo, but can you confirm that the illegal one is deleted?
>
> /Henk
>
> On Fri, Nov 13, 2015 at 6:30 PM, Vedran Vucic <vedran.vucic@gmail.com> wrote:
>> Hello,
>>
>> Here are outputs of commands as you requested:
>> btrfs fi df /
>> Data, single: total=8.00GiB, used=7.71GiB
>> System, DUP: total=32.00MiB, used=16.00KiB
>> Metadata, DUP: total=1.12GiB, used=377.25MiB
>> GlobalReserve, single: total=128.00MiB, used=0.00B
>>
>> btrfs fi show
>> Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
>> Total devices 1 FS bytes used 8.08GiB
>> devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
>>
>> btrfs-progs v4.0+20150429
>>
>> Thanks,
>>
>> vedran
>>
>> On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
>> <ahferroin7@gmail.com> wrote:
>>> On 2015-11-13 11:12, Vedran Vucic wrote:
>>>>
>>>> Hello,
>>>>
>>>> I succeeded to delete illegal snapshot with command:
>>>> btrfs subvolume delete /.snapshots/741/snapshot
>>>> When I have done
>>>> btrfs balance / -dusage=0 -musage=0
>>>> increasing value up to 4o I did not have issues.
>>>> But on value 4- for-dusage= and -musage=
>>>> I got message that there is no space left on disk.
>>>> Do you have any advice how to manage that?
>>>
>>>
>>> Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
>>> should have changed after the balance, and I'd need to see what it looks
>>> like now to be able to give any reasonable advice.
>>>
>>>
>> --
>> 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] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 17:30 ` Vedran Vucic
2015-11-13 17:55 ` Henk Slager
@ 2015-11-13 18:10 ` Austin S Hemmelgarn
2015-11-13 18:42 ` Hugo Mills
1 sibling, 1 reply; 17+ messages in thread
From: Austin S Hemmelgarn @ 2015-11-13 18:10 UTC (permalink / raw)
To: Vedran Vucic; +Cc: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 1816 bytes --]
On 2015-11-13 12:30, Vedran Vucic wrote:
> Hello,
>
> Here are outputs of commands as you requested:
> btrfs fi df /
> Data, single: total=8.00GiB, used=7.71GiB
> System, DUP: total=32.00MiB, used=16.00KiB
> Metadata, DUP: total=1.12GiB, used=377.25MiB
> GlobalReserve, single: total=128.00MiB, used=0.00B
>
> btrfs fi show
> Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
> Total devices 1 FS bytes used 8.08GiB
> devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
>
> btrfs-progs v4.0+20150429
>
Hmm, that's odd, based on these numbers, you should be having no issue
at all trying to run a balance. You might be hitting some other bug in
the kernel, however, but I don't remember if there were any known bugs
related to ENOSPC or balance in the version you're running. You might
see if trying to re-run the balance with '-dusage=40 -musage=40' works
correctly (I've seen cases where the first run fails, but subsequent
ones work because the first one made some progress despite failing).
> On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> On 2015-11-13 11:12, Vedran Vucic wrote:
>>>
>>> Hello,
>>>
>>> I succeeded to delete illegal snapshot with command:
>>> btrfs subvolume delete /.snapshots/741/snapshot
>>> When I have done
>>> btrfs balance / -dusage=0 -musage=0
>>> increasing value up to 4o I did not have issues.
>>> But on value 4- for-dusage= and -musage=
>>> I got message that there is no space left on disk.
>>> Do you have any advice how to manage that?
>>
>>
>> Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
>> should have changed after the balance, and I'd need to see what it looks
>> like now to be able to give any reasonable advice.
>>
>>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 18:10 ` Austin S Hemmelgarn
@ 2015-11-13 18:42 ` Hugo Mills
2015-11-13 19:40 ` Austin S Hemmelgarn
2015-11-13 20:15 ` Vedran Vucic
0 siblings, 2 replies; 17+ messages in thread
From: Hugo Mills @ 2015-11-13 18:42 UTC (permalink / raw)
To: Austin S Hemmelgarn; +Cc: Vedran Vucic, linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 2648 bytes --]
On Fri, Nov 13, 2015 at 01:10:12PM -0500, Austin S Hemmelgarn wrote:
> On 2015-11-13 12:30, Vedran Vucic wrote:
> >Hello,
> >
> >Here are outputs of commands as you requested:
> > btrfs fi df /
> >Data, single: total=8.00GiB, used=7.71GiB
> >System, DUP: total=32.00MiB, used=16.00KiB
> >Metadata, DUP: total=1.12GiB, used=377.25MiB
> >GlobalReserve, single: total=128.00MiB, used=0.00B
> >
> >btrfs fi show
> >Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
> > Total devices 1 FS bytes used 8.08GiB
> > devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
> >
> >btrfs-progs v4.0+20150429
> >
> Hmm, that's odd, based on these numbers, you should be having no
> issue at all trying to run a balance. You might be hitting some
> other bug in the kernel, however, but I don't remember if there were
> any known bugs related to ENOSPC or balance in the version you're
> running.
There's one specific bug that shows up with ENOSPC exactly like
this. It's in all versions of the kernel, there's no known solution,
and no guaranteed mitigation strategy, I'm afraid. Various things like
balancing, or adding, balancing, and removing a device again have been
tried. Sometimes they seem to help; sometimes they just make the
problem worse.
We average maybe one report a week or so(*) with this particular
set of symptoms.
Hugo.
(*) <waves hands vaguely>
> You might see if trying to re-run the balance with
> '-dusage=40 -musage=40' works correctly (I've seen cases where the
> first run fails, but subsequent ones work because the first one made
> some progress despite failing).
> >On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
> ><ahferroin7@gmail.com> wrote:
> >>On 2015-11-13 11:12, Vedran Vucic wrote:
> >>>
> >>>Hello,
> >>>
> >>>I succeeded to delete illegal snapshot with command:
> >>>btrfs subvolume delete /.snapshots/741/snapshot
> >>>When I have done
> >>>btrfs balance / -dusage=0 -musage=0
> >>>increasing value up to 4o I did not have issues.
> >>>But on value 4- for-dusage= and -musage=
> >>>I got message that there is no space left on disk.
> >>>Do you have any advice how to manage that?
> >>
> >>
> >>Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
> >>should have changed after the balance, and I'd need to see what it looks
> >>like now to be able to give any reasonable advice.
> >>
> >>
>
>
--
Hugo Mills | You can play with your friends' privates, but you
hugo@... carfax.org.uk | can't play with your friends' childrens' privates.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | C++ coding rule
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 18:42 ` Hugo Mills
@ 2015-11-13 19:40 ` Austin S Hemmelgarn
2015-11-13 19:55 ` Hugo Mills
2015-11-13 20:15 ` Vedran Vucic
1 sibling, 1 reply; 17+ messages in thread
From: Austin S Hemmelgarn @ 2015-11-13 19:40 UTC (permalink / raw)
To: Hugo Mills, Vedran Vucic, linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 2904 bytes --]
On 2015-11-13 13:42, Hugo Mills wrote:
> On Fri, Nov 13, 2015 at 01:10:12PM -0500, Austin S Hemmelgarn wrote:
>> On 2015-11-13 12:30, Vedran Vucic wrote:
>>> Hello,
>>>
>>> Here are outputs of commands as you requested:
>>> btrfs fi df /
>>> Data, single: total=8.00GiB, used=7.71GiB
>>> System, DUP: total=32.00MiB, used=16.00KiB
>>> Metadata, DUP: total=1.12GiB, used=377.25MiB
>>> GlobalReserve, single: total=128.00MiB, used=0.00B
>>>
>>> btrfs fi show
>>> Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
>>> Total devices 1 FS bytes used 8.08GiB
>>> devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
>>>
>>> btrfs-progs v4.0+20150429
>>>
>> Hmm, that's odd, based on these numbers, you should be having no
>> issue at all trying to run a balance. You might be hitting some
>> other bug in the kernel, however, but I don't remember if there were
>> any known bugs related to ENOSPC or balance in the version you're
>> running.
>
> There's one specific bug that shows up with ENOSPC exactly like
> this. It's in all versions of the kernel, there's no known solution,
> and no guaranteed mitigation strategy, I'm afraid. Various things like
> balancing, or adding, balancing, and removing a device again have been
> tried. Sometimes they seem to help; sometimes they just make the
> problem worse.
>
> We average maybe one report a week or so with this particular
> set of symptoms.
We should get this listed on the Wiki on the Gotcha's page ASAP,
especially considering that it's a pretty significant bug (not quite as
bad as data corruption, but pretty darn close).
Vedran, could you try running the balance with just '-dusage=40' and
then again with just '-musage=40'? If just one of those fails, it could
help narrow things down significantly.
Hugo, is there anything else known about this issue (I don't recall
seeing it mentioned before, and a quick web search didn't turn up much)?
In particular:
1. Is there any known way to reliably reproduce it (I would assume not,
as that would likely lead to a mitigation strategy. If someone does
find a reliable reproducer, please let me know, I've got some
significant spare processor time and storage space I could dedicate to
getting traces and filesystem images for debugging, and already have
most of the required infrastructure set up for something like this)?
2. Is it contagious (that is, if I send a snapshot from a filesystem
that is affected by it, does the filesystem that receives the snapshot
become affected; if we could find a way to reproduce it, I could easily
answer this question within a couple of minutes of reproducing it)?
3. Do we have any kind of statistics beyond the rate of reports (for
example, does it happen more often on bigger filesystems, or possibly
more frequently with certain chunk profiles)?
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 19:40 ` Austin S Hemmelgarn
@ 2015-11-13 19:55 ` Hugo Mills
2015-11-13 20:20 ` Austin S Hemmelgarn
2015-11-13 21:11 ` Duncan
0 siblings, 2 replies; 17+ messages in thread
From: Hugo Mills @ 2015-11-13 19:55 UTC (permalink / raw)
To: Austin S Hemmelgarn; +Cc: Vedran Vucic, linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 4582 bytes --]
On Fri, Nov 13, 2015 at 02:40:44PM -0500, Austin S Hemmelgarn wrote:
> On 2015-11-13 13:42, Hugo Mills wrote:
> >On Fri, Nov 13, 2015 at 01:10:12PM -0500, Austin S Hemmelgarn wrote:
> >>On 2015-11-13 12:30, Vedran Vucic wrote:
> >>>Hello,
> >>>
> >>>Here are outputs of commands as you requested:
> >>> btrfs fi df /
> >>>Data, single: total=8.00GiB, used=7.71GiB
> >>>System, DUP: total=32.00MiB, used=16.00KiB
> >>>Metadata, DUP: total=1.12GiB, used=377.25MiB
> >>>GlobalReserve, single: total=128.00MiB, used=0.00B
> >>>
> >>>btrfs fi show
> >>>Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
> >>> Total devices 1 FS bytes used 8.08GiB
> >>> devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
> >>>
> >>>btrfs-progs v4.0+20150429
> >>>
> >>Hmm, that's odd, based on these numbers, you should be having no
> >>issue at all trying to run a balance. You might be hitting some
> >>other bug in the kernel, however, but I don't remember if there were
> >>any known bugs related to ENOSPC or balance in the version you're
> >>running.
> >
> > There's one specific bug that shows up with ENOSPC exactly like
> >this. It's in all versions of the kernel, there's no known solution,
> >and no guaranteed mitigation strategy, I'm afraid. Various things like
> >balancing, or adding, balancing, and removing a device again have been
> >tried. Sometimes they seem to help; sometimes they just make the
> >problem worse.
> >
> > We average maybe one report a week or so with this particular
> >set of symptoms.
> We should get this listed on the Wiki on the Gotcha's page ASAP,
> especially considering that it's a pretty significant bug (not quite
> as bad as data corruption, but pretty darn close).
It's certainly mentioned in the FAQ, in the main entry on
unexpected ENOSPC. The text takes you through identifying when there's
the "usual" problem, then goes on to say that if you've hit ENOSPC
with free space still to be unallocated, you've got this issue.
> Vedran, could you try running the balance with just '-dusage=40' and
> then again with just '-musage=40'? If just one of those fails, it
> could help narrow things down significantly.
>
> Hugo, is there anything else known about this issue (I don't recall
> seeing it mentioned before, and a quick web search didn't turn up
> much)?
I grumble about it regularly on IRC, where we get many more reports
of it than on the mailing list. There have been a couple on here that
I can recall, but not many.
> In particular:
> 1. Is there any known way to reliably reproduce it (I would assume
> not, as that would likely lead to a mitigation strategy. If someone
> does find a reliable reproducer, please let me know, I've got some
> significant spare processor time and storage space I could dedicate
> to getting traces and filesystem images for debugging, and already
> have most of the required infrastructure set up for something like
> this)?
None that I know of. I can start asking people for btrfs-image
dumps again, if you want to investigate. I did do that for a while, to
pass them to josef, but he said he didn't need any more of them after
a while. (He was always planning on investigating it, but kept getting
diverted by data corruption bugs, which have higher priority).
> 2. Is it contagious (that is, if I send a snapshot from a filesystem
> that is affected by it, does the filesystem that receives the
> snapshot become affected; if we could find a way to reproduce it, I
> could easily answer this question within a couple of minutes of
> reproducing it)?
No, as far as I know, it doesn't transfer via send/receive.
send/receive is largely equivalent to copying the data by other means
-- receive is implemented almost exclusively in userspace, with only a
couple of ioctls for mucking around with the UUIDs at the end.
> 3. Do we have any kind of statistics beyond the rate of reports (for
> example, does it happen more often on bigger filesystems, or
> possibly more frequently with certain chunk profiles)?
Not that I've noticed, no. We've had it on small and large,
single-device and many devices, HDD and SSD, converted and not
converted. At one point, a couple of years ago, I did think it was
down to converted filesystems, because we had a run of them, but that
seems not to be the case.
Hugo.
--
Hugo Mills | The glass is neither half-full nor half-empty; it is
hugo@... carfax.org.uk | twice as large as it needs to be.
http://carfax.org.uk/ |
PGP: E2AB1DE4 | Dr Jon Whitehead
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 19:55 ` Hugo Mills
@ 2015-11-13 20:20 ` Austin S Hemmelgarn
2015-11-13 21:11 ` Duncan
1 sibling, 0 replies; 17+ messages in thread
From: Austin S Hemmelgarn @ 2015-11-13 20:20 UTC (permalink / raw)
To: Hugo Mills, Vedran Vucic, linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 6393 bytes --]
On 2015-11-13 14:55, Hugo Mills wrote:
> On Fri, Nov 13, 2015 at 02:40:44PM -0500, Austin S Hemmelgarn wrote:
>> On 2015-11-13 13:42, Hugo Mills wrote:
>>> On Fri, Nov 13, 2015 at 01:10:12PM -0500, Austin S Hemmelgarn wrote:
>>>> On 2015-11-13 12:30, Vedran Vucic wrote:
>>>>> Hello,
>>>>>
>>>>> Here are outputs of commands as you requested:
>>>>> btrfs fi df /
>>>>> Data, single: total=8.00GiB, used=7.71GiB
>>>>> System, DUP: total=32.00MiB, used=16.00KiB
>>>>> Metadata, DUP: total=1.12GiB, used=377.25MiB
>>>>> GlobalReserve, single: total=128.00MiB, used=0.00B
>>>>>
>>>>> btrfs fi show
>>>>> Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
>>>>> Total devices 1 FS bytes used 8.08GiB
>>>>> devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
>>>>>
>>>>> btrfs-progs v4.0+20150429
>>>>>
>>>> Hmm, that's odd, based on these numbers, you should be having no
>>>> issue at all trying to run a balance. You might be hitting some
>>>> other bug in the kernel, however, but I don't remember if there were
>>>> any known bugs related to ENOSPC or balance in the version you're
>>>> running.
>>>
>>> There's one specific bug that shows up with ENOSPC exactly like
>>> this. It's in all versions of the kernel, there's no known solution,
>>> and no guaranteed mitigation strategy, I'm afraid. Various things like
>>> balancing, or adding, balancing, and removing a device again have been
>>> tried. Sometimes they seem to help; sometimes they just make the
>>> problem worse.
>>>
>>> We average maybe one report a week or so with this particular
>>> set of symptoms.
>> We should get this listed on the Wiki on the Gotcha's page ASAP,
>> especially considering that it's a pretty significant bug (not quite
>> as bad as data corruption, but pretty darn close).
>
> It's certainly mentioned in the FAQ, in the main entry on
> unexpected ENOSPC. The text takes you through identifying when there's
> the "usual" problem, then goes on to say that if you've hit ENOSPC
> with free space still to be unallocated, you've got this issue.
It should still probably be on the Gotcha's page also, as it definitely
fits the general description of the stuff there.
>> Vedran, could you try running the balance with just '-dusage=40' and
>> then again with just '-musage=40'? If just one of those fails, it
>> could help narrow things down significantly.
>>
>> Hugo, is there anything else known about this issue (I don't recall
>> seeing it mentioned before, and a quick web search didn't turn up
>> much)?
>
> I grumble about it regularly on IRC, where we get many more reports
> of it than on the mailing list. There have been a couple on here that
> I can recall, but not many.
Ah, that would explain it, I'm almost never on IRC.
>
>> In particular:
>> 1. Is there any known way to reliably reproduce it (I would assume
>> not, as that would likely lead to a mitigation strategy. If someone
>> does find a reliable reproducer, please let me know, I've got some
>> significant spare processor time and storage space I could dedicate
>> to getting traces and filesystem images for debugging, and already
>> have most of the required infrastructure set up for something like
>> this)?
>
> None that I know of. I can start asking people for btrfs-image
> dumps again, if you want to investigate. I did do that for a while, to
> pass them to josef, but he said he didn't need any more of them after
> a while. (He was always planning on investigating it, but kept getting
> diverted by data corruption bugs, which have higher priority).
I don't have the experience to be able to properly debug it myself from
images (my expertise has always been finding bugs, not necessarily
fixing them), but was more offering to try and generate images (if we
could find some series of commands that reproduces this at least some of
the time, I have the resources to run a couple of VM's doing that over
and over again until it hits the bug). If I could get some, I might be
able to put some assertions into the kernel so that it panics when
there's an ENOSPC in the balance code, and get a stack trace, but the
more I think about it, the more likely it seems that that isn't going to
be too helpful.
>
>> 2. Is it contagious (that is, if I send a snapshot from a filesystem
>> that is affected by it, does the filesystem that receives the
>> snapshot become affected; if we could find a way to reproduce it, I
>> could easily answer this question within a couple of minutes of
>> reproducing it)?
>
> No, as far as I know, it doesn't transfer via send/receive.
> send/receive is largely equivalent to copying the data by other means
> -- receive is implemented almost exclusively in userspace, with only a
> couple of ioctls for mucking around with the UUIDs at the end.
I thought that might be the case, but wanted to ask just to be safe (I
do local backups on some systems using send/receive, largely because
this means if my regular root filesystem gets corrupted, I can directly
boot the backups, run a couple of commands, and then have a working
system again in about 5 or 10 minutes, but if this could spread through
send/receive, then that makes backups done this way less useful (because
this is something that I would treat similar to regular FS corruption)).
>
>> 3. Do we have any kind of statistics beyond the rate of reports (for
>> example, does it happen more often on bigger filesystems, or
>> possibly more frequently with certain chunk profiles)?
>
> Not that I've noticed, no. We've had it on small and large,
> single-device and many devices, HDD and SSD, converted and not
> converted. At one point, a couple of years ago, I did think it was
> down to converted filesystems, because we had a run of them, but that
> seems not to be the case.
That would seem to me to indicate it's somewhere in the common path for
balance, which narrows things down at least, although not by much. Have
we had anyone try balancing just data chunks or just metadata chunks?
That might narrow things down even further. If it's corruption in the
FS itself, I would assume it's somewhere either in the system chunks,
the metadata chunks, or the space cache (if it's there, mounting with
clear_cache should fix it).
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3019 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 19:55 ` Hugo Mills
2015-11-13 20:20 ` Austin S Hemmelgarn
@ 2015-11-13 21:11 ` Duncan
2015-11-13 21:13 ` Hugo Mills
1 sibling, 1 reply; 17+ messages in thread
From: Duncan @ 2015-11-13 21:11 UTC (permalink / raw)
To: linux-btrfs
Hugo Mills posted on Fri, 13 Nov 2015 19:55:20 +0000 as excerpted:
> receive is implemented almost exclusively in userspace, with only a
> couple of ioctls for mucking around with the UUIDs at the end.
I wasn't aware of that and had assumed kernel space. Apart from the
topic of discussion here, that has implications for the old "how old is
too old" versioning question regarding userspace, so thanks, Hugo. =:^)
--
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] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 21:11 ` Duncan
@ 2015-11-13 21:13 ` Hugo Mills
2015-11-13 23:53 ` Duncan
0 siblings, 1 reply; 17+ messages in thread
From: Hugo Mills @ 2015-11-13 21:13 UTC (permalink / raw)
To: Duncan; +Cc: linux-btrfs
[-- Attachment #1: Type: text/plain, Size: 713 bytes --]
On Fri, Nov 13, 2015 at 09:11:46PM +0000, Duncan wrote:
> Hugo Mills posted on Fri, 13 Nov 2015 19:55:20 +0000 as excerpted:
>
> > receive is implemented almost exclusively in userspace, with only a
> > couple of ioctls for mucking around with the UUIDs at the end.
>
> I wasn't aware of that and had assumed kernel space. Apart from the
> topic of discussion here, that has implications for the old "how old is
> too old" versioning question regarding userspace, so thanks, Hugo. =:^)
Note that send is still heavily kernel-side. It's only receive
that's all in userspace.
Hugo.
--
Hugo Mills |
hugo@... carfax.org.uk | __(_'>
http://carfax.org.uk/ | Squeak!
PGP: E2AB1DE4 |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 21:13 ` Hugo Mills
@ 2015-11-13 23:53 ` Duncan
0 siblings, 0 replies; 17+ messages in thread
From: Duncan @ 2015-11-13 23:53 UTC (permalink / raw)
To: linux-btrfs
Hugo Mills posted on Fri, 13 Nov 2015 21:13:41 +0000 as excerpted:
> On Fri, Nov 13, 2015 at 09:11:46PM +0000, Duncan wrote:
>> Hugo Mills posted on Fri, 13 Nov 2015 19:55:20 +0000 as excerpted:
>>
>> > receive is implemented almost exclusively in userspace, with only a
>> > couple of ioctls for mucking around with the UUIDs at the end.
>>
>> I wasn't aware of that and had assumed kernel space. Apart from the
>> topic of discussion here, that has implications for the old "how old is
>> too old" versioning question regarding userspace, so thanks, Hugo. =:^)
>
> Note that send is still heavily kernel-side. It's only receive
> that's all in userspace.
Being "runtime", send's kernel-side use would be expected.
The more general rule that runtime operations are kernel side, so user
side versioning doesn't have the same importance, unless you're trying to
use userside tools such as check, rescue and recover, generally run on an
unmounted btrfs, to recover from damage, since in the general case that's
where userspace code really goes to work and thus where it's version
becomes important.
That the receive side of the send/receive feature is an exception to this
general rule is the news, since now we have a runtime tool, normally run
on a mounted btrfs, where the userspace code is doing the work and
therefore the userspace version, newer versions having the latest fixes,
becomes important.
--
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] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 18:42 ` Hugo Mills
2015-11-13 19:40 ` Austin S Hemmelgarn
@ 2015-11-13 20:15 ` Vedran Vucic
2015-11-13 20:18 ` Vedran Vucic
1 sibling, 1 reply; 17+ messages in thread
From: Vedran Vucic @ 2015-11-13 20:15 UTC (permalink / raw)
To: Hugo Mills, Austin S Hemmelgarn, Vedran Vucic, linux-btrfs
Hello,
I guess that it might be bug in kernel.
I was successful this:
btrfs balance start / -dusage=50 -musage=35
musage above 35 caused ENOSPC message. Otherwise it was good.
Thanks on support,
vedran
On Fri, Nov 13, 2015 at 7:42 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
> On Fri, Nov 13, 2015 at 01:10:12PM -0500, Austin S Hemmelgarn wrote:
>> On 2015-11-13 12:30, Vedran Vucic wrote:
>> >Hello,
>> >
>> >Here are outputs of commands as you requested:
>> > btrfs fi df /
>> >Data, single: total=8.00GiB, used=7.71GiB
>> >System, DUP: total=32.00MiB, used=16.00KiB
>> >Metadata, DUP: total=1.12GiB, used=377.25MiB
>> >GlobalReserve, single: total=128.00MiB, used=0.00B
>> >
>> >btrfs fi show
>> >Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
>> > Total devices 1 FS bytes used 8.08GiB
>> > devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
>> >
>> >btrfs-progs v4.0+20150429
>> >
>> Hmm, that's odd, based on these numbers, you should be having no
>> issue at all trying to run a balance. You might be hitting some
>> other bug in the kernel, however, but I don't remember if there were
>> any known bugs related to ENOSPC or balance in the version you're
>> running.
>
> There's one specific bug that shows up with ENOSPC exactly like
> this. It's in all versions of the kernel, there's no known solution,
> and no guaranteed mitigation strategy, I'm afraid. Various things like
> balancing, or adding, balancing, and removing a device again have been
> tried. Sometimes they seem to help; sometimes they just make the
> problem worse.
>
> We average maybe one report a week or so(*) with this particular
> set of symptoms.
>
> Hugo.
>
> (*) <waves hands vaguely>
>
>> You might see if trying to re-run the balance with
>> '-dusage=40 -musage=40' works correctly (I've seen cases where the
>> first run fails, but subsequent ones work because the first one made
>> some progress despite failing).
>> >On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
>> ><ahferroin7@gmail.com> wrote:
>> >>On 2015-11-13 11:12, Vedran Vucic wrote:
>> >>>
>> >>>Hello,
>> >>>
>> >>>I succeeded to delete illegal snapshot with command:
>> >>>btrfs subvolume delete /.snapshots/741/snapshot
>> >>>When I have done
>> >>>btrfs balance / -dusage=0 -musage=0
>> >>>increasing value up to 4o I did not have issues.
>> >>>But on value 4- for-dusage= and -musage=
>> >>>I got message that there is no space left on disk.
>> >>>Do you have any advice how to manage that?
>> >>
>> >>
>> >>Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
>> >>should have changed after the balance, and I'd need to see what it looks
>> >>like now to be able to give any reasonable advice.
>> >>
>> >>
>>
>>
>
>
>
> --
> Hugo Mills | You can play with your friends' privates, but you
> hugo@... carfax.org.uk | can't play with your friends' childrens' privates.
> http://carfax.org.uk/ |
> PGP: E2AB1DE4 | C++ coding rule
^ permalink raw reply [flat|nested] 17+ messages in thread
* Re: illegal snapshot, cannot be deleted
2015-11-13 20:15 ` Vedran Vucic
@ 2015-11-13 20:18 ` Vedran Vucic
0 siblings, 0 replies; 17+ messages in thread
From: Vedran Vucic @ 2015-11-13 20:18 UTC (permalink / raw)
To: Hugo Mills, Austin S Hemmelgarn, Vedran Vucic, linux-btrfs
Hello,
My system is on laptop that is not heavy duty such as servers.
openSuse 13.2 was installed approx 2 months ago so the issue did not
appear due to longterm lack of administration or maintenance.
Please let me know if I can help in any other way.
Thanks,
vedran
On Fri, Nov 13, 2015 at 9:15 PM, Vedran Vucic <vedran.vucic@gmail.com> wrote:
> Hello,
>
> I guess that it might be bug in kernel.
> I was successful this:
> btrfs balance start / -dusage=50 -musage=35
>
> musage above 35 caused ENOSPC message. Otherwise it was good.
> Thanks on support,
>
> vedran
>
> On Fri, Nov 13, 2015 at 7:42 PM, Hugo Mills <hugo@carfax.org.uk> wrote:
>> On Fri, Nov 13, 2015 at 01:10:12PM -0500, Austin S Hemmelgarn wrote:
>>> On 2015-11-13 12:30, Vedran Vucic wrote:
>>> >Hello,
>>> >
>>> >Here are outputs of commands as you requested:
>>> > btrfs fi df /
>>> >Data, single: total=8.00GiB, used=7.71GiB
>>> >System, DUP: total=32.00MiB, used=16.00KiB
>>> >Metadata, DUP: total=1.12GiB, used=377.25MiB
>>> >GlobalReserve, single: total=128.00MiB, used=0.00B
>>> >
>>> >btrfs fi show
>>> >Label: none uuid: d6934db3-3ac9-49d0-83db-287be7b995a5
>>> > Total devices 1 FS bytes used 8.08GiB
>>> > devid 1 size 18.71GiB used 10.31GiB path /dev/sda6
>>> >
>>> >btrfs-progs v4.0+20150429
>>> >
>>> Hmm, that's odd, based on these numbers, you should be having no
>>> issue at all trying to run a balance. You might be hitting some
>>> other bug in the kernel, however, but I don't remember if there were
>>> any known bugs related to ENOSPC or balance in the version you're
>>> running.
>>
>> There's one specific bug that shows up with ENOSPC exactly like
>> this. It's in all versions of the kernel, there's no known solution,
>> and no guaranteed mitigation strategy, I'm afraid. Various things like
>> balancing, or adding, balancing, and removing a device again have been
>> tried. Sometimes they seem to help; sometimes they just make the
>> problem worse.
>>
>> We average maybe one report a week or so(*) with this particular
>> set of symptoms.
>>
>> Hugo.
>>
>> (*) <waves hands vaguely>
>>
>>> You might see if trying to re-run the balance with
>>> '-dusage=40 -musage=40' works correctly (I've seen cases where the
>>> first run fails, but subsequent ones work because the first one made
>>> some progress despite failing).
>>> >On Fri, Nov 13, 2015 at 5:30 PM, Austin S Hemmelgarn
>>> ><ahferroin7@gmail.com> wrote:
>>> >>On 2015-11-13 11:12, Vedran Vucic wrote:
>>> >>>
>>> >>>Hello,
>>> >>>
>>> >>>I succeeded to delete illegal snapshot with command:
>>> >>>btrfs subvolume delete /.snapshots/741/snapshot
>>> >>>When I have done
>>> >>>btrfs balance / -dusage=0 -musage=0
>>> >>>increasing value up to 4o I did not have issues.
>>> >>>But on value 4- for-dusage= and -musage=
>>> >>>I got message that there is no space left on disk.
>>> >>>Do you have any advice how to manage that?
>>> >>
>>> >>
>>> >>Can you post the output of 'btrfs fi df' and 'btrfs fi show' again? Both
>>> >>should have changed after the balance, and I'd need to see what it looks
>>> >>like now to be able to give any reasonable advice.
>>> >>
>>> >>
>>>
>>>
>>
>>
>>
>> --
>> Hugo Mills | You can play with your friends' privates, but you
>> hugo@... carfax.org.uk | can't play with your friends' childrens' privates.
>> http://carfax.org.uk/ |
>> PGP: E2AB1DE4 | C++ coding rule
^ permalink raw reply [flat|nested] 17+ messages in thread
end of thread, other threads:[~2015-11-13 23:53 UTC | newest]
Thread overview: 17+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-11-11 22:11 illegal snapshot, cannot be deleted Vedran Vucic
2015-11-12 12:32 ` Austin S Hemmelgarn
2015-11-13 16:12 ` Vedran Vucic
2015-11-13 16:30 ` Austin S Hemmelgarn
2015-11-13 17:30 ` Vedran Vucic
2015-11-13 17:55 ` Henk Slager
2015-11-13 17:57 ` Vedran Vucic
2015-11-13 18:10 ` Austin S Hemmelgarn
2015-11-13 18:42 ` Hugo Mills
2015-11-13 19:40 ` Austin S Hemmelgarn
2015-11-13 19:55 ` Hugo Mills
2015-11-13 20:20 ` Austin S Hemmelgarn
2015-11-13 21:11 ` Duncan
2015-11-13 21:13 ` Hugo Mills
2015-11-13 23:53 ` Duncan
2015-11-13 20:15 ` Vedran Vucic
2015-11-13 20:18 ` Vedran Vucic
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.