similar to: [btrfs-progs 1/4] Add man/mkfs.btrfs.8.in

Add man/btrfsctl.8.in Signed-off-by: Goldwyn Rodrigues <rgoldwyn@gmail.com> --- man/btrfsctl.8.in | 45 +++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 45 insertions(+), 0 deletions(-) create mode 100644 man/btrfsctl.8.in diff --git a/man/btrfsctl.8.in b/man/btrfsctl.8.in new file mode 100644 index 0000000..e11f46a --- /dev/null +++ b/man/btrfsctl.8.in @@ -0,0 +1,45 @@

Extend mkfs options to specify optional or potentially backwards incompatible features. Signed-off-by: David Sterba <dsterba@suse.cz> --- man/mkfs.btrfs.8.in | 9 ++++ mkfs.c | 124 +++++++++++++++++++++++++++++++++++++++++++++++----- 2 files changed, 123 insertions(+), 10 deletions(-) diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in index a3f1503..548e754 100644 ---

Currently mkfs in response to mkfs.btrfs -d raid10 dev1 dev2 instead of telling "you can''t do that" creates a SINGLE on two devices, and only rebalance can transform it to raid0. Generally, it never warns users about decisions it makes and it''s not at all obvious which profile it picks when. Fix this by checking the number of effective devices and reporting back

Signed-off-by: Matias Bjørling <m@bjorling.me> --- man/mkfs.btrfs.8.in | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/man/mkfs.btrfs.8.in b/man/mkfs.btrfs.8.in index 41163e0..db8c57c 100644 --- a/man/mkfs.btrfs.8.in +++ b/man/mkfs.btrfs.8.in @@ -37,7 +37,7 @@ mkfs.btrfs uses all the available storage for the filesystem. .TP \fB\-d\fR, \fB\-\-data

Hi Rich, A compiling error occurs here, File "../ocaml/guestfs.ml", line 1, characters 0-1: Error: The implementation ../ocaml/guestfs.ml does not match the interface ../ocaml/guestfs.cmi: Values do not match: external mkfs_btrfs : t -> ?allocstart:int64 -> ?bytecount:int64 -> ?datatype:string ->

Hi, I try to format a USB memory with a Btrfs. I can format it with mkfs.btrfs without problems. But; when I try to mount it, it fails to mount with the below error messages. But the USB memory works fine with other filesystems (ext4, XFS etc.). So, the hardware is not faulty. tarkane@tarkane:~$ sudo mkfs.btrfs -d single -n 4096 /dev/sdb1 WARNING! - Btrfs v0.18-26-g0030f1d IS EXPERIMENTAL

Hello all We are experimenting with btrfs and we''ve run into some problems. We are running on two Sun Storage J4400 Arrays containing a total of 48 1 TB disks. With 24 disks in the btrfs: # mkfs.btrfs /dev/sd[b-y] WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using adding device /dev/sdc id 2 ... adding device /dev/sdy id 24 fs

Check for the return value of ''open_ctree()'' before dereferencing it. Signed-off-by: Nageswara R Sastry <nasastry@in.ibm.com> --- btrfs-image.c | 1 + 1 file changed, 1 insertion(+) diff --git a/btrfs-image.c b/btrfs-image.c index f2bbcc8..2a33a55 100644 --- a/btrfs-image.c +++ b/btrfs-image.c @@ -491,6 +491,7 @@ static int create_metadump(const char *input, FILE *out,

We do log replay in a single transaction, so it''s not good to do unbound operations during replaying log. This patch makes orphan inodes cleanup executed after replaying log. It also avoid doing other unbound operations such as truncating a file during replaying log. These unbound operations are postponed to the orphan inode cleanup stage. Signed-off-by: Yan Zheng

This fixes up the progs to properly deal with skinny metadata. This adds the -x option to mkfs and btrfstune for enabling the skinny metadata option. This also makes changes to fsck so it can properly deal with the skinny metadata entries. Thanks, Signed-off-by: Josef Bacik <jbacik@fusionio.com> --- V2->V3: update the mkfs.btrfs man page with the new option This is based on

moved the node-,leaf-,sectorsize from btrfs_root to btrfs_fs_info since we don''t intend to allow different sizes between trees also removed sectorsize from btrfs_block_group_cache because it now can use the one in fs_info updated all uses accordingly please note in disk-io.c: -static int __setup_root(nodesize, leafsize, sectorsize, stripesize, - *root,

Since 2.6.29-rc1 contains btrfs I had to try it. However the loopback mount of my btrfs formatted file fails: user@host:~$ dd if=/dev/zero of=btrfs.img bs=1MB count=512 user@host:~$ mkfs.btrfs btrfs.img fs created label (null) on btrfs.img nodesize 4096 leafsize 4096 sectorsize 4096 size 488.28MB Btrfs v0.16+da35ab2b0b54 user@host:~$ sudo mount -t btrfs -o loop btrfs.img /mnt/btrfs mount:

Signed-off-by: Goldwyn Rodrigues <rgoldwyn@gmail.com> --- man/Makefile | 27 +++++++++++++++++++++++++++ man/btrfsck.8.in | 17 +++++++++++++++++ 2 files changed, 44 insertions(+), 0 deletions(-) create mode 100644 man/Makefile create mode 100644 man/btrfsck.8.in diff --git a/man/Makefile b/man/Makefile new file mode 100644 index 0000000..2665dd1 --- /dev/null +++ b/man/Makefile

hi,sir I creat the filesystem with command mkfs.btrfs /dev/sda2, and it returns fs created label (null) on /dev/sda2 nodesize 4096 leafsize 4096 sectorsize 4096 size 2.93GB then I mount the /dev/sda2 with command mount -t btrfs /dev/sda2 /btrfs/, it returns mount: /dev/sda2: can''t read superblock. Why? -- To unsubscribe from this list: send the line "unsubscribe

btrfs 0.19 Ubuntu 10.10 Linux linux 2.6.35-23-generic #41-Ubuntu SMP Wed Nov 24 11:55:36 UTC 2010 x86_64 GNU/Linux I create a new btrfs on a 200GB disk with one partition. I mount the partition. I create a snapshot of that partition. I unmount the partition. I run btrfsck and it says I have an "unresolved ref" error. If I create two snaps, I get three errors. If I create three snaps, I

From: Andi Kleen <ak@linux.intel.com> 240f62c8756 replaced the node_lock with rcu_read_lock, but forgot to remove the actual lock in the data structure. Remove it here. Signed-off-by: Andi Kleen <ak@linux.intel.com> --- fs/btrfs/ctree.h | 3 --- fs/btrfs/disk-io.c | 1 - 2 files changed, 0 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h index

Hi, As I use btrfs as root FS, I wanted fstype to be able to recognize it. The following patch add support for this FS. Regards, benjamin Signed-off-by: Benjamin Cama <benoar at free.fr> --- diff --git a/usr/kinit/fstype/btrfs_fs.h b/usr/kinit/fstype/btrfs_fs.h new file mode 100644 index 0000000..e1f933e --- /dev/null +++ b/usr/kinit/fstype/btrfs_fs.h @@ -0,0 +1,51 @@ +#ifndef

(switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Thu, 17 Feb 2011 13:20:20 GMT bugzilla-daemon@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=29302 > > Summary: Null pointer dereference with large max_sectors_kb > Product: IO/Storage > Version: 2.5 > Kernel

The type of some functions that return only 0 is changed to ''void''. In addition, the check on the return value in the caller of these functions becomes unnecessary. So, these check is removed. Signed-off-by: Tsutomu Itoh <t-itoh@jp.fujitsu.com> --- fs/btrfs/async-thread.c | 17 ++++-------- fs/btrfs/async-thread.h | 4 +- fs/btrfs/compression.c | 14 ++++------

Hello I did the following commands and resulted in a segmentation fault. [root@localhost ~]# mkfs.btrfs /dev/sda6 WARNING! - Btrfs Btrfs v0.19 IS EXPERIMENTAL WARNING! - see http://btrfs.wiki.kernel.org before using fs created label (null) on /dev/sda6 nodesize 4096 leafsize 4096 sectorsize 4096 size 46.93GB Btrfs Btrfs v0.19 [root@localhost ~]# mount /dev/sda6 /mnt/btra [root@localhost ~]#