Btrfs Partition out of free space - no mount possible

Hello! My Btrfs partition (/home) is out of free space. The partition is a logical drive within a LVM configuration. I've already extended the LVM logical volume. However, it's impossible to mount the partition from a live CD system (SystemRescue CD). The error in dmesg is: BTRFS: inode 8443 st

[PATCH] Btrfs: fix subvolume mount by name problem when default mount subvolume is set

We create two subvolumes (meego_root and meego_home) in btrfs root directory. And set meego_root as default mount subvolume. After we remount btrfs, meego_root is mounted to top directory by default. Then when we try to mount meego_home (subvol=meego_home) to a subdirectory, it failed. The problem

[PATCH] Btrfs: fix compile warning from __btrfs_map_block

While compile btrfs modules on 32bit box, I encounter the following: WARNING: "__umoddi3" [fs/btrfs/btrfs.ko] undefined! The WARNING comes from that __btrfs_map_block does not use do_div() for relative operations, this will cause problems on 32bit box, for values with "u64" type should use do_di

[PATCH] btrfs: clear __GFP_FS flag in the space cache inode

From: Miao Xie the object id of the space cache inode's key is allocated from the relative root, just like the regular file. So we can't identify space cache inode by checking the object id of the inode's key, and we have to clear __GFP_FS flag at the time we look up the space cache inode. Signe

Re: [PATCH 0/2] btrfs: allow cross-subvolume BTRFS_IOC_CLONE

Arne Jansen wrote: On Thu, Mar 31, 2011 at 12:00:11AM -0400, Larry D'Anna wrote: This is a simple patch to allow reflinks to be made crossing subvolume boundaries. NAK. subvolumes will have to become vfsmounts sooner or later, and we really must not support any operations spanning mountpoint

Re: [PATCH 0/2] btrfs: allow cross-subvolume BTRFS_IOC_CLONE

Excerpts from Christoph Hellwig's message of 2011-03-31 02:36:36 -0400: > On Thu, Mar 31, 2011 at 12:00:11AM -0400, Larry D'Anna wrote: > > This is a simple patch to allow reflinks to be made crossing subvolume > > boundaries. > > NAK. subvolumes will have to become vfsmounts sooner or later, and

Re: [PATCH] Btrfs: fix compile warning from __btrfs_map_block

Excerpts from liubo's message of 2011-03-31 05:45:20 -0400: > > While compile btrfs modules on 32bit box, I encounter the following: > > WARNING: "__umoddi3" [fs/btrfs/btrfs.ko] undefined! > > The WARNING comes from that __btrfs_map_block does not use do_div() for > relative operations, this wil

[PATCH] Btrfs: fix subvol_sem leak in btrfs_rename()

btrfs_rename() does not release the subvol_sem if the transaction failed to start. Signed-off-by: Johann Lombardi --- fs/btrfs/inode.c |8 +--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 93c28a1..495b055 100644 --- a/fs/btrfs

checkpoints to often

There should be a way to make automatic checkpoints less frequent. On the busy ssd I have about 7 cp every second. If it were for example once every 5 minutes then one could set garbage removal every few days. Also garbage removal should have option to clean only if like 90% of drive is used. there

Re: checkpoints to often

Excerpts from krz...@gmail.com's message of 2011-03-31 10:30:51 -0400: > There should be a way to make automatic checkpoints less frequent. On > the busy ssd I have about 7 cp every second. If it were for example > once every 5 minutes then one could set garbage removal every few > days. > Also gar

Re: [PATCH] Btrfs - use %pU to print fsid

On Wed, Feb 9, 2011 at 8:05 AM, Ilya Dryomov wrote: > Get rid of FIXME comment.  Uuids from dmesg are now the same as uuids > given by btrfs-progs. > > Signed-off-by: Ilya Dryomov > --- >  fs/btrfs/volumes.c |    8 ++-- >  1 files changed, 2 insertions(+), 6 deletions(-) > > diff --git a/fs/b

[PATCH] Btrfs: fix free space cache when there are pinned extents and clusters

I noticed a huge problem with the free space cache that was presenting as an early ENOSPC. Turns out when writing the free space cache out I forgot to take into account pinned extents and more importantly clusters. This would result in us leaking free space everytime we unmounted the filesystem a

Re: Do not use free space caching!

On Wed, 2011-03-30 at 17:19 -0400, Josef Bacik wrote: > Hello, > > Just found a big bug in the free space caching stuff that will result in > early ENOSPC. I'm working on fixing this bug, but it won't be until > tomorrow that I'll have it completely working, so for now make sure to > mount -o

Re: [PATCH 1/3] VFS/ioctl: Add punching-hole support to ioctl().

Frankly I see no point extending the ioctl interface when we have a syscall interface. On 03/31/2011 12:33 AM, Tristan Ye wrote: We're currently support two paths from VFS to preallocate unwritten extents(from FS_IOC_RESVSP, or fallocate()), likewise, behavior of punching-hole should be treated

Re: [PATCH] Btrfs - use %pU to print fsid

On Thu, Mar 31, 2011 at 12:14:14PM -0500, Mitch Harder wrote: > On Wed, Feb 9, 2011 at 8:05 AM, Ilya Dryomov wrote: > > Get rid of FIXME comment.  Uuids from dmesg are now the same as uuids > > given by btrfs-progs. > > > > Signed-off-by: Ilya Dryomov > > --- > >  fs/btrfs/volumes.c |    8 ++

Re: [PATCH 1/3] VFS/ioctl: Add punching-hole support to ioctl().

On Thu, Mar 31, 2011 at 02:14:43PM -0700, Sunil Mushran wrote: > Frankly I see no point extending the ioctl interface when we have > a syscall interface. > I'd even go so far as to say we could probably axe the xfs and ocfs2 ioctls since we have the fallocate interface :). Thanks, Josef -- To un

Re: Do not use free space caching!

On Thu, Mar 31, 2011 at 05:06:42PM -0400, Calvin Walton wrote: > On Wed, 2011-03-30 at 17:19 -0400, Josef Bacik wrote: > > Hello, > > > > Just found a big bug in the free space caching stuff that will result in > > early ENOSPC. I'm working on fixing this bug, but it won't be until > > tomorrow

Re: [PATCH 1/3] VFS/ioctl: Add punching-hole support to ioctl().

On Thu, Mar 31, 2011 at 06:56:18PM -0400, Josef Bacik wrote: > On Thu, Mar 31, 2011 at 02:14:43PM -0700, Sunil Mushran wrote: > > Frankly I see no point extending the ioctl interface when we have > > a syscall interface. > > > > I'd even go so far as to say we could probably axe the xfs and ocfs2

Re: [PATCH 1/3] VFS/ioctl: Add punching-hole support to ioctl().

On Thu, Mar 31, 2011 at 04:44:55PM -0700, Joel Becker wrote: > On Thu, Mar 31, 2011 at 06:56:18PM -0400, Josef Bacik wrote: > > On Thu, Mar 31, 2011 at 02:14:43PM -0700, Sunil Mushran wrote: > > > Frankly I see no point extending the ioctl interface when we have > > > a syscall interface. > > > > >

Re: [PATCH] Btrfs: fix compile warning from __btrfs_map_block

On 03/31/2011 08:10 PM, Chris Mason wrote: > Excerpts from liubo's message of 2011-03-31 05:45:20 -0400: >> While compile btrfs modules on 32bit box, I encounter the following: >> >> WARNING: "__umoddi3" [fs/btrfs/btrfs.ko] undefined! >> >> The WARNING comes from that __btrfs_map_block does not use

Re: [PATCH 1/2] Btrfs: fix OOPS of empty filesystem after balance

On 03/30/2011 07:58 PM, Arne Jansen wrote: > Am 10.03.2011 13:28, schrieb Chris Mason: >> Excerpts from liubo's message of 2011-03-10 03:50:27 -0500: >>> On 03/07/2011 10:13 AM, liubo wrote: btrfs will remove unused block groups after balance. When a empty filesystem is balanced, the bloc

[RFC PATCH] Trace: use unsigned long long in trace print frames

While adding tracepoint for btrfs, I got a problem: btrfs uses some macros with "ULL" type, but tracepoint's macros, __print_[flags,symbols](), only have "unsigned long", so on 32bit box there will be 64->32 truncate WARNINGs when compiling. Here I'm inclined to make the replacement to clear tho