similar to: [PATCH] btrfs-progs: add -V description in print_usage

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 ---

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

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

Three kind of structures need to be freed on close: * All struct btrfs_device managed by fs_devices * The name field for each struct btrfs_device * The above items for seed_devices Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com> --- volumes.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git a/volumes.c b/volumes.c index

Hello, This patch adds rollback support for the converter, the converter can roll back a conversion if the image file haven't been modified. In addition, I rearrange some codes in convert.c and add a few comments. Regards YZ --- diff -r 12138d4beeb0 convert.c --- a/convert.c Fri Jan 04 11:29:55 2008 -0500 +++ b/convert.c Mon Jan 07 23:35:25 2008 +0800 @@ -33,6 +33,7 @@ #include

The patch is against 3.1-rc3. struct vring_used has two __u16 fields plus array of struct vring_used_elem. Current vring_size counts the __u16 fields to 3. Fix it to 2 in the patch. Signed-off-by: Wang Sheng-Hui <shhuiw at gmail.com> --- include/linux/virtio_ring.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/virtio_ring.h

The patch is against 3.1-rc3. struct vring_used has two __u16 fields plus array of struct vring_used_elem. Current vring_size counts the __u16 fields to 3. Fix it to 2 in the patch. Signed-off-by: Wang Sheng-Hui <shhuiw at gmail.com> --- include/linux/virtio_ring.h | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/include/linux/virtio_ring.h

The memory allocation failure is BUG_ON in add_excluded_extent (following the code path). No need to BUG_ON -ENOMEM inside btrfs_alloc_logged_file_extent. Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com> --- fs/btrfs/extent-tree.c | 6 ++---- 1 files changed, 2 insertions(+), 4 deletions(-) diff --git a/fs/btrfs/extent-tree.c b/fs/btrfs/extent-tree.c index 95492cc..9b9a6fa 100644 ---

Currently we can specify the testing filesytems like ''check -xfs'', but btrfs is not support in this kind of command option. Add the option ''check -btrfs'' support. Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com> --- check | 2 ++ 1 file changed, 2 insertions(+) diff --git a/check b/check index ff8fbcf..9c40615 100755 --- a/check +++ b/check @@

I started to try to use llvm::Error recently. This has nice runtime checks for if you didn't check the result, but I thought it would be really nice to get a compiler warning for the obvious cases of this rather than having to wait for a runtime check. This, of course, is exactly what the C++17 [[nodiscard]] attribute is for - with new enough compilers in C++17 mode we can just declare the

Sanjoy Das <sanjoy at playingwithpointers.com> writes: > Hi Justin, > > This SGTM generally, but please make the difference between > LLVM_NODISCARD and LLVM_UNUSED_RESULT clear in the code. :) Right, this is where it gets a little weird. LLVM_NODISCARD would be for types, whereas LLVM_UNUSED_RESULT would be for functions. Depending on your host compiler, using the wrong one

Some programs like btrfsck should not be run on a mounted filesystem. This patch adds a check in btrfs_open_devices() for the mount status of every device belonging to the filesystem. The function check_mount() gets improved support for loopback devices. It now detects if the program is run on the file that is being used by the loopback device. Signed-off-by: Andi Drebes

Hi, I thought that I would attempt a quick little patch that will make btrfsck into a No-op when called as fsck.btrfsck. The reasoning is that the FAQ states that it is recommended and safe to do so, and the current 12.04 version of Ubuntu just symlinks fsck.btrfsck to btrfsck instead of /bin/true. PS - Apologies if I mess this git send-email up! Dan McGrath (1): btrfs-progs: No-op when

If you are using XFS - there is mount option "discard|nodiscard" From XFS man page: discard|nodiscard Enable/disable the issuing of commands to let the block device reclaim space freed by the filesystem. This is useful for SSD devices, thinly provisioned LUNs and virtual machine images, but may have a performance impact. Note: It is currently

Use a custom test driver for running the tests: based on the test-driver provided by automake, it adds the running time of the test in each .trs file. --- configure.ac | 1 + guestfs-test-driver | 151 ++++++++++++++++++++++++++++++++++++++++++++++++++++ tests/Makefile.am | 2 + 3 files changed, 154 insertions(+) create mode 100755 guestfs-test-driver diff --git a/configure.ac

Add man/mkfs.btrfs.8.in Kept the name with the name in, so that further processing such as BUILD_DATE BUILD_VERSION etc. could be included later. All man pages included in the man directory to avoid file cluttering. Signed-off-by: Goldwyn Rodrigues <rgoldwyn@suse.de> --- man/mkfs.btrfs.8.in | 63 +++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 63 insertions(+), 0

Hello, I feel that the klibc package should include an insmod that can be used on an initramfs. While it is possible to use an insmod built statically against glibc, such a binary is (comparatively) huge at 565K. The attached insmod.c is essentially the insmod.c from module-init-tools minus a couple of lines related to calling the old (2.4) version of insmod for backward compat. BTW: Insmod

Hello, There is a new feature ''uninitialized block groups'' in ext4. Block and inode bitmaps in uninitialized block groups are uninitialized. This confuses the converter. The fix is call ext2fs_new_inode for each block group at open time. It set up uninitialized block and inode bitmaps appropriately. This patch also contains some other minor fixes. Thank you, Signed-off-by: Yan

FIXME this patch isn't complete, still need to figure out the ldap command to wait for that service, something along the lines of: ldapsearch -b dc=priv,dc=ovirt,dc=org -x (but how will we parse the base from the installer? also this cmd fails, how to fix?) --- installer/modules/ovirt/manifests/ovirt.pp | 8 +++++- installer/modules/ovirt/manifests/postgres.pp | 13 ++++++---

Replaced the previous HostWrapper class with the new HostAgent class, which more closely resembles the style of the ProcessorsAgent class. Deleted the HostWrapper class entirely. Refactored the daemon entry point to reduce the number of methods invoked in order to start or stop the HostAgent instance. Moved the NICWrapper's setupQMFObject method from private to public so that it can be