search for: f2fs

Hi, this small patch series exposes one of the utility in f2fs-tools, and use it to expand f2fs partitions in virt-resize. Thanks, Pino Toscano (2): New API: f2fs_expand resize: expand f2fs partitions daemon/Makefile.am | 1 + daemon/f2fs.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++ generator/actions_core.ml | 9 ++++++++...

Use resize.f2fs (via f2fs_expand) to expand f2fs filesystems, if available. --- resize/resize.ml | 12 ++++++++++-- resize/virt-resize.pod | 10 ++++++++-- 2 files changed, 18 insertions(+), 4 deletions(-) diff --git a/resize/resize.ml b/resize/resize.ml index 1a21e4dff..8e4bb1b16 100644 --- a/resize/resiz...

Hi, easy series to improve the support for f2fs filesystems: while we should be able to mount them already (if the used kernel has the support for this filesystem), put in the appliance f2fs-tools, so we can also create them. Unfortunately, there isn't much in f2fs-tools, so all that can be done is simply setting a different label only when...

...g +S: Supported +F: tests/btrfs/ +F: common/btrfs + +CEPH +L: ceph-devel at vger.kernel.org +S: Supported +F: tests/ceph/ +F: common/ceph + +CIFS +L: linux-cifs at vger.kernel.org +S: Supported +F: tests/cifs + +EXT4 +L: linux-ext4 at vger.kernel.org +S: Supported +F: tests/ext4/ +F: common/ext4 + +F2FS +L: linux-f2fs-devel at lists.sourceforge.net +S: Supported +F: tests/f2fs/ +F: common/f2fs + +FSVERITY +L: fsverity at lists.linux.dev +S: Supported +F: common/verity + +FSCRYPT +L: linux-fscrypt at vger.kernel.org +S: Supported +F: common/encrypt + +FS-IDMAPPED +L: linux-fsdevel at vger.kern...

This patch adds support for the F2FS filesystem to fstype. Signed-off-by: Marc Dietrich <marvin24 at gmx.de> --- usr/kinit/fstype/f2fs_fs.h | 44 ++++++++++++++++++++++++++++++++++++++++++++ usr/kinit/fstype/fstype.c | 14 ++++++++++++++ 2 files changed, 58 insertions(+) create mode 100644 usr/kinit/fstype/f2fs_fs.h diff --...

Pass -L $LABEL to set the label of a f2fs filesystem when creating it. --- daemon/mkfs.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/daemon/mkfs.c b/daemon/mkfs.c index cef3574..a0617a0 100644 --- a/daemon/mkfs.c +++ b/daemon/mkfs.c @@ -228,6 +228,10 @@ do_mkfs (const char *fstype, const char *device, int blocksize, ADD...

...68cb..0ad12a38 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -108,6 +108,7 @@ Maintainers List or reviewer or co-maintainer can be in cc list. BTRFS +R: Filipe Manana <fdmanana at suse.com> L: linux-btrfs at vger.kernel.org S: Supported F: tests/btrfs/ @@ -137,16 +138,19 @@ F: tests/f2fs/ F: common/f2fs FSVERITY +R: Eric Biggers <ebiggers at google.com> L: fsverity at lists.linux.dev S: Supported F: common/verity FSCRYPT +R: Eric Biggers <ebiggers at google.com> L: linux-fscrypt at vger.kernel.org S: Supported F: common/encrypt FS-IDMAPPED +R: Chris...

...to new ctime accessors ecryptfs: switch to new ctime accessors efivarfs: switch to new ctime accessors efs: switch to new ctime accessors erofs: switch to new ctime accessors exfat: switch to new ctime accessors ext2: switch to new ctime accessors ext4: switch to new ctime accessors f2fs: switch to new ctime accessors fat: switch to new ctime accessors freevxfs: switch to new ctime accessors fuse: switch to new ctime accessors gfs2: switch to new ctime accessors hfs: switch to new ctime accessors hfsplus: switch to new ctime accessors hostfs: switch to new ctime acces...

In every place where sb_start_pagefault was called now we must manage the error code and return VM_FAULT_RETRY. Signed-off-by: Marco Stornelli <marco.stornelli at gmail.com> --- fs/btrfs/inode.c | 4 +++- fs/buffer.c | 4 +++- fs/ext4/inode.c | 4 +++- fs/f2fs/file.c | 4 +++- fs/gfs2/file.c | 4 +++- fs/nilfs2/file.c | 4 +++- fs/ocfs2/mmap.c | 4 +++- include/linux/fs.h | 6 ++++-- mm/filemap.c | 7 +++++-- 9 files changed, 30 insertions(+), 11 deletions(-) diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c index 09c...

...happen we would miss to raise IOP_XATTR because sb->s_xattr would be NULL. Fix these things and then get rid of the misleading and effectively already unused generic POSIX ACL handlers. For most filesystems it is a trivial removal of the generic POSIX ACL handlers. Only for erofs, ext2, ext4, f2fs, jffs2, reiserfs, oc2fs the handler is used but rather easy to fix. All filesystems with reasonable integration into xfstests have been tested with: ./check -g acl,attr,cap,idmapped,io_uring,perms,unlink All tests pass without regression on xfstests for-next branch. Since erofs doesn...

..."btrfs" |] then - printf "btrfs\n"; + machine_readable_printf "btrfs\n"; if g#feature_available [| "xfs" |] then - printf "xfs\n"; + machine_readable_printf "xfs\n"; if g#feature_available [| "f2fs" |] then - printf "f2fs\n"; + machine_readable_printf "f2fs\n"; exit 0 ); diff --git a/sparsify/cmdline.ml b/sparsify/cmdline.ml index b0af053ac..4070d46bf 100644 --- a/sparsify/cmdline.ml +++ b/sparsify/cmdline.ml @@ -107,19 +107,19 @@ read the...

...it system, and decided to tackle booting Quirky on it, from a USB stick. I turned off Secure Boot. I wrote /usr/share/syslinux/gptmbr.bin to the flash drive (/dev/sdc) with dd. I setup the Flash stick with GPT, a 512MB FAT32 EFI System partition, and the rest of the drive a second partition with f2fs filesystem. I installed syslinux 6.03 in the normal way: # syslinux --install /dev/sdc1 I have the usual files in the root directory of the first partition, this is them: boot.msg help.msg ldlinux.c32 ldlinux.sys logo.16 syslinux.cfg vmlinuz Content of syslinux.cfg: default quirky display boo...

...fs.org/guestfs-release-notes.1.html New features New features in existing tools Virt-inspector now displays the libosinfo short ID for guests (Pino Toscano). Guestfish -N will now generate 1G disks instead of 100M disks by default. Virt-resize supports f2fs filesystems (Pino Toscano). libguestfs-test-tool now supports bash tab completion (Pino Toscano). The --machine-readable option now supports sending output to files or stdout/stderr. This works uniformly across most OCaml-based virt tools, specifically: virt-builder,...

Hi, this is a first approach (hence RFC, since it misses tests & documentation) in selecting the output for --machine-readable. The possible choices are: * --machine-readable: to stdout, like before * --machine-readable=file:name-of-file: to the specified file * --machine-readable=stream:stdout: explicitly to stdout * --machine-readable=stream:stderr: explicitly to stderr This makes it

...n"; if g#feature_available [| "btrfs" |] then - printf "btrfs\n"; + pr "btrfs\n"; if g#feature_available [| "xfs" |] then - printf "xfs\n"; + pr "xfs\n"; if g#feature_available [| "f2fs" |] then - printf "f2fs\n"; + pr "f2fs\n"; exit 0 + | _, _ -> () ); (* Verify we got exactly 2 disks. *) @@ -353,7 +355,10 @@ read the man page virt-resize(1). (* The output disk is being created, so use cache=unsafe here. *)...

..._all> -will make them visible. +calling C<guestfs_lvm_scan> with the C<activate> +parameter C<true> will make them visible. Use C<guestfs_list_dm_devices> to list all device mapper devices." }; @@ -9718,4 +9706,26 @@ before the partition." }; This expands a f2fs filesystem to match the size of the underlying device." }; + { defaults with + name = "lvm_scan"; added = (1, 39, 8); + style = RErr, [Bool "activate"], []; + tests = [ + InitEmpty, Always, TestRun ( + [["lvm_scan"; "true"]]), []...

...oting Quirky on it, from a USB stick. > > I turned off Secure Boot. > > I wrote /usr/share/syslinux/gptmbr.bin to the flash drive (/dev/sdc) with dd. > > I setup the Flash stick with GPT, a 512MB FAT32 EFI System partition, > and the rest of the drive a second partition with f2fs filesystem. > > I installed syslinux 6.03 in the normal way: > > # syslinux --install /dev/sdc1 Remember (just in case) that the filesystem should be unmounted before executing the syslinux installer command, or use the extlinux installer instead. To reduce some potential problem...

I think I might be mad to include that many mailing lists in this patchset... As I explained in [PATCH 1/5], fstests covers more and more fs testing thing, so we always get help from fs specific mailing list, due to they learn about their features and bugs more. Besides that, some folks help to review patches (relevant with them) more often. So I'd like to bring in the similar way of

Hi all, I'm wondering whether it is feasible to have an option that will make rsync spawn a separate thread to close files it has created, to avoid the main process blocking while the destination files are flushed during the close operation? The reason I ask is that it is currently very slow to use rsync on a fast locally-mounted network filesystem, as you see the following behaviour: 1.

Hi, this adds the possibility to select the output for --machine-readable in OCaml tools. The possible choices are: * --machine-readable: to stdout, like before * --machine-readable=file:name-of-file: to the specified file * --machine-readable=stream:stdout: explicitly to stdout * --machine-readable=stream:stderr: explicitly to stderr This makes it possible to add additional output for