Re: Btrfs warnings in kernel 4.13.5

[Juan Orti Alcaine]

2017-10-13 20:15 GMT+02:00 Chris Murphy :
> On Fri, Oct 13, 2017 at 12:02 PM, Duncan <1i5t5.dun...@cox.net> wrote:
>> Those warnings aren't anything to be /too/ worried about.  They are
>> triggered when a btrfs device size isn't a multiple of the btrfs
>> sectorsize (currently 4 KiB on amd64 aka x86_64).  You can manually
>> shrink your btrfs devices the fraction to an exact 4 KiB multiple, or
>> wait a bit, and a new release of btrfs-tools should have a command to do
>> it for you.
>
>
> So it's an open question now why it was created with a device size
> that isn't divisible by 4KiB. Seems like a bad idea to make it easy to
> create virtual block devices based on 512 byte divisions, as it makes
> it easy to end up with unaligned sectors at some point if one of the
> underlying devices is an AF 512e device. Was it manually created? Or
> was it created via the OS installer? Some time ago there was a feature
> proposal for the Fedora installer being able to create bcache and
> dmcache devices, but I haven't seen anything yet.


I'm sure I created all bcache devices with a block size of 4k.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Btrfs warnings in kernel 4.13.5

[Juan Orti Alcaine]

2017-10-13 13:02 GMT+02:00 Duncan <1i5t5.dun...@cox.net>:
> Those warnings aren't anything to be /too/ worried about.  They are
> triggered when a btrfs device size isn't a multiple of the btrfs
> sectorsize (currently 4 KiB on amd64 aka x86_64).  You can manually
> shrink your btrfs devices the fraction to an exact 4 KiB multiple, or
> wait a bit, and a new release of btrfs-tools should have a command to do
> it for you.


Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Btrfs warnings in kernel 4.13.5

[Juan Orti Alcaine]

2017-10-13 10:40 GMT+02:00 Juan Orti Alcaine <j.orti.alca...@gmail.com>:
> Hi,
>
> I've upgraded my system to Fedora 27 and now I see many btrfs
> warnings, although the system seems to be working fine. Is this
> something I should worry about?


I'm getting more warnings:

[  337.822868] [ cut here ]
[  337.822890] WARNING: CPU: 5 PID: 459 at fs/btrfs/ctree.h:1559
btrfs_update_device+0x1be/0x1d0 [btrfs]
[  337.822891] Modules linked in: rfcomm fuse vhost_net vhost tap
xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun
nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter
ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat
ebtable_broute ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6
nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack
libcrc32c iptable_mangle iptable_raw iptable_security bridge stp llc
ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep vfat fat
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel
kvm irqbypass snd_hda_codec_realtek snd_hda_codec_generic
snd_usb_audio snd_hda_codec_hdmi snd_hda_intel snd_hda_codec
snd_hda_core snd_usbmidi_lib eeepc_wmi
[  337.822928]  btusb btrtl uvcvideo snd_hwdep crct10dif_pclmul
crc32_pclmul videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq
videobuf2_core ghash_clmulni_intel videodev intel_cstate asus_wmi
snd_rawmidi intel_uncore btbcm snd_seq_device btintel bluetooth
intel_rapl_perf sparse_keymap media ecdh_generic joydev wmi_bmof
snd_pcm rfkill i2c_i801 video iTCO_wdt iTCO_vendor_support mei_me mei
snd_timer wmi snd soundcore shpchp lpc_ich nfsd auth_rpcgss nfs_acl
lockd grace sunrpc binfmt_misc btrfs xor raid6_pq amdkfd amd_iommu_v2
radeon bcache i2c_algo_bit drm_kms_helper crc32c_intel ttm r8169
serio_raw drm mii
[  337.822963] CPU: 5 PID: 459 Comm: btrfs-cleaner Tainted: GW
  4.13.5-300.fc27.x86_64 #1
[  337.822964] Hardware name: System manufacturer System Product
Name/P8Z68-V LE, BIOS 4102 09/09/2013
[  337.822965] task: 9e98479ecc80 task.stack: b3a4c229
[  337.822983] RIP: 0010:btrfs_update_device+0x1be/0x1d0 [btrfs]
[  337.822984] RSP: 0018:b3a4c2293d28 EFLAGS: 00010206
[  337.822986] RAX: 0fff RBX: 9e9844f3ad20 RCX: 01d1c100fe00
[  337.822987] RDX: 0004 RSI: 3efa RDI: 9e9821e5e000
[  337.822988] RBP: b3a4c2293d70 R08: 3efe R09: b3a4c2293ce0
[  337.822989] R10: 1000 R11: 0003 R12: 9e9844999c00
[  337.822990] R13:  R14: 3eda R15: 9e9821e5e000
[  337.822994] FS:  () GS:9e985ed4()
knlGS:
[  337.822995] CS:  0010 DS:  ES:  CR0: 80050033
[  337.822996] CR2: 1f89b1c4d000 CR3: 00037ce09000 CR4: 000426e0
[  337.822997] Call Trace:
[  337.823017]  btrfs_remove_chunk+0x365/0x870 [btrfs]
[  337.823036]  btrfs_delete_unused_bgs+0x30d/0x3d0 [btrfs]
[  337.823054]  cleaner_kthread+0x165/0x180 [btrfs]
[  337.823057]  kthread+0x125/0x140
[  337.823074]  ? __btree_submit_bio_start+0x20/0x20 [btrfs]
[  337.823078]  ? kthread_park+0x60/0x60
[  337.823081]  ret_from_fork+0x25/0x30
[  337.823083] Code: 4c 89 ff 45 31 c0 ba 10 00 00 00 4c 89 f6 e8 fa
20 ff ff 4c 89 ff e8 f2 ee fc ff e9 d3 fe ff ff 41 bd f4 ff ff ff e9
d0 fe ff ff <0f> ff eb b6 e8 29 bd ab ca 66 0f 1f 84 00 00 00 00 00 66
66 66
[  337.823118] ---[ end trace 3609a7da677d8847 ]---
[  805.824111] FS-Cache: Loaded
[  805.835188] FS-Cache: Netfs 'nfs' registered for caching
[  805.861120] Key type dns_resolver registered
[  805.891629] NFS: Registering the id_resolver key type
[  805.891635] Key type id_resolver registered
[  805.891635] Key type id_legacy registered
[  807.427618] nf_conntrack: default automatic helper assignment has
been turned off for security reasons and CT-based  firewall rule not
found. Use the iptables CT target to attach helpers instead.
[ 2512.070835] [ cut here ]
[ 2512.070873] WARNING: CPU: 4 PID: 14051 at fs/btrfs/ctree.h:1559
btrfs_update_device+0x1be/0x1d0 [btrfs]
[ 2512.070874] Modules linked in: rpcsec_gss_krb5 nfsv4 dns_resolver
nfs fscache rfcomm fuse vhost_net vhost tap xt_CHECKSUM ipt_MASQUERADE
nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns
nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6
xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute ip6table_nat
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle
ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c
iptable_mangle iptable_raw iptable_security bridge stp llc
ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep vfat fat
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel
kvm irqbypass snd_hda_codec_realtek snd_hda_codec_generic
snd_u

Btrfs warnings in kernel 4.13.5

[Juan Orti Alcaine]

Hi,

I've upgraded my system to Fedora 27 and now I see many btrfs
warnings, although the system seems to be working fine. Is this
something I should worry about?

I have a scrub running with no errors so far:

# btrfs scrub status /mnt/btrfs
scrub status for 038b2b48-fd2d-4565-b2b1-d07847ecca8c
scrub started at Thu Oct 12 19:35:55 2017, running for 03:28:41
total bytes scrubbed: 3.35TiB with 0 errors

# uname -a
Linux xenon 4.13.5-300.fc27.x86_64 #1 SMP Thu Oct 5 16:57:11 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

# btrfs --version
btrfs-progs v4.13.2

# btrfs fi show
Label: 'btrfs_raid1'  uuid: 038b2b48-fd2d-4565-b2b1-d07847ecca8c
Total devices 4 FS bytes used 1.81TiB
devid4 size 1.82TiB used 1.19TiB path /dev/bcache32
devid5 size 1.82TiB used 1.19TiB path /dev/bcache16
devid6 size 1.82TiB used 1.19TiB path /dev/bcache0
devid7 size 1.79TiB used 158.00GiB path /dev/bcache48

# btrfs fi usage /mnt/btrfs
Overall:
Device size:   7.24TiB
Device allocated:  3.72TiB
Device unallocated:3.53TiB
Device missing:  0.00B
Used:  3.62TiB
Free (estimated):  1.81TiB  (min: 1.81TiB)
Data ratio:   2.00
Metadata ratio:   2.00
Global reserve:  512.00MiB  (used: 0.00B)

Data,RAID1: Size:1.85TiB, Used:1.80TiB
   /dev/bcache01.18TiB
   /dev/bcache16   1.18TiB
   /dev/bcache32   1.18TiB
   /dev/bcache48 157.00GiB

Metadata,RAID1: Size:7.00GiB, Used:5.78GiB
   /dev/bcache05.00GiB
   /dev/bcache16   4.00GiB
   /dev/bcache32   4.00GiB
   /dev/bcache48   1.00GiB

System,RAID1: Size:32.00MiB, Used:320.00KiB
   /dev/bcache16  32.00MiB
   /dev/bcache32  32.00MiB

Unallocated:
   /dev/bcache0  647.02GiB
   /dev/bcache16 647.98GiB
   /dev/bcache32 645.98GiB
   /dev/bcache48   1.63TiB

All my bcache devices are in writethrough mode:

# bcache-status -s
--- bcache ---
UUIDd82cf90a-756c-4b8a-b871-72714cdae024
Block Size  4.00 KiB
Bucket Size 2.0 MiB
Congested?  False
Read Congestion 2.0ms
Write Congestion20.0ms
Total Cache Size95 GiB
Total Cache Used95 GiB(100%)
Total Cache Unused  0 B(0%)
Evictable Cache 95 GiB(100%)
Replacement Policy  [lru] fifo random
Cache Mode  [writethrough] writeback writearound none
Total Hits  150430(62%)
Total Misses90622
Total Bypass Hits   1036307(100%)
Total Bypass Misses 0
Total Bypassed  2 GiB
--- Backing Device ---
  Device File   /dev/sde4 (8:68)
  bcache Device File/dev/bcache48 (252:48)
  Size  2 TiB
  Cache Mode[writethrough] writeback writearound none
  Readahead 0.0k
  Sequential Cutoff 4.0 MiB
  Merge sequential? False
  State clean
  Writeback?True
  Dirty Data0 B
  Total Hits14066(57%)
  Total Misses  10363
  Total Bypass Hits 40454(100%)
  Total Bypass Misses   0
  Total Bypassed134.3 MiB
--- Cache Device ---
  Device File   /dev/sda4 (8:4)
  Size  95 GiB
  Block Size4.00 KiB
  Bucket Size   2.0 MiB
  Replacement Policy[lru] fifo random
  Discard?  False
  I/O Errors0
  Metadata Written  99.1 MiB
  Data Written  6 GiB
  Buckets   48432
  Cache Used95 GiB(100%)
  Cache Unused  0 B(0%)
--- Backing Device ---
  Device File   /dev/sdb1 (8:17)
  bcache Device File/dev/bcache32 (252:32)
  Size  2 TiB
  Cache Mode[writethrough] writeback writearound none
  Readahead 0.0k
  Sequential Cutoff 4.0 MiB
  Merge sequential? False
  State clean
  Writeback?True
  Dirty Data0 B
  Total Hits28167(40%)
  Total Misses  42227
  Total Bypass Hits 632707(100%)
  Total Bypass Misses   0
  Total Bypassed2 GiB
--- Backing Device ---
  Device File   /dev/sdc1 (8:33)
  bcache Device File/dev/bcache16 (252:16)
  Size  2 TiB
  Cache Mode[writethrough] writeback writearound none
  Readahead 0.0k
  Sequential Cutoff 4.0 MiB
  Merge sequential? False
  State clean
  Writeback?True
  Dirty Data0 B
  Total Hits67948(74%)
  Total 

Re: mount time for big filesystems

[Juan Orti Alcaine]

2017-08-31 13:36 GMT+02:00 Roman Mamedov :
> If you could implement SSD caching in front of your FS (such as lvmcache or
> bcache), that would work wonders for performance in general, and especially
> for mount times. I have seen amazing results with lvmcache (of just 32 GB) for
> a 14 TB FS.

I'm thinking about adding a SSD for my 4 disks RAID1 filesystem, but I
have doubts about how to correctly do it in a multidevice filesystem.

I guess I should make 4 partitions on the SSD and pair them with my
backing devices, then create the btrfs on top of bcache0, bcache1,...
is this the right way to do it?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Home storage with btrfs

[Juan Orti Alcaine]

2017-03-13 12:29 GMT+01:00 Hérikz Nawarro :
> Hello everyone,
>
> Today is safe to use btrfs for home storage? No raid, just secure
> storage for some files and create snapshots from it.
>

In my humble opinion, yes. I'm running a RAID1 btrfs at home for 5
years and I feel the most serious bugs have been fixed, because in the
last two years I have not experienced any issue.

Anyway, keeping your kernel and btrfs-progs updated is a must, and of
course, having good backups. I'm using Fedora and it's fine.

Kind regards.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

kernel BUG at fs/btrfs/delayed-inode.c

[Juan Orti Alcaine]

Hi, today I got this bug after a power failure.

One file that was being written during the power failure, appeared
after reboot as:

$ ls -la data/0/3833
?-. 1 root root 0 ene  1  1970 data/0/3833

I decided to delete it, but I got this bug after a few seconds and the
system halted, I had to reboot it with the magic SysRq keys.

After the reboot, I saw this file as:

# ls -la
ls: no se puede acceder a '3833': No such file or directory
total 0
drwx--. 1 backup backup 4 nov  7 19:48 .
drwx--. 1 backup backup 2 nov  7 09:05 ..
-?? ? ?  ?  ?? 3833

I've already deleted the affected subvolume, and I have not detected
any more problems. Should I worry?

My versions are:

# uname -a
Linux xenon 4.8.6-300.fc25.x86_64 #1 SMP Tue Nov 1 12:36:38 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
# rpm -q btrfs-progs
btrfs-progs-4.8.2-2.fc25.x86_64

I've also reported the bug in the Fedora bugzilla:

https://bugzilla.redhat.com/show_bug.cgi?id=1392557


nov 07 19:24:43 xenon kernel: BTRFS error (device sdb7): err add
delayed dir index item(index: 50) into the deletion tree of the
delayed node(root id: 28557, inode id: 265, errno: -17)
nov 07 19:24:43 xenon kernel: [ cut here ]
nov 07 19:24:43 xenon kernel: kernel BUG at fs/btrfs/delayed-inode.c:1561!
nov 07 19:24:43 xenon kernel: invalid opcode:  [#1] SMP
nov 07 19:24:43 xenon kernel: Modules linked in: xfs libcrc32c rfcomm
fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_set
xt_multiport ip_set_hash_ip nf_conntrack_netbios_ns
nf_conntrack_broadcast
nov 07 19:24:43 xenon kernel:  intel_cstate intel_uncore xor
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi
intel_rapl_perf snd_hda_intel snd_hda_codec uvcvideo snd_usb_audio
snd_hda_core snd_usb
nov 07 19:24:43 xenon kernel: CPU: 0 PID: 10691 Comm: rm Not tainted
4.8.6-300.fc25.x86_64 #1
nov 07 19:24:43 xenon kernel: Hardware name: System manufacturer
System Product Name/P8Z68-V LE, BIOS 4102 09/09/2013
nov 07 19:24:43 xenon kernel: task: 94ccac7a3d00 task.stack:
94cc0bf14000
nov 07 19:24:43 xenon kernel: RIP: 0010:[]
[] btrfs_delete_delayed_dir_index+0x222/0x2c0
[btrfs]
nov 07 19:24:43 xenon kernel: RSP: 0018:94cc0bf17d18  EFLAGS: 00010282
nov 07 19:24:43 xenon kernel: RAX:  RBX:
94ccba0dbdb0 RCX: 
nov 07 19:24:43 xenon kernel: RDX:  RSI:
94cd1ec0e048 RDI: 94cd1ec0e048
nov 07 19:24:43 xenon kernel: RBP: 94cc0bf17d88 R08:
00098b7f R09: 0005
nov 07 19:24:43 xenon kernel: R10: 94cd0703c400 R11:
0483 R12: 94ccba0dbdf8
nov 07 19:24:43 xenon kernel: R13: 94cd071b2800 R14:
0032 R15: 
nov 07 19:24:43 xenon kernel: FS:  7fb8228b5700()
GS:94cd1ec0() knlGS:
nov 07 19:24:43 xenon kernel: CS:  0010 DS:  ES:  CR0: 80050033
nov 07 19:24:43 xenon kernel: CR2: 7f512fa32000 CR3:
00030bd31000 CR4: 000406f0
nov 07 19:24:43 xenon kernel: Stack:
nov 07 19:24:43 xenon kernel:  94cd0ac81a20 94cc0bf17d58
0004 94cd0703c400
nov 07 19:24:43 xenon kernel:  94cd0703c400 0900
6001 0032
nov 07 19:24:43 xenon kernel:  6dbfa5b9 94cc4266da88
94cc6c073d00 3272
nov 07 19:24:43 xenon kernel: Call Trace:
nov 07 19:24:43 xenon kernel:  []
__btrfs_unlink_inode+0x1b1/0x4b0 [btrfs]
nov 07 19:24:43 xenon kernel:  []
btrfs_unlink_inode+0x1c/0x40 [btrfs]
nov 07 19:24:43 xenon kernel:  []
btrfs_unlink+0x6b/0xc0 [btrfs]
nov 07 19:24:43 xenon kernel:  [] vfs_unlink+0x108/0x190
nov 07 19:24:43 xenon kernel:  [] do_unlinkat+0x277/0x2f0
nov 07 19:24:43 xenon kernel:  [] SyS_unlinkat+0x1b/0x30
nov 07 19:24:43 xenon kernel:  []
entry_SYSCALL_64_fastpath+0x1a/0xa4
nov 07 19:24:43 xenon kernel: Code: eb fe ff ff 48 8b 53 10 49 8b bd
f0 01 00 00 41 89 c1 4c 8b 03 48 c7 c6 d0 1b db c0 48 8b 8a 48 03 00
00 4c 89 f2 e8 fe f5 f6 ff <0f> 0b 65 8b 05 8d 96 28 3f 89 c0 48 0f a3
05
nov 07 19:24:43 xenon kernel: RIP  []
btrfs_delete_delayed_dir_index+0x222/0x2c0 [btrfs]
nov 07 19:24:43 xenon kernel:  RSP 
nov 07 19:24:43 xenon kernel: ---[ end trace fb2b0363e7e89d6e ]---


-- 
Juan Orti
https://apuntesderootblog.wordpress.com/
GPG: 61F0 8272 6882 BCA6 3A35  88F6 B630 4B72 DEEB D08B
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Hello world, python-btrfs

[Juan Orti Alcaine]

2016-06-18 0:01 GMT+02:00 Hans van Kranenburg :
> Hi!
>
> After playing around a bit for a few months with a bunch of
> proof-of-concept level scripts to be able to debug my btrfs file
> systems, the inevitable happened:
>
> https://github.com/knorrie/python-btrfs/
>

Hi, I want just to inform you that I've submitted your module to Fedora.

Thanks for your work.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[BUG] unable to handle kernel NULL pointer dereference when removing device

[Juan Orti Alcaine]

Hello, I've hit this bug when removing the device
/dev/mapper/vg_hd04-lv_btrfs_hd04 from this filesystem. The only
peculiarity is that it mixes partitions and a lvm logical volume.

The device was removed successfully and no further errors have been seen.

# btrfs fi show
Label: 'btrfs_raid1'  uuid: 038b2b48-fd2d-4565-b2b1-d07847ecca8c
Total devices 4 FS bytes used 1.90TiB
devid1 size 1.81TiB used 1.30TiB path /dev/sdb4
devid2 size 1.81TiB used 1.30TiB path /dev/sdc4
devid3 size 1.81TiB used 1.30TiB path /dev/sdd4
devid4 size 1.60TiB used 0.00B path
/dev/mapper/vg_hd04-lv_btrfs_hd04

btrfs-progs v4.2.2

# uname -a
Linux xenon 4.2.8-300.fc23.x86_64 #1 SMP Tue Dec 15 16:49:06 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux

# btrfs dev remove /dev/mapper/vg_hd04-lv_btrfs_hd04 /mnt/btrfs

# dmesg
[ 5557.353436] BUG: unable to handle kernel NULL pointer dereference
at 0380
[ 5557.353492] IP: [] bio_get_nr_vecs+0x15/0x40
[ 5557.353532] PGD 0
[ 5557.353547] Oops:  [#1] SMP
[ 5557.353571] Modules linked in: hfsplus hfs minix msdos jfs xfs
libcrc32c xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_set
xt_multiport ip_set_h
ash_ip ip_set nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast
ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_broute
bridge ebtable_filter ebtable_nat ebtables ip6table_mangle
ip6table_raw ip6table_security ip6table_nat nf_conntrack_ipv6
nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables iptable_mangle
iptable_raw iptable_security iptable_nat nf_conntrack_ipv4
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack vfat fat uvcvideo
videobuf2_vmalloc videobuf2_core videobuf2_memops v4l2_common videodev
media intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel kvm
snd_hda_codec_realtek snd_hda_codec_g
eneric snd_hda_codec_hdmi
[ 5557.354070]  crct10dif_pclmul crc32_pclmul snd_hda_intel
snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep
snd_rawmidi snd_seq snd_seq_dev
ice snd_pcm fuse snd_timer iTCO_wdt iTCO_vendor_support snd eeepc_wmi
asus_wmi sparse_keymap rfkill mei_me lpc_ich joydev i2c_i801 shpchp
soundcore mei video
wmi nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc btrfs xor
raid6_pq amdkfd amd_iommu_v2 radeon i2c_algo_bit drm_kms_helper ttm
crc32c_intel drm 802
1q serio_raw garp stp llc mrp r8169 mii
[ 5557.354424] CPU: 1 PID: 1626 Comm: transmission-da Not tainted
4.2.8-300.fc23.x86_64 #1
[ 5557.354467] Hardware name: System manufacturer System Product
Name/P8Z68-V LE, BIOS 4102 09/09/2013
[ 5557.354514] task: 8803f8cc ti: 8803dffb4000 task.ti:
8803dffb4000
[ 5557.354554] RIP: 0010:[]  []
bio_get_nr_vecs+0x15/0x40
[ 5557.354600] RSP: 0018:8803dffb7a88  EFLAGS: 00010246
[ 5557.354629] RAX:  RBX: 1000 RCX: 0100
[ 5557.354666] RDX: 0100 RSI:  RDI: 88040dc296c0
[ 5557.354703] RBP: 8803dffb7a88 R08: 00010050516f R09: 88040c142000
[ 5557.354740] R10: 8803777928a0 R11:  R12: 8803dffb7d30
[ 5557.354777] R13:  R14: 000130e7b360 R15: 88007f2c97b0
[ 5557.354815] FS:  7fc64ffa0700() GS:88041ec4()
knlGS:
[ 5557.354856] CS:  0010 DS:  ES:  CR0: 80050033
[ 5557.354887] CR2: 0380 CR3: 0003df687000 CR4: 000406e0
[ 5557.354923] Stack:
[ 5557.354936]  8803dffb7ae8 a035dae7 

[ 5557.354981]   ea000e2b3740 8803dffb7b68

[ 5557.355028]  ea000e2b3740  8803dffb7d40
0da6c000
[ 5557.355074] Call Trace:
[ 5557.355110]  [] submit_extent_page+0x177/0x1e0 [btrfs]
[ 5557.355160]  [] __do_readpage+0x39e/0x910 [btrfs]
[ 5557.355206]  [] ?
btrfs_create_repair_bio+0x100/0x100 [btrfs]
[ 5557.355257]  [] ? btrfs_real_readdir+0x570/0x570 [btrfs]
[ 5557.355305]  []
__extent_readpages.constprop.41+0x2c4/0x2e0 [btrfs]
[ 5557.355349]  [] ? __add_to_page_cache_locked+0x1c6/0x2b0
[ 5557.355397]  [] ? btrfs_real_readdir+0x570/0x570 [btrfs]
[ 5557.355446]  [] extent_readpages+0x1de/0x1f0 [btrfs]
[ 5557.355491]  [] ? btrfs_real_readdir+0x570/0x570 [btrfs]
[ 5557.355530]  [] ? alloc_pages_current+0x91/0x100
[ 5557.355573]  [] btrfs_readpages+0x1f/0x30 [btrfs]
[ 5557.355608]  [] __do_page_cache_readahead+0x1b6/0x230
[ 5557.355644]  [] force_page_cache_readahead+0x3a/0x60
[ 5557.355680]  [] SyS_fadvise64+0x1f6/0x250
[ 5557.355712]  [] entry_SYSCALL_64_fastpath+0x12/0x71
[ 5557.355746] Code: 5b 5d c3 e8 5e 75 d3 ff 90 90 90 90 90 90 90 90
90 90 90 90 90 90 66 66 66 66 90 48 8b 87 98 00 00 00 55 b9 00 01 00
00 48 89 e5 <48> 8b
90 80 03 00 00 5d 8b 82 00 07 00 00 0f b7 92 2a 07 00 00
[ 5557.355987] RIP  [] bio_get_nr_vecs+0x15/0x40
[ 5557.356022]  RSP 
[ 5557.356041] CR2: 0380
[ 5557.369444] ---[ end trace b3c3f1a1174600de ]---
[ 5557.369446] [ cut here 

Usage of new added disk not updated while doing a balance

[Juan Orti Alcaine]

Hello,

I have added a new disk to my filesystem and I'm doing a balance right
now, but I'm a bit worried that the disk usage does not get updated as
it should. I remember from earlier versions that you could see the
disk usage being balanced across all disks.

These are the commands I've run:
# btrfs device add /dev/sdb2 /mnt/btrfs_raid1
# btrfs fi balance /mnt/btrfs_raid1

I see the unallocated space of sdc2 and sdd2 increasing, but for sdb2
(the new disk), it doesn't change. sdb2 doesn't even appear in the
btrfs usage command for data, metadata and system.

Is this normal? It's very strange the disk not showing up in the usage report.

# btrfs --version
btrfs-progs v4.1

# uname -a
Linux xenon 4.1.3-201.fc22.x86_64 #1 SMP Wed Jul 29 19:50:22 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux

# btrfs fi usage /mnt/btrfs_raid1
Overall:
Device size:   5.44TiB
Device allocated:  2.74TiB
Device unallocated:2.70TiB
Device missing:  0.00B
Used:  2.61TiB
Free (estimated):  1.42TiB  (min: 1.42TiB)
Data ratio:   2.00
Metadata ratio:   2.00
Global reserve:  512.00MiB  (used: 16.00KiB)

Data,RAID1: Size:1.36TiB, Used:1.30TiB
   /dev/sdc2   1.36TiB
   /dev/sdd2   1.36TiB

Metadata,RAID1: Size:10.00GiB, Used:8.11GiB
   /dev/sdc2  10.00GiB
   /dev/sdd2  10.00GiB

System,RAID1: Size:32.00MiB, Used:224.00KiB
   /dev/sdc2  32.00MiB
   /dev/sdd2  32.00MiB

Unallocated:
   /dev/sdb2   1.81TiB
   /dev/sdc2 454.48GiB
   /dev/sdd2 454.48GiB

# btrfs fi df /mnt/btrfs_raid1
Data, RAID1: total=1.36TiB, used=1.30TiB
System, RAID1: total=32.00MiB, used=224.00KiB
Metadata, RAID1: total=10.00GiB, used=8.13GiB
GlobalReserve, single: total=512.00MiB, used=18.83MiB

# btrfs fi show /mnt/btrfs_raid1
Label: 'btrfs_raid1'  uuid: 03eeb44b-de69-4f1f-9261-70bd7a5c6de0
Total devices 3 FS bytes used 1.30TiB
devid1 size 1.81TiB used 1.37TiB path /dev/sdc2
devid2 size 1.81TiB used 1.37TiB path /dev/sdd2
devid3 size 1.81TiB used 0.00B path /dev/sdb2

btrfs-progs v4.1

And the kernel log:
ago 11 11:54:45 xenon kernel: BTRFS info (device sdd2): disk added /dev/sdb2
ago 11 11:56:18 xenon kernel: BTRFS info (device sdd2): relocating
block group 1715902349312 flags 17
ago 11 11:56:36 xenon kernel: BTRFS info (device sdd2): found 12127 extents
ago 11 12:09:52 xenon kernel: BTRFS info (device sdd2): found 12127 extents
ago 11 12:09:56 xenon kernel: BTRFS info (device sdd2): relocating
block group 1714828607488 flags 17
ago 11 12:10:11 xenon kernel: BTRFS info (device sdd2): found 1076 extents
ago 11 12:11:24 xenon kernel: BTRFS info (device sdd2): found 1076 extents
ago 11 12:11:25 xenon kernel: BTRFS info (device sdd2): relocating
block group 1713754865664 flags 17
ago 11 12:11:37 xenon kernel: BTRFS info (device sdd2): found 8 extents
ago 11 12:11:50 xenon kernel: BTRFS info (device sdd2): found 8 extents
ago 11 12:11:50 xenon kernel: BTRFS info (device sdd2): relocating
block group 1712681123840 flags 17
ago 11 12:12:16 xenon kernel: BTRFS info (device sdd2): found 1432 extents
ago 11 12:13:17 xenon kernel: BTRFS info (device sdd2): found 1432 extents
[...]

-- 
Juan Orti
https://miceliux.com
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Usage of new added disk not updated while doing a balance

[Juan Orti Alcaine]

2015-08-11 15:20 GMT+02:00 Austin S Hemmelgarn ahferro...@gmail.com:
 How much slack space was allocated by BTRFS before running the balance (ie,
 how big a difference was there between the allocated and used space), and
 did the balance run to completion?  If you had a lot of mostly empty chunks
 and stopped the balance part way through, then this is what I would expect
 to happen (balance back-fills partial chunks before it starts allocating new
 ones).

 If that is not the case however, then this is very much _not_ normal, and is
 almost certainly a bug, in which case you should make sure any important
 data on the filesystem is backed up before doing anything further with it
 (including unmounting it or rebooting the system).


I don't have the usage numbers before running the balance, but I have
around 1000 readonly snapshots, so maybe that's a factor.

It keeps running and using both CPU and IO, so I'll wait to see what happens.

Thank you.

-- 
Juan Orti
https://miceliux.com
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Plans for a library for btrfs?

[Juan Orti Alcaine]

I'm not a developer, but I read this a days ago. Could it be helpful?

https://blog-vpodzime.rhcloud.com/?p=61
https://github.com/rhinstaller/libblockdev


2015-05-27 14:31 GMT+02:00 Stef Bon stef...@gmail.com:
 Hi,

 I'm working on a program (using sqlite, FUSE and btrfs) to provide
 backup and version managment
 for users. They can enable the backup service for folders they own,
 and select files they want to backup using mimetypes.

 This program, which I've called fuse-backup, creates backup subvolumes
 and snapshots by calling an extrenal script, which does something
 like:

 btrfs subvolume snapshot -r %PathToBackup%/ %PathToSnapshot%

 This works perfect, but are there any plans to do this with a library?

 Stef Bon
 --
 To unsubscribe from this list: send the line unsubscribe linux-btrfs in
 the body of a message to majord...@vger.kernel.org
 More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Juan Orti
https://miceliux.com

GPG key: https://miceliux.com/pub/pubkey.asc
GPG fingerprint: 61F0 8272 6882 BCA6 3A35  88F6 B630 4B72 DEEB D08B
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Cannot convert to raid1

[Juan Orti Alcaine]

El 2015-03-29 22:04, Holger Hoffstätte escribió:

On Sun, 29 Mar 2015 13:40:56 -0600, Chris Murphy wrote:


On Sun, Mar 29, 2015 at 1:15 PM, Juan Orti Alcaine
juan.o...@miceliux.com wrote:


The filesystem was created with one device, and I have added two more
devices afterwards. To convert it to raid1, I have used:

# btrfs balance start -dconvert=raid1 -mconvert=raid1 
/mnt/btrfs_raid1



The balance process has finished, but if I check my filesystem, it
shows up as single


Yeah, I'm kinda stumped. The only thing I'm thinking is if you're
absolutely sure it's mounted at /mnt/btrfs_raid1 – because I've made
this mistake before. (Oops.)


Nope, known bug in 4.0-rc:
http://thread.gmane.org/gmane.comp.file-systems.btrfs/43117



Do you know if the fix is going to do it for 4.0 final?
Thank you.

--
Juan Orti
https://miceliux.com

GPG key: https://miceliux.com/pub/pubkey.asc
GPG fingerprint: 61F0 8272 6882 BCA6 3A35  88F6 B630 4B72 DEEB D08B
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Cannot convert to raid1

[Juan Orti Alcaine]

Hello, I'm experiencing problems while balancing a filesystem to 
raid1. The versions I'm using are: 
kernel-4.0.0-0.rc5.git1.3.fc22.x86_64
btrfs-progs-3.19.1-1.fc22.x86_64

The filesystem was created with one device, and I have added two more 
devices afterwards. To convert it to raid1, I have used:

# btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/btrfs_raid1

The balance process has finished, but if I check my filesystem, it 
shows up as single

# btrfs fi show /mnt/btrfs_raid1
Label: 'btrfs_raid1'  uuid: cd7d4b6d-fa6b-4e2e-8b53-116d25ccdf4e
Total devices 3 FS bytes used 1.19TiB
devid1 size 1.81TiB used 410.06GiB path /dev/sdb2
devid2 size 1.81TiB used 410.00GiB path /dev/sdc2
devid3 size 1.81TiB used 410.00GiB path /dev/sdd2

btrfs-progs v3.19.1

# btrfs fi df /mnt/btrfs_raid1
Data, single: total=1.19TiB, used=1.19TiB
System, DUP: total=32.00MiB, used=176.00KiB
Metadata, DUP: total=5.00GiB, used=3.73GiB
GlobalReserve, single: total=512.00MiB, used=0.00B

# btrfs fi usage /mnt/btrfs_raid1
Overall:
Device size:   5.44TiB
Device allocated:  1.20TiB
Device unallocated:4.24TiB
Device missing:  0.00B
Used:  1.20TiB
Free (estimated):  4.24TiB  (min: 2.12TiB)
Data ratio:   1.00
Metadata ratio:   2.00
Global reserve:  512.00MiB  (used: 0.00B)

Data,single: Size:1.19TiB, Used:1.19TiB
   /dev/sdb2 406.00GiB
   /dev/sdc2 405.00GiB
   /dev/sdd2 409.00GiB

Metadata,DUP: Size:5.00GiB, Used:3.73GiB
   /dev/sdb2   4.00GiB
   /dev/sdc2   5.00GiB
   /dev/sdd2   1.00GiB

System,DUP: Size:32.00MiB, Used:176.00KiB
   /dev/sdb2  64.00MiB

Unallocated:
   /dev/sdb2   1.41TiB
   /dev/sdc2   1.41TiB
   /dev/sdd2   1.41TiB


-- 
Juan Orti
https://miceliux.com

GPG key: https://miceliux.com/pub/pubkey.asc
GPG fingerprint: 61F0 8272 6882 BCA6 3A35  88F6 B630 4B72 DEEB D08B

--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Random file system corruption in 3.17 (not BTRFS related...?)

[Juan Orti Alcaine]

El 2014-10-14 18:54, Robert White escribió:

Howdy,

So I run several gentoo systems and I upgraded two of them to kernel 
3.17.0


One using BTRFS for root.
One using ext3 for root (via the ext4 driver)

_Both_ systems exhibited strange behavior (long pauses and then hangs
requiring hard-power) within several hours. Both then had random
filesystem damage.

On the BTRFS system much of my browser settings for firefox were
trashed, particularly the cookies and saved conifigurations for
add-ons (like which sites had scripts enabled/disabled in no-script)
etc.

On the ext3/4 system there were several corruptions including a
pipe/special file with a large non-zero size that required I do a
fsck -fyD /dev/sda3 to repair. (one comment from fsck was that the
pipe/special file looked like a directory or some such)

So I can say that corruption is taking place, but I suspect it is
_not_ happening in the BTRFS specific code.

(ASIDE: both systems are older amd64 using built-in radeon display 
hardware.)




I've also experienced Btrfs corruptions with 3.17.0 (Fedora 21 alpha). 
It has happened two times, each one after a clean reinstall and a wipe 
of the old fs. In less than a day, both installations got corrupted and 
the filesystems went readonly. When listing the contents, I saw many 
directories with question marks.


My system has 4 drives and 2 fs:
- 1 SSD in single
- 3 HDD in RAID1

I do readonly snapshots every hour of all the subvolumes, so I have 
hundreds of snapshots.


Now I'm back in 3.16.4 without any problems. I'm trying to reproduce my 
setup in a virtual machine. If the corruption happens again, I'll send 
you more data on this problem.


--
Juan Orti
https://miceliux.com

--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Random file system corruption in 3.17 (not BTRFS related...?)

[Juan Orti Alcaine]

El 2014-10-15 15:46, Josef Bacik escribió:

On 10/15/2014 03:08 AM, Juan Orti Alcaine wrote:

I've also experienced Btrfs corruptions with 3.17.0 (Fedora 21 alpha).
It has happened two times, each one after a clean reinstall and a wipe
of the old fs. In less than a day, both installations got corrupted 
and

the filesystems went readonly. When listing the contents, I saw many
directories with question marks.

My system has 4 drives and 2 fs:
- 1 SSD in single
- 3 HDD in RAID1


Did it happen on both fs'es or just one?  Thanks,

Josef


Both filesystems were corrupted. I have / in the SSD and /home in the 
HDDs.


I didn't notice anything while working with the system, I only 
discovered the problem when booting up after the second or third reboot 
and seeing the service failing to start. Could it be something related 
to the mount/umount logic?


--
Juan Orti
https://miceliux.com

--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Random file system corruption in 3.17 (not BTRFS related...?)

[Juan Orti Alcaine]

El 2014-10-15 16:30, Josef Bacik escribió:

On 10/15/2014 10:05 AM, Juan Orti Alcaine wrote:

El 2014-10-15 15:46, Josef Bacik escribió:

On 10/15/2014 03:08 AM, Juan Orti Alcaine wrote:
I've also experienced Btrfs corruptions with 3.17.0 (Fedora 21 
alpha).
It has happened two times, each one after a clean reinstall and a 
wipe
of the old fs. In less than a day, both installations got corrupted 
and

the filesystems went readonly. When listing the contents, I saw many
directories with question marks.

My system has 4 drives and 2 fs:
- 1 SSD in single
- 3 HDD in RAID1


Did it happen on both fs'es or just one?  Thanks,

Josef


Both filesystems were corrupted. I have / in the SSD and /home in the 
HDDs.


I didn't notice anything while working with the system, I only
discovered the problem when booting up after the second or third 
reboot

and seeing the service failing to start. Could it be something related
to the mount/umount logic?



We've found it, the Fedora guys are reverting the bad patch now, we'll
get the fix sent back to stable shortly.  Sorry about that.


Thanks to you. Fortunately I have good backups.

--
Juan Orti
https://miceliux.com

--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Identify mounted subvolume

[Juan Orti Alcaine]

I cannot find the answer to this one. How can I determine which 
subvolume I have mounted in a certain path? I'm looking through /sys but 
no clue.


Thank you.

--
Juan Orti
https://miceliux.com

--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

File capabilities are lost when sending/receiving a btrfs subvolume

[Juan Orti Alcaine]

Hello, I noticed that file capabilites are lost on received subvolumes, so I 
opened the bug report #68891 [1]. I don't know if other xattrs are affected by 
this problem.

I just like to know if fixing this issue is under the radar of the developers.

Thank you.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=68891

-- 
Juan Orti
GPG Key: DEEBD08B - http://jorti.fedorapeople.org/pubkey.asc
Blog: https://apuntesderoot.wordpress.com/

signature.asc
Description: This is a digitally signed message part.

Another crash when deleting a large number of snapshots

[Juan Orti Alcaine]

This kind of crashes happens me very often when I delete a large
number (+200) of snapshots at once.
There is a very high IO for a while, and after that, the system
freezed at intervals. I had to reboot the system to get it responsive
again.

Versions used:
kernel-3.13.6-200.fc20.x86_64
btrfs-progs-3.12-1.fc20.x86_64

The log:
http://ur1.ca/gvr3j
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Error when deleting snapshots

[Juan Orti Alcaine]

I got this error when deleting around a hundred snapshots with kernel
3.13.0 and btrfs-progs 3.12:

[  831.628833] [sched_delayed] sched: RT throttling activated
[  858.586718] BUG: soft lockup - CPU#1 stuck for 22s! [btrfs-transacti:643]
[  858.586721] Modules linked in: ipt_MASQUERADE xt_CHECKSUM tun
ip6t_rpfilter ip6t_REJECT xt_conntrack bnep bluetooth cfg80211
ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
ip6table_mangle ip6table_security ip6table_raw ip6table_filter
ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw
iTCO_wdt eeepc_wmi iTCO_vendor_support asus_wmi sparse_keymap rfkill
snd_hda_codec_hdmi vfat fat x86_pkg_temp_thermal coretemp kvm_intel
kvm crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek crc32c_intel
ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_memops
videobuf2_core microcode videodev snd_usb_audio snd_hda_intel media
snd_usbmidi_lib serio_raw
[  858.586742]  snd_hda_codec snd_rawmidi i2c_i801 snd_hwdep snd_seq
mceusb snd_seq_device rc_core r8169 snd_pcm mii lpc_ich mfd_core
snd_page_alloc snd_timer snd mei_me mei soundcore shpchp wmi
binfmt_misc usb_storage btrfs libcrc32c xor raid6_pq radeon
i2c_algo_bit drm_kms_helper ttm drm i2c_core video
[  858.586754] CPU: 1 PID: 643 Comm: btrfs-transacti Not tainted
3.13.0-1.fc20.x86_64 #1
[  858.586755] Hardware name: System manufacturer System Product
Name/P8Z68-V LE, BIOS 4101 05/09/2013
[  858.586756] task: 8803ff9133c0 ti: 880002898000 task.ti:
880002898000
[  858.586757] RIP: 0010:[a029eea1]  [a029eea1]
comp_entry+0x11/0x1b0 [btrfs]
[  858.586767] RSP: 0018:880002899c00  EFLAGS: 0246
[  858.586768] RAX: 035f45c0 RBX: 880002899b98 RCX: 00b8
[  858.586769] RDX:  RSI: 8802e5a4fae0 RDI: 88037a7a8360
[  858.586769] RBP: 880002899c18 R08:  R09: 
[  858.586770] R10: a029fa3f R11: ea000bc7fac0 R12: 880403d5b100
[  858.586771] R13: 0001002a0001 R14:  R15: 002a02899b80
[  858.586772] FS:  () GS:88041ec4()
knlGS:
[  858.586772] CS:  0010 DS:  ES:  CR0: 80050033
[  858.586773] CR2: 02beb018 CR3: 0dc0c000 CR4: 000407e0
[  858.586774] Stack:
[  858.586774]  88037a7a8360 3009 8802e5a4d300
880002899c70
[  858.586776]  a029f8b5 8802f31dd660 880404ab4be0
88037a7a8360
[  858.586777]  0001 88031c7e3cc0 8802f31dd660

[  858.586779] Call Trace:
[  858.586787]  [a029f8b5] btrfs_merge_delayed_refs+0xe5/0x3d0 [btrfs]
[  858.586793]  [a0246e74] run_clustered_refs+0x84/0x1080 [btrfs]
[  858.586798]  [a02472af] ? run_clustered_refs+0x4bf/0x1080 [btrfs]
[  858.586803]  [a02472af] ? run_clustered_refs+0x4bf/0x1080 [btrfs]
[  858.586809]  [a024bb70] btrfs_run_delayed_refs+0xe0/0x530 [btrfs]
[  858.586815]  [a025bb0e] btrfs_commit_transaction+0x4e/0x940 [btrfs]
[  858.586821]  [a0257c25] transaction_kthread+0x1c5/0x250 [btrfs]
[  858.586827]  [a0257a60] ?
btrfs_cleanup_transaction+0x520/0x520 [btrfs]
[  858.586830]  [8108f3b2] kthread+0xd2/0xf0
[  858.586831]  [8108f2e0] ? insert_kthread_work+0x40/0x40
[  858.586833]  [8169503c] ret_from_fork+0x7c/0xb0
[  858.586835]  [8108f2e0] ? insert_kthread_work+0x40/0x40
[  858.586835] Code: b4 eb 2c a0 48 89 55 e8 e8 2d e8 dc e0 48 8b 55
e8 e9 1e ff ff ff 0f 1f 40 00 66 66 66 66 90 55 48 89 e5 41 55 41 54
49 89 fc 53 48 8b 47 18 48 89 f3 48 39 46 18 0f 82 be 00 00 00 0f 87
90 00
[  858.622675] BUG: soft lockup - CPU#4 stuck for 22s! [btrfs-cleaner:642]
[  858.622677] Modules linked in: ipt_MASQUERADE xt_CHECKSUM tun
ip6t_rpfilter ip6t_REJECT xt_conntrack bnep bluetooth cfg80211
ebtable_nat ebtable_broute bridge stp llc ebtable_filter ebtables
ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6
ip6table_mangle ip6table_security ip6table_raw ip6table_filter
ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4
nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw
iTCO_wdt eeepc_wmi iTCO_vendor_support asus_wmi sparse_keymap rfkill
snd_hda_codec_hdmi vfat fat x86_pkg_temp_thermal coretemp kvm_intel
kvm crct10dif_pclmul crc32_pclmul snd_hda_codec_realtek crc32c_intel
ghash_clmulni_intel uvcvideo videobuf2_vmalloc videobuf2_memops
videobuf2_core microcode videodev snd_usb_audio snd_hda_intel media
snd_usbmidi_lib serio_raw
[  858.622698]  snd_hda_codec snd_rawmidi i2c_i801 snd_hwdep snd_seq
mceusb snd_seq_device rc_core r8169 snd_pcm mii lpc_ich mfd_core
snd_page_alloc snd_timer snd mei_me mei soundcore shpchp wmi
binfmt_misc usb_storage btrfs libcrc32c xor raid6_pq radeon
i2c_algo_bit drm_kms_helper ttm drm i2c_core 

Cannot delete subvolume - Directory not empty

[Juan Orti Alcaine]

I'm trying to delete a emtpy subvolume, but I can't. It is a Luks
device and I'm using autofs, I have unmounted it, closed the Luks
device and remounted again, but it doesn't work.

# mount | grep hd04
systemd-1 on /mnt/hd04 type autofs
(rw,relatime,fd=46,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
systemd-1 on /mnt/hd04_duply type autofs
(rw,relatime,fd=47,pgrp=1,timeout=300,minproto=5,maxproto=5,direct)
/dev/mapper/luks-964185b6-7203-439f-a7c9-cbb374131af4 on /mnt/hd04
type btrfs (rw,relatime,seclabel,compress=lzo,space_cache)
/dev/mapper/luks-964185b6-7203-439f-a7c9-cbb374131af4 on
/mnt/hd04_duply type btrfs
(rw,relatime,seclabel,compress=lzo,space_cache)

# btrfs sub list .
ID 256 gen 2854 top level 5 path backups
ID 1063 gen 2876 top level 5 path duply
ID 1066 gen 1765 top level 5 path duply@2014-01-11_20:40:18
ID 1756 gen 2840 top level 5 path duply@2014-01-16_21:23:49

# ls -la backups/
total 4
drwxr-xr-x. 1 root root   0 ene 16 21:43 .
drwxr-xr-x. 1 root root 124 ene 16 21:26 ..

# btrfs sub delete backups
Delete subvolume '/mnt/hd04/backups'
ERROR: cannot delete '/mnt/hd04/backups' - Directory not empty

# btrfs fi show
Label: hd04_backups_externos  uuid: e163fa83-4a98-4c04-b69f-fb8518e7230a
Total devices 1 FS bytes used 695.94GiB
devid1 size 1.82TiB used 1.46TiB path
/dev/mapper/luks-964185b6-7203-439f-a7c9-cbb374131af4

Btrfs v3.12

Kernel 3.12.7-300.fc20.x86_64

-- 
Juan Orti
GPG Key: DEEBD08B - http://jorti.fedorapeople.org/pubkey.asc
Blog: https://apuntesderoot.wordpress.com/
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html