On Sun, 2010-10-17 at 17:53 +0200, Goffredo Baroncelli wrote:
On Tuesday, 12 October, 2010, Ian Kent wrote:
On Mon, 2010-10-11 at 20:08 +0200, Goffredo Baroncelli wrote:
[...]
+ ret = btrfs_unlink_subvol(trans, root, dir,
+ dest-root_key.objectid,
+
On Sun, 2010-10-17 at 18:09 +0200, Goffredo Baroncelli wrote:
Hi all,
enclosed you can find a new version of the patch which permits to remove a
volume via the rmdir(2) syscall by a non-root user. The goal of this patch
is to permits to remove a subvolume with a simple rm -rf command.
On 17/10/10 19:26, hugo-l...@carfax.org.uk wrote:
Change btrfs filesystem df to allow the user to control the scales
used for sizes in the output.
Index: btrfs-progs-unstable/btrfs.c
===
--- btrfs-progs-unstable.orig/btrfs.c
On Mon, 18 Oct 2010 10:41:41 +0800, Shaohua Li wrote:
Hi Miao Chris,
On Wed, Oct 13, 2010 at 05:00:56PM +0800, Miao Xie wrote:
When I investigated the performance problem of file creation/deletion, I found
btrfs spends lots of time in the b-tree search, so I consider whether we can use
the
Hi Hugo,
please, remember to update the manpage also.
Regards
G.Baroncelli
Messaggio originale
Da: hugo-l...@carfax.org.uk
Data: 17/10/2010 20.26
A: linux-btrfs@vger.kernel.org
Ogg: [patch 0/4] Size reporting of btrfs tool
While playing around with resizing volumes recently, I realised
reading, in dir-item.c, the code in
struct btrfs_dir_item *btrfs_match_dir_item_name (...)
I am a little surprised to see an O(n) iterative name comparison check
instead of something that would
efficiently support directories with lots of items in them. Is this
function a fall-back if a O(1) table
That's the other thing the cleaner_kthread does; conceivably some new
delayed iputs could get queued during snapshot deletions.
Thoughts?
--
In one instance, a rai being transported by canoe was accidentally
dropped and sunk to the sea floor. Although it was never seen again,
everyone agreed
Hi all
like my previous patch, this one allow to remove a subvolume by an ordinary
user. Instead of adding this capability to the rmdir(2) syscall, I update the
BTRFS_IOC_SNAP_DESTROY ioctl, relaxing the rules to be execute.
The checks are the ones performed by the rmdir(2) syscall. So a
On Fri, Oct 15, 2010 at 05:28:34PM -0400, Josef Bacik wrote:
Because the ENOSPC code over reserves super aggressively we end up allocating
chunks way more often than we should. For example with my fs_mark tests on a
2gb fs I can end up reserved 1gb just for metadata, when only 34mb of that is
On Mon, Oct 18, 2010 at 09:21:56AM +0100, Frank Kingswood wrote:
On 17/10/10 19:26, hugo-l...@carfax.org.uk wrote:
Change btrfs filesystem df to allow the user to control the scales
used for sizes in the output.
Index: btrfs-progs-unstable/btrfs.c
Because the ENOSPC code over reserves super aggressively we end up allocating
chunks way more often than we should. For example with my fs_mark tests on a
2gb fs I can end up reserved 1gb just for metadata, when only 34mb of that is
being used. So instead check to see if the amount of space
11 matches
Mail list logo