The patchset enhanced btrfs qgroup show command.
Firstly, we restructure show_qgroups, make it easy to add new features.
And then we add '-p' '-c', '-l',and '-e' options to print the parent
qgroup id, child qgroup id, max referenced size and max exclusive size
of qgroup respectively, add '-F' and
From: Wang Shilong wangsl-f...@cn.fujitsu.com
This patch introduces '-p' option to print the ID of the parent qgroups.
You may use it like:
btrfs qgroup show -p path
For Example:
qgroupid(2/0)
/ \
/ \
/
From: Wang Shilong wangsl-f...@cn.fujitsu.com
This patch introduce '-e' option to print max exclusive size of qgroups.
You may use it like this:
btrfs qgroup -e path
Signed-off-by: Wang Shilong wangsl-f...@cn.fujitsu.com
Signed-off-by: Miao Xie mi...@cn.fujitsu.com
---
From: Wang Shilong wangsl-f...@cn.fujitsu.com
This patch introduces '-f' option which can help you filter the qgroups
by the path name, you may use it like:
btrfs qgroup show -f path
For example:
qgroupid(2/0)
/ \
From: Wang Shilong wangsl-f...@cn.fujitsu.com
The current show_qgroups() just shows a little information, and it is hard to
add some functions which the users need in the future, so i restructure it, make
it easy to add new functions.
In order to improve the scalability of show_qgroups(), i add
From: Wang Shilong wangsl-f...@cn.fujitsu.com
You might want to list qgroups in order of some items, such as 'qgroupid',
'rfer'
and so on, you can use '--sort'. Now you can sort the qgroups by 'qgroupid',
'rfer','excl','max_rfer' and 'max_excl'.
For example:
If you want to list qgroups
From: Wang Shilong wangsl-f...@cn.fujitsu.com
This patch introduces '-F' option which can help you filter the qgroups
by the path name, you may use it like:
btrfs qgroup show -F path
For example:
qgroupid(2/0)
/ \
From: Wang Shilong wangsl-f...@cn.fujitsu.com
This patch introduces '-l' option to print max referenced size of qgroups.
You may use it like:
btrfs qgroup show -l path
Signed-off-by: Wang Shilong wangsl-f...@cn.fujitsu.com
Signed-off-by: Miao Xie mi...@cn.fujitsu.com
---
From: Wang Shilong wangsl-f...@cn.fujitsu.com
This patch introduces '-c' option to print the ID of the child qgroups.
You may use it like:
btrfs qgroup show -c path
For Example:
qgroupid(2/0)
/ \
/ \
/
From: Wang Shilong wangsl-f...@cn.fujitsu.com
This patch introduce '-t' option which can help you print the result
as a table.
You can use it like:
btrfs qgroup show -t path
However, to table the result better, we make '-p' and '-c' not present
at the same time.If you still want to show
On 09/18/2013 09:51 AM, Eric Sandeen wrote:
On 9/17/13 8:11 PM, rongqing...@windriver.com wrote:
From: Roy Li rongqing...@windriver.com
The dependencies of all: version.h or other similar ones can not
fix the parallel build failure, only reduce the times; In fact,
many *.o files require
Thân Email dùng,
Hộp thư của bạn đã vượt quá giới hạn lưu trữ mà là 20.00 GB như thiết lập bởi
quản trị viên của bạn, bạn đang chạy trên 19,99 GB, bạn có thể không có thể gửi
hoặc nhận thư mới cho đến khi bạn xác nhận hộp thư điện tử của bạn. Vui lòng
nhấp vào liên kết dưới đây để xác nhận
Thân Email dùng,
Hộp thư của bạn đã vượt quá giới hạn lưu trữ mà là 20.00 GB như thiết lập bởi
quản trị viên của bạn, bạn đang chạy trên 19,99 GB, bạn có thể không có thể gửi
hoặc nhận thư mới cho đến khi bạn xác nhận hộp thư điện tử của bạn. Vui lòng
nhấp vào liên kết dưới đây để xác nhận
The command is
btrfs subvolume set-default subvolid path.
It uses @subvolid to control the default subvolume and
@subvolid=0 has always been parsed into FS_TREE no matter
what subvolume @path points to.
So in order to set a subvolume to the default one, we need
to get the id of this subvolume
On Mon, Sep 23, 2013 at 2:30 AM, Miao Xie mi...@cn.fujitsu.com wrote:
On sun, 22 Sep 2013 21:55:53 +0100, Filipe David Borba Manana wrote:
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
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
Wang Shilong posted on Mon, 23 Sep 2013 10:18:19 +0800 as excerpted:
On 09/23/2013 09:53 AM, Dusty Mabe wrote:
There is one other thing I have noticed while playing around
with quota and qgroups. If I delete subvolumes I can manage to get some
of the qgroup information to be reported as a
On Mon, Sep 23, 2013 at 10:11:42AM +0100, Filipe David Manana wrote:
On Mon, Sep 23, 2013 at 2:30 AM, Miao Xie mi...@cn.fujitsu.com wrote:
On sun, 22 Sep 2013 21:55:53 +0100, Filipe David Borba Manana wrote:
Currently the fs sync function (super.c:btrfs_sync_fs()) doesn't
wait for
On Mon, Sep 23, 2013 at 10:23 AM, Filipe David Borba Manana
fdman...@gmail.com wrote:
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
On Mon, Sep 23, 2013 at 10:53:20AM +0100, Filipe David Manana wrote:
On Mon, Sep 23, 2013 at 10:23 AM, Filipe David Borba Manana
fdman...@gmail.com wrote:
Currently the fs sync function (super.c:btrfs_sync_fs()) doesn't
wait for delayed work to finish before returning success to the
On Mon, Sep 23, 2013 at 10:59 AM, Liu Bo bo.li@oracle.com wrote:
On Mon, Sep 23, 2013 at 10:53:20AM +0100, Filipe David Manana wrote:
On Mon, Sep 23, 2013 at 10:23 AM, Filipe David Borba Manana
fdman...@gmail.com wrote:
Currently the fs sync function (super.c:btrfs_sync_fs()) doesn't
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
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
Hello,
My system is configured to do FS snapshots when I upgrade packages. I
have a cron job which runs at night to delete these snapshots. Its goal
is to keep 10 snapshots maximum, one per day if possible.
This works perfectly with 3.11.1 but fails miserably with anything post
3.11.
On Sat, Sep 21, 2013 at 09:16:25AM +0800, Wang Shilong wrote:
- open_ctree_fs_info_restore(target, 0, 0, 0, 1);
+ open_ctree_fs_info_restore(target, 0, 0, OPEN_CTREE_PARTIAL);
Good idea, i think this should be another patch.
yes
--
To unsubscribe from this list: send the line unsubscribe
On Sun, Sep 22, 2013 at 09:06:39AM +0800, Rongqing Li wrote:
I want to know how many cores your cpu has? I can not reproduce it on
my 2 cores cpu, but it always happens when run on a server which is
a 16 cores cpu and make -j20
Depends on what you call a core, I've tested this on a box with 8
Hello,
My system is configured to do FS snapshots when I upgrade packages. I
have a cron job which runs at night to delete these snapshots. Its goal
is to keep 10 snapshots maximum, one per day if possible.
This works perfectly with 3.11.1 but fails miserably with anything post
3.11.
Hello,
Wang Shilong posted on Mon, 23 Sep 2013 10:18:19 +0800 as excerpted:
On 09/23/2013 09:53 AM, Dusty Mabe wrote:
There is one other thing I have noticed while playing around
with quota and qgroups. If I delete subvolumes I can manage to get some
of the qgroup information to be
Hello,
I think this problem may be related to qgroup memory leak that you also
reported before,
however, i have not reproduced it in my test box.
By the way, did you machine still exist high memory cost with quota enabled?
Thanks,
Wang
Not sure if it's anything interesting - I had the
On Mon, Sep 23, 2013 at 04:47:29PM +0800, Liu Bo wrote:
The command is
btrfs subvolume set-default subvolid path.
It uses @subvolid to control the default subvolume and
@subvolid=0 has always been parsed into FS_TREE no matter
what subvolume @path points to.
So in order to set a
On Mon, Sep 23, 2013 at 09:17:46AM -0400, Josef Bacik wrote:
On Mon, Sep 23, 2013 at 04:47:29PM +0800, Liu Bo wrote:
The command is
btrfs subvolume set-default subvolid path.
It uses @subvolid to control the default subvolume and
@subvolid=0 has always been parsed into FS_TREE no
On Mon, Sep 23, 2013 at 07:43:44AM +0700, Tomasz Chmielewski wrote:
Not sure if it's anything interesting - I had the following entry in
dmesg a few days ago, on a server with 32 GB RAM. The system is still working
fine.
Can you try the patch here
On 9/20/13 11:42 AM, David Sterba wrote:
The message about trim was printed unconditionally, we should check if
trim is supported at all.
Good idea, but I wonder if there's any risk that discard(0,0) will ever
be optimized away on the kernel side pass unconditionally?
I was thinking we could
Mathieu Chouquet-Stringer posted on Mon, 23 Sep 2013 14:54:17 +0200 as
excerpted:
My system is configured to do FS snapshots when I upgrade packages. I
have a cron job which runs at night to delete these snapshots. Its goal
is to keep 10 snapshots maximum, one per day if possible.
This
On 9/23/13 10:44 AM, David Sterba wrote:
On Mon, Sep 23, 2013 at 10:08:08AM -0500, Eric Sandeen wrote:
On 9/20/13 11:42 AM, David Sterba wrote:
The message about trim was printed unconditionally, we should check if
trim is supported at all.
Good idea, but I wonder if there's any risk that
On Mon, Sep 23, 2013 at 10:08:08AM -0500, Eric Sandeen wrote:
On 9/20/13 11:42 AM, David Sterba wrote:
The message about trim was printed unconditionally, we should check if
trim is supported at all.
Good idea, but I wonder if there's any risk that discard(0,0) will ever
be optimized away
Wang Shilong wangshilong1991 at gmail.com writes:
In Dusty's reproduced steps, there are no parent qgroups. So i think every
qgroup should works as expected, if negative numbers come out, it must
be a *bug*.
In that case would you like for me to open a new bug report with the details?
On Fri, Sep 20, 2013 at 09:53:02AM -0700, Greg KH wrote:
On Fri, Sep 20, 2013 at 06:34:39PM +0200, David Sterba wrote:
3d05ca371200b3366530621abf73769024581b79
b13a004528c3e5eb060a26eee795f5a0da7bfe9f
7ef67ffda91cc0c56f33937bfdf1d057b9ee96ca
ca6d07c1d74bf7ba3083bc31a9aeeaa1d0ad86aa
On Mon, Sep 23, 2013 at 07:43:44AM +0700, Tomasz Chmielewski wrote:
Not sure if it's anything interesting - I had the following entry in
dmesg a few days ago, on a server with 32 GB RAM. The system is still working
fine.
Yes this is interesting of course.
[1878432.675210] btrfs-qgroup-re:
On Tue, Sep 17, 2013 at 11:30:52AM -0400, Frank Holton wrote:
Thanks for that hint to use ftw. I've updated the code to use it and
tried to make sure
that I caught all of the styling errors.
Dunno what caused that, but the whitespace is completely messed up and
squasthed into a single space
On Mon, Sep 23, 2013 at 07:19:06PM +0200, David Sterba wrote:
On Mon, Sep 23, 2013 at 07:43:44AM +0700, Tomasz Chmielewski wrote:
Not sure if it's anything interesting - I had the following entry in
dmesg a few days ago, on a server with 32 GB RAM. The system is still
working fine.
Yes
This patch was tested on a kernel with [PATCH v4] Btrfs: fix sync fs to
actually wait for all data to be persisted applied.
Thanks,
chandan
--
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
The sync makes sure that 'very recently' introduced delayed work is
accounted for in the output of 'btrfs subvolume find-new' command.
Signed-off-by: chandan chan...@linux.vnet.ibm.com
---
cmds-subvolume.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/cmds-subvolume.c
Add an option to defrag all files in a directory recursively.
Signed-off-by: Frank Holton fhol...@gmail.com
---
v3: prefix globals with defrag
v2: switch to ftw amd callback
cmds-filesystem.c | 156 ++---
1 file changed, 113 insertions(+), 43
SAMSUNG SSD 830 Series
CPU0: Intel® Core(TM) i7-2820QM CPU @ 2.30GHz (fam: 06, model: 2a, stepping: 07)
8GB RAM (quite heavily tested, not recently, with several days of memtest)
kernel 3.11.1-200.fc19.x86_64 running on baremetal
btrfs-progs-0.20.rc1.20130308git704a08c-1.fc19.x86_64
Today I did a
Result of btrfsck (without --repair) on the fs.
Checking filesystem on /dev/sda6
UUID: d505bdee-ba7c-4a64-9481-d5cd76ab8b3e
checking extents
checking fs roots
root 257 inode 37693 errors 1800
found 3938304000 bytes used err is 1
total csum bytes: 3557972
total tree bytes: 271794176
total fs tree
On mon, 23 Sep 2013 11:35:11 +0100, Filipe David Borba Manana wrote:
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
On Mon, Sep 23, 2013 at 9:35 PM, Wang Shilong
wangsl.f...@cn.fujitsu.com wrote:
On 09/24/2013 12:55 AM, Dusty Mabe wrote:
In that case would you like for me to open a new bug report with the
details?
Yes.
https://bugzilla.kernel.org/show_bug.cgi?id=61951
--
To unsubscribe from this list:
48 matches
Mail list logo
