similar to: [PATCH] recognise ext4 without journal

Enhance fstype so it properly takes into account whether or not the ext4 and/or ext4dev filesystems are present, and properly handles the test_fs flag. The old code also has some really buggy checks --- for example, where it compared the set of supported ro_compat features against the incompat feature bitmask: (sb->s_feature_incompat & __cpu_to_le32(EXT3_FEATURE_RO_COMPAT_SUPP) I

hello hpa, nothing too exciting, again syncing latest Debian upload and subsequent patch emails. plus wanting to get the ext4dev in line for the Lenny release. :) please review. thanks -- maks please pull git pull git://git.debian.org/~maks/klibc.git maks for the changes: Arthur Loiret (1): Makefile (ARCH): Support sh4 as sh. David H?rdeman (1): [klibc] mount: allow multiple fs

hello hpa, rebased my branch, please pull latest git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for the following shortlog maximilian attems (6): fstype: add squashfs v3 support reiser4_fs.h: add attribute packed to reiser4_master_sb fstype: add ext4 support .gitignore: add subdir specific entries usr/klibc/Kbuild: beautify klibc build fstype:

Commit-ID: 52251e210c7a21068063fe16a3874903d3f1aa14 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=52251e210c7a21068063fe16a3874903d3f1aa14 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Mon, 7 Oct 2019 20:39:46 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Tue, 8 Oct 2019 00:13:20 +0100 [klibc] fstype: Drop obsolete

[please note that I'm not subscribed to the list] Hi again, this patch adds support for the NILFS2 (http://www.nilfs.org/) filesystem to fstype (on top of 1.5.7 from the debian package). Please let me know what you think. (please note that I'm not affiliated to nilfs in any way). diff -Nur klibc-1.5.7.orig/usr/kinit/fstype/fstype.c klibc-1.5.7/usr/kinit/fstype/fstype.c ---

This is part of some patches to support sectors > 512. Currently I'm able to boot a Ubuntu kernel but seems that mboot is not working for some reason. This patch add a rdwr_bytes functions which remove the assumption in some places that sector is 512. This function is quite helpful if you are going to read/write a range of bytes to/from the stack without creating stack overflows for free.

hello hpa, please pull git pull git://brane.itp.tuwien.ac.at/~mattems/klibc.git maks for those changes: Kyle McMartin (1): klibc-utils: add dmesg maximilian attems (2): klibc comment fix fstype: add ocfs2 support with the following diffstat README | 2 usr/Kbuild | 2 usr/kinit/fstype/fstype.c | 15 +++++++

I have an ext3 filesystem that I want to mount without loading the journal. I tried the "noload" option with both 2.4.9 and 2.4.18 series kernels and get the errors listed below. [root@host]# mount -t ext3 -o noload /dev/sdf1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdf1, or too many mounted file systems /var/log/messages: Apr 18 13:30:23 host kernel: ext3:

It's already mounted rw somewhere else. This enables the needs_recovery feature which prevents an ext2 mount. -Leslie -----Original Message----- From: Christopher J. PeBenito [mailto:pebenito@ieee.org] Sent: Tuesday, April 22, 2003 11:30 AM To: kuczynski, leslie Cc: 'ext3-users@redhat.com' Subject: Re: ext3 "noload" option to mount returning error in 2.4.9 & 2.4.18 s

I have an ext3 filesystem that I want to mount without loading the journal. I tried the "noload" option with both 2.4.9 and 2.4.18 series kernels and get the errors listed below. [root@host]# mount -t ext3 -o noload /dev/sdf1 /mnt mount: wrong fs type, bad option, bad superblock on /dev/sdf1, or too many mounted file systems /var/log/messages: Apr 18 13:30:23 host kernel: ext3:

An embedded and charset-unspecified text was scrubbed... Name: sparse-fs_ext3_resize.patch URL: <http://listman.redhat.com/archives/ext3-users/attachments/20050620/8e33ffa8/attachment.ksh>

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 9991b95cb712cdd9a40240bde6274d5415476fb5 commit: 860c7fa9d6d433011e82a4f7f896893e914ce4a9 [11/22] fw_cfg: write vmcoreinfo details config: i386-randconfig-a0-201804 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: git checkout 860c7fa9d6d433011e82a4f7f896893e914ce4a9 # save

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: 9991b95cb712cdd9a40240bde6274d5415476fb5 commit: 860c7fa9d6d433011e82a4f7f896893e914ce4a9 [11/22] fw_cfg: write vmcoreinfo details config: i386-randconfig-c0-02011330 (attached as .config) compiler: gcc-7 (Debian 7.2.0-12) 7.2.1 20171025 reproduce: git checkout 860c7fa9d6d433011e82a4f7f896893e914ce4a9

Signed-off-by: Alexey Dobriyan <adobriyan at mail.ru> --- fs/ext3/resize.c | 20 ++++++++++---------- fs/ext3/super.c | 8 ++++---- include/linux/ext3_fs.h | 2 +- 3 files changed, 15 insertions(+), 15 deletions(-) Index: linux-warnings/include/linux/ext3_fs.h =================================================================== ---

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

[please note that I'm not subscribed to the list] Hi guys, I've noticed that the size returned by the fstype utility was not correct for JFS filesystems (it returns the size in number of HW blocks instead of bytes). Here is a simple patch that addresses it (based on 1.5.7 from the debian package). diff -Nur klibc-1.5.7.orig/usr/kinit/fstype/fstype.c

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 --git a/usr/kinit/fstype/f2fs_fs.h b/usr/kinit/fstype/f2fs_fs.h

On Tue, 24 Jun 2003 ext3-users-request@redhat.com wrote : >Send Ext3-users mailing list submissions to > ext3-users@redhat.com > >To subscribe or unsubscribe via the World Wide Web, visit > https://www.redhat.com/mailman/listinfo/ext3-users >or, via email, send a message with subject or body 'help' to > ext3-users-request@redhat.com > >You can reach the person

This patch ports 5 new applications to the stubdom makefile structure for inclusion into stubdom domains. While these are required for vtpm-stubdom and vtpmmgrdom they could be used with other stubdom applications. -libgmp 4.3.2 -openssl 1.0.0a -polarssl 0.12.1 -berlios tpm_emulator 0.6.1 -vtpm_manager (from the tools directory) Signed off by: Matthew Fioravante

The latest version that Western Digital has shipped with the My cloud devices accesses the disk about twice a minute. The access to /dev/sda2 is causing the system to keep the disk from going into standby mode. I don't understand the call to quotactl every minute when no one is trying to access the share. An strace of one of the processes shows the following: poll([{fd=13,