similar to: [PATCH] Btrfs: fix incorrect inode acl reset

When adding orphans to an inode''s root, we start a transaction for that root that when ended in several places such as for example extent-tree.c:btrfs_remove_block_group(), inode.c:btrfs_unlink() and inode.c:btrfs_evict_node(), doesn''t result in a commit, that is, inode.c:btrfs_orphan_commit_root() doesn''t get called (via transaction.c:commit_fs_roots()). The respective

When the binary search returns 0 (exact match), the target key will necessarily be at slot 0 of all nodes below the current one, so in this case the binary search is not needed because it will always return 0, and we waste time doing it, holding node locks for longer than necessary, etc. Below follow histograms with the times spent on the current approach of doing a binary search when the

The inode eviction can be very slow, because during eviction we tell the VFS to truncate all of the inode''s pages. This results in calls to btrfs_invalidatepage() which in turn does calls to lock_extent_bits() and clear_extent_bit(). These calls result in too many merges and splits of extent_state structures, which consume a lot of time and cpu when the inode has many pages. In some

Currently the fs sync function (super.c:btrfs_sync_fs()) doesn''t wait for delayed work to finish before returning success to the caller. This change fixes this, ensuring that there''s no data loss if a power failure happens right after fs sync returns success to the caller and before the next commit happens. Steps to reproduce the data loss issue: $ mkfs.btrfs -f /dev/sdb3 $

If there''s an ongoing transaction when the uuid scan kthread attempts to create one, the kthread will block, waiting for that transaction to finish while it''s keeping locks on the tree root, and in turn the existing transaction is waiting for those locks to be free. The stack trace reported by the kernel follows. [36700.671601] INFO: task btrfs-uuid:15480 blocked for more than

On btrfs, do the following ------------------ # su user1 # cd btrfs-part/ # touch aaa # getfacl aaa # file: aaa # owner: user1 # group: user1 user::rw- group::rw- other::r-- # su user2 # cd btrfs-part/ # setfacl -m u::rwx aaa # getfacl aaa # file: aaa # owner: user1 # group: user1 user::rwx <- successed to setfacl group::rw- other::r-- ------------------ but we

If we get any error while doing a dir index/item lookup in the log tree, we were always unlinking the corresponding inode in the subvolume. It makes sense to unlink only if the lookup failed to find the dir index/item, which corresponds to NULL or -ENOENT, and not when other errors happen (like a transient -ENOMEM or -EIO). Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> ---

In tree-log.c:replay_one_name(), if memory allocation for the name fails, ensure we iput the dir inode we got before before we return. Signed-off-by: Filipe David Borba Manana <fdmanana@gmail.com> --- fs/btrfs/tree-log.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/tree-log.c b/fs/btrfs/tree-log.c index ff60d89..6797a93 100644 ---

El vie, 10-04-2015 a las 10:21 +0900, Timo Sirainen escribi?: > On 09 Apr 2015, at 06:52, Guillermo M. Narvaja <guillermo.narvaja at fierro.com.ar> wrote: > > > > Since December 2014, clients using the Python poplib library (getmail in > > my case) started to limit the line length of RETR and other command > > responses sent from the server to 2048 bytes: >

Hola, Ya estamos preparando la siguiente reunión del "Grupo de Usuarios de R de Madrid". Tenemos acordada ya parte de la agenda (os adjunto detalles), si alguien quiere unirse y presentar algo (corto, largo o medio-pensionista) no dude en ponerse en contacto conmigo para incluirle sin problemas. Jueves 20 Junio de 2013 - *Lugar:* Facultad de Ciencias - UNED. C/ Senda del Rey,

I noticed we were getting lots of warnings with xfstest 83 because we have reservations outstanding. This is because we moved the orphan add outside of the truncate, but we don''t actually cleanup our reservation if something fails. This fixes the problem and I no longer see warnings. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- fs/btrfs/inode.c | 2 ++ 1

Since December 2014, clients using the Python poplib library (getmail in my case) started to limit the line length of RETR and other command responses sent from the server to 2048 bytes: See https://bugs.python.org/issue16041 (Included at least in Python-2.7.9) Dovecot doesn't have line split in the POP3 module, so Python fails to retrieve messages with long lines. RFC 1939 says: "

On 10 Apr 2015, at 17:51, Guillermo M. Narvaja <guillermo.narvaja at fierro.com.ar> wrote: > > El vie, 10-04-2015 a las 10:21 +0900, Timo Sirainen escribi?: >> On 09 Apr 2015, at 06:52, Guillermo M. Narvaja <guillermo.narvaja at fierro.com.ar> wrote: >>> >>> Since December 2014, clients using the Python poplib library (getmail in >>> my case)

Buenas a todo, Una breve nota para comentaros que este jueves (4-Abril) mantendremos la siguiente reunión del "Grupo de Usuarios de R de Madrid". La agenda prevista es la siguiente: (Prevista) Jueves 4 de Abril de 2013 - *Lugar:* Facultad de Ciencias - UNED. C/ Senda del Rey, 9.<http://portal.uned.es/portal/page?_pageid=93,688166&_dad=portal&_schema=PORTAL> -

What happened to the hot data tracking feature in btrfs? There are a lot of old patches from aug 2010, but it looks like the feature has been completly removed from the current version of btrfs. Is this feature still on the roadmap?

Hey, guys. I have a problem when installing syslinux 4.06, and I'd be grateful if someone could tell me how to solve the problem. My task - to install the bootloader on the virtual machine image. The image contains the MBR and the only partition with the file system ext4. The file system contains all the files for the guest OS. To install bootloader into the image of the guest OS, I use the

Thanks for Remko for his help to solve the fractional cylinder problem. But there is the second problem, the boot disk failure (see below << [B]) ... command line: initrd=disk.img harddisk c=2 h=256 s=63 BOOT_IMAGE=memdisk Disk is hard disk, 16128K CHS=2/256/63 <<<< [A] ... Loading boot sector... booting... SYSLINUX 2.04 welcome! boot: 1 [single dot]

Some people contribute to someone specific fs testing mostly, record some of them as Reviewer. Signed-off-by: Zorro Lang <zlang at kernel.org> --- If someone doesn't want to be in cc list of related fstests patch, please reply this email, I'll remove that reviewer line. Or if someone else (who contribute to fstests very much) would like to a specific reviewer, nominate yourself to

Following is one grub entry menuentry "Ubuntu, Linux 2.6.32.27" { insmod ntfs set root=''(hd0,2)'' search --no-floppy --fs-uuid --set 96f65c80f65c6313 loopback loop0 /ubuntu/disks/root.disk set root=(loop0) linux /boot/vmlinuz-2.6.32.27 root=/dev/sda2 loop=/ubuntu/disks/root.disk ro quiet splash initrd

Hi, I'm running rsync-3.0.4 on my UNIX system. I've just updated from rsync-2.6.9. I'm facing a general problem with the execution of files during a transfer process. The situation: 2 Directories (dir1 and dir2) on one machine with a some files in dir1 which shall be translated to dir2. rsync does not correctly recognize dir1 and dir2 as directories. It tries to transfer dir1 as a