From: Anand Jain anand.j...@oracle.com
This will add new option -x to the btrfs subvol list
sub-command to display subvol-snapshot relation in tree
format with appropriate indentation.
Anand Jain (5):
Btrfs-progs: add parent uuid for snapshots
Btrfs-progs: maintain similar case in heading
From: Anand Jain anand.j...@oracle.com
Signed-off-by: Anand Jain anand.j...@oracle.com
---
btrfs-list.c | 32 +++-
btrfs-list.h |1 +
cmds-subvolume.c |6 +-
3 files changed, 33 insertions(+), 6 deletions(-)
diff --git a/btrfs-list.c
From: Anand Jain anand.j...@oracle.com
A trivial fix
before this patch
btrfs su list -qu /btrfs
ID 256 gen 35 top level 5 parent UUID - uuid
60e54c4a-8136-3c43-a107-ea42052c6240 path sv1
ID 257 gen 35 top level 5 parent UUID 60e54c4a-8136-3c43-a107-ea42052c6240
uuid
From: Anand Jain anand.j...@oracle.com
its better to have btrfs_list_subvols just return witout printing
so that btrfs_list_subvols can be reused.
Signed-off-by: Anand Jain anand.j...@oracle.com
---
btrfs-list.c | 28 ++--
btrfs-list.h |2 +-
From: Anand Jain anand.j...@oracle.com
Currently we have default (name value) and table format to
list the subvol. This patch will help to accommodate the
enhancement to provide the tree display for the subvol-snapshot
list.
Signed-off-by: Anand Jain anand.j...@oracle.com
---
btrfs-list.c |
From: Anand Jain anand.j...@oracle.com
This will add new option -x to the btrfs subvol list
sub-command to display the snapshots under its parent subvol
with appropriate indentation.
Signed-off-by: Anand Jain anand.j...@oracle.com
---
btrfs-list.c | 135
I've been testing Josef's btrfs-next master branch using a test that
loops through creation, manipulation and destruction of snapshots of
kernel git sources.
The version of btrfs-next I'm using was built as of Friday, December
14th, and the top commit is:
Btrfs: don't take inode delalloc mutex if
Hello Mitch, hello all,
Since btrfs has significant improvements and fixes in each kernel
release, and since very few of these changes are backported, it is
recommended to use the latest kernels available.
Ok, it's 3.7 now.
The root ### inode # errors 400 are an indication that there
On Sat, Dec 15, 2012 at 1:40 PM, Hendrik Friedel hend...@friedels.name wrote:
Hello Mitch, hello all,
Since btrfs has significant improvements and fixes in each kernel
release, and since very few of these changes are backported, it is
recommended to use the latest kernels available.
Ok,
I've got a system running Debian kernel 3.2.0-4-amd64 with root on a SSD that
identifies itself as INTEL SSDSC2CT12 300i (it's an Intel 120G device).
Here is the /proc/mounts entry which shows that ssd and discard options are
enabled.
/dev/disk/by-uuid/7939c405-c656-4e85-a6a0-29f17be09585 /
On Sat, Dec 15, 2012 at 5:23 PM, Russell Coker
russell+bt...@coker.com.au wrote:
I've got a system running Debian kernel 3.2.0-4-amd64 with root on a SSD that
identifies itself as INTEL SSDSC2CT12 300i (it's an Intel 120G device).
3.2 is massively old in btrfs terms, with lots of fun little
11 matches
Mail list logo